> 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/scan-with-snyk/snyk-api-web/vulnerabilities-detected/owasp-top-10-scanning.md).

# OWASP Top 10 scanning

How Snyk API & Web scans for the OWASP Top 10

Snyk API & Web can scan for the 2021 and 2025 Open Web Application Security Project (OWASP) Top 10, searching for a wide range of vulnerabilities that belong to the different OWASP Top 10 categories.

## Generate OWASP Top 10 reports

After the target scan, you can generate a target scan report for OWASP Top 10. The report includes a table indicating which areas of the Top 10 Snyk tested and which ones passed.

Visit [Types of target scan reports you can generate with Snyk API & Web](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/overview-reports/report-types.md) for more information about generating reports.

## Scan profiles and OWASP Top 10

All built-in scan profiles check for the Top 10 vulnerabilities, except for the **Lightning** scan profile.

Visit [Built-in scan profiles and their differences](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/start-scanning/overview-scan-settings/built-in-scan-profiles.md) for more information about scan profiles.


---

# 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/scan-with-snyk/snyk-api-web/vulnerabilities-detected/owasp-top-10-scanning.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.