> 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/security-policies-conditions.md).

# Security policy conditions

The conditions available for Snyk security policies

A condition is a variable on which to set a rule.

After you select a condition category, you are prompted to select **Includes** or **Does not include** and the desired condition, for example, Mature, CWE-1234.

Security policies are applicable to Snyk Open Source and Snyk Container Projects.

You can stack multiple conditions in the same rule using the **AND** function.

<table data-header-hidden><thead><tr><th width="210">Condition category</th><th>Condition definitions and variables</th></tr></thead><tbody><tr><td>Exploit Maturity</td><td>Matches all issues that contain a specified exploit maturity value. When multiple values are selected, the condition applies to all issues containing any of the selected values. Values include <code>Mature</code>, <code>Proof of Concept</code>, <code>No known exploit</code>, and <code>No data available</code>.</td></tr><tr><td>CWE</td><td>Matches all issues that contain a specified CWE. Supports multiple CWEs.</td></tr><tr><td>CVE</td><td>Matches all issues that contain a specified CVE. Supports multiple CVEs.</td></tr><tr><td>Snyk ID</td><td>Matches all issues that contain a specified Snyk ID. Supports multiple Snyk IDs. Not every issue has a CVE, so this is a good way to specify those.</td></tr><tr><td>Severity</td><td>Matches all issues that contain a specified severity level. When multiple values are selected, the condition will apply to all issues containing any of the selected severity levels (for example, Critical, High, Medium, Low).</td></tr></tbody></table>


---

# 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/security-policies-conditions.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.