> 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.md).

# Security policies

How Group administrators define Snyk security policies

Group administrators can define Open Source and Container security policies, providing an automated way to identify certain issues or types of issues and apply actions like changing the severity of or ignoring an issue based on specified conditions.

{% hint style="info" %}
Security policies are applicable to Snyk Open Source and Snyk Container Projects.
{% endhint %}

You can [create a security policy and set rules](/scan-fix-and-prevent/prevent/policies/security-policies/create-a-security-policy-and-rules.md) by clicking the **Policies** menu option on the Group Overview page to open the Policy manager.

You can [apply a policy to Project attributes](/scan-fix-and-prevent/prevent/policies/assign-policies-to-projects.md) or [apply a policy to an Organization](/scan-fix-and-prevent/prevent/policies/assign-a-policy-to-an-organization.md).

For more information about security policies, see the following pages:

* [Security policy conditions](/scan-fix-and-prevent/prevent/policies/security-policies/security-policies-conditions.md)
* [Security policy actions](/scan-fix-and-prevent/prevent/policies/security-policies/security-policy-actions.md)
* [Security policy results](/scan-fix-and-prevent/prevent/policies/security-policies/security-policy-results.md)


---

# 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.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.