> 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/implement-snyk.md).

# Overview

Overview of implementing Snyk across your organization, from development through deployment, to fix vulnerabilities and build a security culture

Implementing a developer security tool like Snyk is critical to ensuring the security of your applications, from development through deployment. Whatever the size of your team, the goals are to fix vulnerabilities and foster a culture of security awareness and responsibility across your entire business.

Here is a brief overview of the process:

1. **Assessment**: Evaluate your current security practices and identify areas for improvement.
2. **Planning**: use the provided Project plans to outline your goals, timelines, and necessary resources.
3. **Configuration**: Follow configuration guidance to tailor the security platform to your needs, ensuring it integrates seamlessly with your existing tools and workflows.
4. **Rollout**: Implement the platform across your development teams, following the specific guidance for small teams or enterprise environments.
5. **Training**: Educate your developers on the importance of security and how to use the platform effectively.
6. **Monitoring and iteration**: Continuously monitor the health and performance of your applications and make adjustments as needed to maintain optimal security.

If you have a small team looking for guidance on rolling out Snyk in your processes, see the [Team implementation guide](/implementation-guides/team-implementation-guide.md).

If you are part of an enterprise implementing a large-scale rollout, see the [Enterprise implementation guide](/implementation-guides/enterprise-implementation-guide.md).

The guides include a downloadable project plan, a planning phase, configuration guidance, and guidance on rollout specific to each context.


---

# 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/implement-snyk.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.