> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/containers/private-container-registry/dcd-how-tos/view-vulnerability-scan-results.md).
# View Vulnerability Scan Results
Each Private Container Registry can provide a detailed analysis of Common Vulnerabilities and Exposures (CVEs) that may be exploitable in your artifacts. For more information, see [Enable Vulnerability Scanning](/cloud/containers/private-container-registry/dcd-how-tos/enable-vulnerability-scanning.md).
Vulnerability scan results provide detailed information about the security of your artifacts at different levels. The following sections provide more information.
## Search the Private Container Registry for a specific vulnerability
When new vulnerabilities are identified, you may want to search your entire Private Container Registry to see if any of the artifacts are vulnerable. To do this, you will need the Common Vulnerabilities and Exposures (CVE) number. Every published vulnerability or security issue is assigned a unique CVE number.
1\. In the **DCD**, go to **Menu** > **Containers** > **Container Registry**.
2\. In the **Container Registry** window, select the Private Container Registry by clicking on its name, and select the **Vulnerability Search** tab. Alternatively, from the **OPTIONS** column > select  > **Vulnerabilities**.
3\. Search for a specific vulnerability by entering its full CVE number in the **Vulnerability Search** tab.
{% hint style="success" %}
**Result:** A list of artifacts known to be vulnerable to the CVE are displayed.
{% endhint %}
## Summarize Vulnerability Scan results by Repository
To secure your artifacts and the software supply chain, review vulnerability scan results periodically. First, identify which repositories contain vulnerabilities.
1\. In the **DCD**, go to **Menu** > **Containers** > **Container Registry**.
2\. In the **Container Registry** window, click the name of your target Private Container Registry and select the **Repositories** tab. Alternatively, from the **OPTIONS** column > select  > **Repositories**.
{% hint style="success" %}
**Result:** The Private Container Registry displays a list of repositories. The **VULNERABILITIES** column indicates the highest severity vulnerability found in the most recently pushed artifact.
{% endhint %}
{% hint style="info" %}
**Note:** Depending on the content of your Private Container Registry, there may be too many repositories to list on a single page. Remember to use the **per page** to set the number of repositories displayed per page and to navigate between pages using **<** and **>**.
{% endhint %}
## Summarize Vulnerability Scan results by Artifact
You can review specific artifacts within a repository to identify vulnerability exposure. This view highlights artifacts with known fixes and displays the last push date (the update timestamp) and the last pull date—which often aligns with environment deployments.
1\. In the **DCD**, go to **Menu** > **Containers** > **Container Registry**.
2\. In the **Container Registry** window, click the name of your target Private Container Registry and select the **Repositories** tab. Alternatively, from the **OPTIONS** column > select  > **Repositories**.
3\. In the **Repositories** tab, click the name of the repository to select and review it. Alternatively, select  > **View Repository**.
{% hint style="success" %}
**Result:** The repository view lists all artifacts and displays the following information:
* The artifact and the tag used when pushing the artifact to the repository.
* The **VULNERABILITIES** column lists the highest severity vulnerability detected during the **LAST SCAN**.
* The **LAST PUSH** date and time of the most recent artifact update.
* The **LAST PULL** date and time indicating the last retrieval of the artifact (often indicating a deployment).
{% endhint %}
{% hint style="info" %}
**Note:** Depending on the content of your repository, there may be too many artifacts to list on a single page. Remember to use **per page** to set the number of artifacts displayed per page and to navigate between pages using **<** and **>**.
{% endhint %}
## View Vulnerability Scan Results for a specific Artifact
1\. In the **DCD**, go to **Menu** > **Containers** > **Container Registry**.
2\. In the **Container Registry** window, click the name of your target Private Container Registry and select the **Repositories** tab. Alternatively, from the **OPTIONS** column > select  > **Repositories**.
3\. In the **Repositories** tab, click the name of the repository to select and review it. Alternatively, select  > **View Repository**.
4\. Select the artifact you want to view.
{% hint style="success" %}
**Result:** The view lists all known CVEs affecting the artifact. Use the available filters to sort the list by **SEVERITY** or to display only **FIXABLE** vulnerabilities.
{% endhint %}
## View Details of a specific CVE
When you have found a specific CVE, either by [viewing vulnerability scan results for a specific artifact](#view-vulnerability-scan-results-for-a-specific-artifact) or by [finding artifacts that are vulnerable to a specific CVE](#view-vulnerability-scan-results-for-a-specific-artifact), you can see more details about the CVE by clicking on the CVE identification number. This will provide additional information about the vulnerability and may include references to third-party sites where additional information can be found.
---
# 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.ionos.com/cloud/containers/private-container-registry/dcd-how-tos/view-vulnerability-scan-results.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.