> 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/create-a-vulnerability-policy.md).

# Create a vulnerability policy

Create vulnerability policies that create issues or prevent findings based on defined conditions and scope.

Before creating a policy, be sure to review the information in the [Vulnerability Policies](/cortex-cloud-posture-management/vunerability-management/vulnerability-policies.md) section.

1. Navigate to **Posture Management** → **Rules & Policies** → **Policies** → **Vulnerability Management**.
2. Click **+Add Policy** and select one of the options:
   * **Create a policy for issue creation**
   * **Create a policy for prevention**
3. Add a **Policy Name** and, optionally, a **Description**, and then click Next.
4. Set the policy conditions by creating a query that defines the specific findings for which the policy will create issues. Your policy can specify which findings to include and which to exclude.

   Preview the list of findings that match your policy. If the results look correct, click **Next**.
5. Define the policy scope by selecting one or more asset groups from the dropdown menu. If you don't choose an asset group, the policy will apply to all assets.

   If you want to create a new asset group, click **Create New Asset Group** to open the **Asset Groups** page in a new browser tab. Click **+ Add Group** and follow the instructions in the wizard. After you've created the new asset group, go back to your original tab and finish creating your policy with new asset group.

   Click **Next**.
6. Choose the action that will be executed on the findings that match the policy. If you select **Create an issue for each matching finding**, you must also select the issue severity that will be applied to those issues. You can base the severity of the issue on the severity of the underlying CVE by selecting **Use Default CVE Severity** in the dropdown menu.
7. Click **Done**.

   The policy wizard will close, and you will be redirected back to the **Vulnerability Policies** page.
8. Set the order of evaluation for the policy.

   By default new policies are added to bottom of the policy list. To move a policy up or down in the list, click and hold the arrows in the **Name** column and drag the policy to the desired position in the list.

   We recommend placing wider-reaching, more generic policies towards the bottom of the policy list, and more specific policies towards the top of the list.

   Click **Save**.


---

# 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/create-a-vulnerability-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.