> 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/start-scanning/overview-scan-settings/built-in-scan-profiles.md). # Built-in scan profiles The built-in Snyk API & Web scan profiles and their differences Snyk API & Web has four different built-in scan profiles: * **Lightning** * **Safe** * **Normal** * **Full** ## Lightning The **Lightning** scan profile is designed for speed, taking less than a minute to complete, and focuses on identifying vulnerabilities related to SSL/TLS, HTTP headers, and cookies. ## Safe The **Safe** scan profile minimizes the potential impact on the target application by testing for all supported vulnerabilities using a limited set of payloads. The scanner uses only GET requests and does not include POST, PUT, or DELETE requests. The crawler still makes requests using these methods when necessary, for example, to log in to the application. ## Normal The **Normal** scan profile tests for all supported vulnerabilities and uses a more extensive set of payloads than the **Safe** profile without any restrictions on the methods used. ## Full The **Full** scan profile includes all tests from the **Normal** profile and uses an even more extensive set of payloads. ## Customization Snyk also lets you customize scan profiles when you need to adjust and fine-tune the scans for your targets. For details, visit [Customize a scan profile](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/start-scanning/overview-scan-settings/customize-scan-profile.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/scan-with-snyk/snyk-api-web/start-scanning/overview-scan-settings/built-in-scan-profiles.md?ask=&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.