> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/risk-management/risk-indicators.md). # Risk Indicators Risk Indicators, also known as Risk Factors, highlight critical elements within your environment that may be targeted by attackers, including deployed images, runtime-connected repositories, and potential internet exposure (coming soon). By identifying these indicators, Prisma Cloud helps you prioritize which security issues to address first. This prioritization is crucial because external exposure can increase the risk of unauthorized access, data breaches, and exploitation of vulnerabilities. ## Prerequisites To leverage Risk Factors for prioritizing security efforts, you must first fulfill the following requirements. * Enable the CI/CD module in CAS. Refer to [Application Security License Types](/content-collections/application-security/get-started/application-security-license-types.md) for more information about the CI/CD module licensing * Ensure that [Agentless Scanning](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/runtime-security/agentless-scanning/agentless-scanning.md) and container image workloads are enabled in your cloud account or that [Defender](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/runtime-security/install/deploy-defender/deploy-defender.md) is enabled in your container orchestration environments * Connect your repositories to a supported CI system. Refer to [CI/CD Systems](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-systems/ci-cd-systems.md) for more information about integrating CI systems ## Prioritize External Risks Prioritize external risks through Deployed Repositories, Deployed Images and Internet Exposed Deployment (coming soon) risk indicators. ### Deployed Repositories The 'Deployed Repositories' risk indicator reveals which repositories trigger container image builds from your code. Use the **Risk Factor** filter to easily find your repositories that are connected to runtime. 1. In **Application Security**, select **Repositories**. 2. Under the **Risk Factors** filter, choose **Deployed Repository**.
prior risk deploy repo 3.1
Repositories deployed in runtime are displayed. The icon under the Risk Factor column indicates the type of risk indicator, in this case, deployed repositories.
prior risk icon1
3. To view additional details in a sidecar, click on the repository. The **Details** tab of the sidecar, which opens by default, displays repository details including size, last commit, dependencies, CI files, pipelines and deployed images. Additionally, all technologies detected in the repository are listed.
repo details3.1
4. Select the **Contributor** tab to view all contributors and their associated repository permissions. 5. Select the **Graph** tab to view the repository in graph view. For more information, refer to [Application Graph](/content-collections/application-security/visibility/repositories.md#app-graph). ### Deployed Images The **Deployed Images** risk indicator allows you to identify container images in a running environment. It also enables a comprehensive view of your code-to-cloud journey: The **Deployed Images** risk indicator allows you to identify container images in a running environment. It also enables a comprehensive view of your code-to-cloud journey (Repository > CI pipeline > Container Image). You can view deployed images under the **Deployed Images** column as well as through the **Details** tab in the repository sidecar (see Deployed Repositories above). Use the **Deployed Images filter** to filter by specific container images. This will enable you to quickly find your repositories that are connected to runtime.
prior risk deploy image filter1.1
## Runtime CVE Vulnerabilities You can identify CVE vulnerabilities detected in your runtime environment within Cloud Application Security (CAS), enabling you to mitigate these vulnerabilities at source and preventing them from impacting your runtime environment. For more information, refer to [Mitigate Runtime Vulnerabilities at Source](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/application-security/risk-management/monitor-and-manage-code-build/software-composition-analysis/software-composition-analysis.md#runtime-vulnerabilities). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prismacloud.io/content-collections/application-security/risk-management/risk-indicators.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.