> 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/implementation-guides/team-implementation-guide/phase-5-rolling-out-the-prevention-stage.md).

# Phase 5: Rolling out the prevention stage

Phase 5 of the Snyk team implementation: roll out prevention and gating to stop new vulnerabilities entering your applications

After you gain visibility into your security issues, you can start to implement a prevention and gating system to stop new vulnerabilities from being added to your applications.

## Common prevention methods

The following are the two common ways to prevent new issues:

* Snyk tests on pull request (PR) and merge request (MR) checks, available for Snyk Open Source and Snyk Code.
* Adding `snyk test` to your CI/CD pipelines (you may have already implemented `snyk monitor` to import your Projects as part of the pipeline).
  * You can gate open source, code, infrastructure as code, and container vulnerabilities.

In either case, Snyk recommends that you communicate these changes clearly to your developers before implementing any form of gating.

## Tips

### Block the differences

If you are not already blocking vulnerabilities, start by blocking the difference.

This eases developers into the process, as they only take responsibility for vulnerabilities directly related to their changes.

To block new issues, you can use PR Checks. For details, visit [Run PR Checks](https://docs.snyk.io/scan-fix-and-prevent/prevent/pull-request-checks).

### Communicate exception processes

Ensure that the teams know the exception processes and what to do if a PR is blocked or a build fails.

For example:

* Let the team know who has the authority to override a PR check if a pass is mandatory.
* If a build fails, can the issue be ignored and the test rerun? Who can run it? Or can a script be run allowing that step to pass? Who can make that determination?


---

# 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/implementation-guides/team-implementation-guide/phase-5-rolling-out-the-prevention-stage.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.
