> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/prevent/policies/security-policies/create-a-security-policy-and-rules.md).

# Create a security policy and rules

How to create a Snyk security policy and its rules

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Create a security policy and rules

To create a new security policy, navigate to **Policies** in your Group menu, and in the Policies manager, expand the **Security policies** category and click **Add new policy**. For details, see [View policies](/scan-fix-and-prevent/prevent/policies/view-create-and-modify-policies.md).

{% hint style="info" %}
Select **Snyk Default Security Policy** to change the conditions or actions for a security policy that applies to all Projects in all Organizations in the Group.

Security policies are applicable to Snyk Open Source and Snyk Container Projects.
{% endhint %}

### Rules, conditions, and actions

Security policy rules are in the “if, then” format with one or more conditions and an action. An example follows:

{% hint style="info" %}
When you create a new security policy, the first blank rule is created automatically.
{% endhint %}

Select the conditions and actions to complete a rule. See [Security policy conditions](/scan-fix-and-prevent/prevent/policies/security-policies/security-policies-conditions.md) and [Security policy actions](/scan-fix-and-prevent/prevent/policies/security-policies/security-policy-actions.md) for details.

* To add a new blank rule, click on the plus sign beneath the previous rule.
* To delete or duplicate a rule, click the three dots at the top right of the rule box.

{% hint style="info" %}
The order of the rules you create determines the order they will be applied. If multiple rules with the same action type match the same issue, the rule closest to the top takes precedence over any subsequent rules.

**Example:**

* Rule 1: Sets severity to HIGH for issues with mature exploit maturity.
* Rule 2: Sets severity to LOW for issue ID "CVE-2025-0001".

If an issue with "CVE-2025-0001" also has mature exploit maturity, both rules apply. Because Rule 1 is listed first, the final severity will be HIGH.
{% endhint %}


---

# 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://docs.snyk.io/scan-fix-and-prevent/prevent/policies/security-policies/create-a-security-policy-and-rules.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.