> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/vunerability-management/vulnerability-policies/update-the-ignored-cves-asset-groups-and-assets-policy.md).

# Update the Ignored CVEs, Asset Groups, and Assets policy

Update the ignored CVEs, asset groups, and assets policy to prevent matching vulnerability findings from creating issues.

Policy number 0 in the policy list is the **Ignored CVEs, Asset Groups, and Assets** policy. This policy contains a list of vulnerabilities and assets for which Cortex Cloud will not create vulnerability issues. Findings will still be created for these vulnerabilities and assets, and you can review those on the **Vulnerabilities** and **Vulnerable Assets** pages. You can update the **Ignored CVEs, Asset Groups, and Assets** policy at any time by using the following steps to add or remove assets, asset groups, and CVEs.

1. Navigate to **Posture Management** → **Rules & Policies** → **Policies** → **Vulnerability Management**.
2. The first policy in the policy list is the **Ignored CVEs, Asset Groups, and Assets** policy. Click on that policy to open the policy wizard.
3. Add or remove vulnerabilities, asset groups, and assets as needed. Click **Next**.
   * To add CVEs, asset groups, or assets, use the search bar in each section to find the value you are looking for, and select it to add it to the list.
   * To remove CVEs, asset groups, or assets, click the **X** to the right of each item in the list.
4. Review the **Results Preview** to see the list of findings that will not generate issues. If the list looks correct, click **Done**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/vunerability-management/vulnerability-policies/update-the-ignored-cves-asset-groups-and-assets-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.