> 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/agent-security/evo-by-snyk/continuous-offensive-security-cos.md).

# Continuous Offensive Security (COS)

How Snyk Continuous Offensive Security continuously tests web applications and validates real vulnerabilities

Snyk Continuous Offensive Security is an AI-driven pentesting engine that continuously tests your web applications, validates real vulnerabilities, and tracks findings over time.

Use the pages in this section to configure targets, run scans, and review findings.

### Assessment depth

Depth is determined by whether a source repository is linked. There is no separate setting to change.

| Depth        | Condition            | What you get                                                                                                                                                                           |
| ------------ | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Blackbox** | No repository linked | Agents test entirely from the outside. Remediation guidance is generic to the vulnerability class, with references                                                                     |
| **Greybox**  | Repository linked    | Agents use source code to understand structure and reach logic flaws that are invisible from the outside. Remediation guidance names the file, the line, and the suggested code change |

Link repositories to help Snyk find more issues and provide more actionable guidance on fixes.


---

# 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/agent-security/evo-by-snyk/continuous-offensive-security-cos.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.