Snyk
Last updated
Was this helpful?
Last updated
Was this helpful?
Snyk is a platform that helps developers find and fix vulnerabilities in their open-source dependencies and container images. It scans the project's dependencies to identify and alerts about any known security vulnerabilities.
Delivery Shield mandates security scans on images using Snyk. It connects with Snyk to see if the required version of the image has been scanned and if not done, Delivery Shield generates a security issue.
Once the Snyk scan is done, Delivery Shield pulls container security scan results from Snyk, and this data is used to calculate the overall security status of the images and application, to generate alerts and remediation.
The scan results fetched by Delivery Shield will be displayed in the Vulnerability Management page, Artifact section of the DBOM and View Open Security Issues page.
Navigate to Setup > Integrations.
In the Source panel, click Snyk.
You can use the toggle button provided below the integration tile to enable or disable it as needed.
The Snyk integration page is displayed.
Click +New Account. In the popup that appears, enter the values for the fields as shown below:
Enter the account name.
Enter the Snyk Org Id.
Select the Mode : Local or Cloud.
If Local Mode is selected, Snyk is run as a CLI tool.
If Cloud Mode is selected, SaaS version of Snyk is run.
Enter the token to access your Synk account in the Token field. (See Generating API Token for details on how to generate API token).
Enable or disable Helm scan as required.
Select the Teams and the corresponding Environments from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.
You can select up to 5 teams for the integration to be displayed.
An example is given below for reference:
In the example above,
if Team 1, Team 2, and Team 3 are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as Team 4, will not have access to this account.
Even if the user who created this account is also an admin for Team 4, the integration account remains restricted and is not available for Team 4.
Access to the account is strictly limited to the specified Teams and Environments selected during account creation.
For Organization Admins:
When an Organization Admin creates an account without selecting specific Teams and Environments, the account will be universally applicable, granting access to all teams and all environments by default.
For Team Admins with Multiple Teams:
If a Team Admin who manages multiple teams creates an account without specifying particular Teams and Environments, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
Click Save. The Synk account gets integrated in the artifact stage.
The new values get updated.
