> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/snyk/onboard-snyk.md).

# Onboard Snyk

Connect Snyk to Cortex Cloud to ingest SCA and SAST findings.

## Prerequisites

Complete the [Snyk prerequisites](/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/snyk.md#prerequisites) before onboarding.

1. Navigate to **Settings** → **Data Sources & Integrations** → **+ Add New**.
2. Search for and hover over **Snyk** and click **Add**, or **Add Another Instance** if an instance is already onboarded.
3. On the **Configure Integration** step of the integration wizard.
   1. Configure Snyk parameters:
      * Select your **Snyk API URL** from the menu (for example `API URLSNYK-US-02 (https://api.us.snyk.io/rest`))
      * Enter your **Snyk API token**
   2. Click Authorize.
4. On the **Select Organization** step of the wizard: **Enter your Snyk Organization ID** → **Next**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Select <strong>Test Connection</strong> to verify that Cortex Cloud can connect to your Snyk organization.</p></div>
5. On the **Select Issue Types** step of the wizard: **Select the type of data findings to be ingested: SAST, SCA or both** → **Next**.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><ul><li>SCA requires Snyk Open Source or Snyk Container projects configured in the organization</li><li>SAST requires Snyk Code enabled and projects configured in the organization</li></ul></div>
6. Select ingestion targets: On the **Map to Repositories** step of the wizard, review the detected Snyk projects and confirm or manage their repository mappings

   1. * Select **Automatically map future Snyk applications** to automatically map current and future Snyk projects to Cortex Cloud repositories. This is recommended to ensure maximum security coverage
      * Configure unmapped or mismatched applications: Manually configure mapping if Cortex Cloud cannot match an application to a repository or an update to the mapping is required: From the list of detected applications, select the application from the list, then choose the correct repository from the **Repository** dropdown menu
   2. Click Save.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><ul><li>Mapping establishes relationships between Snyk applications and Cortex Cloud code repositories, simplifying access management and enabling risk analysis at the repository level, including displaying findings on the tenant</li><li>Only mapped applications are ingested</li></ul></div>

   After saving, Cortex Cloud triggers the initial scan ingestion for the selected targets.

## Verify integration

Verify the integration in Cortex Cloud:

* On **Data Sources & Integrations**, filter for **Snyk**. Select the data source and confirm your instance and mapped applications show **Connected**.

## Validate scan health and view results

After connection, Cortex Cloud ingests Snyk findings. Scanning supports SAST and SCA analysis.

1. Navigate to **Modules** → **Application Security** → **AppSec Coverage**.
2. Filter by **Is scanned by Snyk = true**.
3. Select a repository.
4. Review the Snyk findings and issues generated by repository policies.

## Manage Snyk integrations

1. Go to **Settings** → **Data Sources & Integrations**.
2. Search for **Snyk** and select the result.

### Instance actions

Right-click an instance and select an action:

* **Edit instance**: The onboarding wizard opens. Update the issue types or repository mappings.
* **Delete instance**: Delete the integration configuration and its mappings. Findings and issues from previous Snyk scans remain active.
* **Copy entire row**: Copy all row values to the clipboard.

{% hint style="info" %}
You need the required RBAC permissions to edit or delete an instance.
{% endhint %}

### Project actions

Right-click a connected project to modify its **Scan Configuration** or **Remove Project**. You can select the Semgrep issue types to ingest in **Scan Configuration**.

1. Locate your instance. See [Instance actions](#instance-actions) above.
2. Select the instance. A list of connected projects appears.
3. Right-click a project, select the required action, then select **Save**.

## Learn more about Snyk ingestion

Review how Cortex Cloud ingests and manages Snyk issues and findings:

[Snyk Software Composition Analysis (SCA) ingestion](/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/snyk/snyk-software-composition-analysis-sca-ingestion.md).

[Snyk Static Application Security Testing (SAST) data ingestion](/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/snyk/snyk-static-application-security-testing-sast-data-ingestion.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/snyk/onboard-snyk.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
