> 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/integrations/snyk-sast-dast-integration.md). # Snyk SAST/DAST integration How to integrate Snyk SAST and Snyk API & Web DAST findings {% hint style="info" %} **Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface. {% endhint %} ## Snyk SAST/DAST integration This guide explains how to set up and use the static application security testing (SAST) and dynamic application security testing (DAST) integration to correlate findings from Snyk API & Web (DAST) with your static analysis results in Snyk (SAST). ### Overview By connecting your dynamic and static scan results, you can streamline triage and remediation. This integration links DAST findings directly to the vulnerable location in your source code, helping your developers fix vulnerabilities faster. ### Prerequisites * You must have active accounts in both Snyk API & Web and the Snyk platform. * You must have a target application that both Snyk for SAST (Snyk Code) and Snyk API & Web for DAST scan. ### Step 1: Connect your Snyk accounts Establish a connection between your Snyk API & Web account and your main Snyk account. 1. In Snyk API & Web, navigate to **Settings > Integrations**. 2. Locate the **Snyk** module. 3. Click the link to **Snyk group**. This starts the authentication and authorization process to connect your two accounts. ### Step 2: Map a target to your Snyk projects Next, tell Snyk API & Web which Snyk Code projects (code repository) correspond to your DAST target. 1. Navigate to the **Targets** page and identify the target you want to integrate. 2. Navigate to that target **Settings** and click the **Integrations** tab. 3. In the **Snyk** module, click **Select projects** to open a new modal. 4. Map the current Snyk API & Web target to the corresponding code analysis projects from Snyk and click **Save**. ### Step 3: Run a DAST scan Run a new scan on the target you configured in Step 2. Snyk API & Web correlates the DAST findings from this scan with the SAST findings from your mapped Snyk projects. ### Step 4: Analyze correlated findings After the scan is complete, you can view the correlated results. Any correlated finding has an associated SAST label. 1. From the list of findings for your target, click a finding to open its details page. 2. Select the **SAST Findings** tab. ### Verify the outcome The **SAST Findings** tab provides the connection between your DAST and SAST results. A DAST finding provides proof that a vulnerability is exploitable. This integration links that finding directly to the specific line in your source code, so you can fix it immediately. The correlation provides you with a link to the vulnerability within Snyk Code, a link to the repository, and a snippet of code that is triggering a given vulnerability. ### Manage the feature and provide feedback You can provide feedback directly on the finding details page. * In the **SAST Findings** tab, you can report whether you believe the correlation was a match or a mismatch. This helps fine-tune the correlation process and provide better results. * You can also provide additional qualitative feedback to help improve the accuracy of the correlation engine. --- # 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/integrations/snyk-sast-dast-integration.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.