Group-level integrations

Group-level SCM integrations provide broader visibility into all the application assets for a given customer and pull in the additional application context and, or metadata, for example, information on developers, commits, and so on.

At the Group level, you can set up and customize your Snyk Essentials integrations from the Integrations Hub, where the following SCMs are available:

• GitHub and GitHub Enterprise

• GitLab

• Azure DevOps

• BitBucket

If your SCM instance is not publicly accessible, you must connect using Snyk Broker. For details, see Snyk Broker - Snyk Essentials.

The Integrations page at the Group-level shows all active integrations, including any data automatically synced from your existing Snyk Organizations, and provides access to the Integration Hub.

The SCM integrations use an incremental approach to retrieve repositories. This means that when a sync is initiated, it checks the last update time of the repository and only transfers the repositories that have been modified since then.

If there have been changes to the scope of the user or PAT used for the integration, any repositories that are newly within scope will only be identified after either a change to trigger the incremental collection or a change to the integration configuration itself.

The following supported Snyk data are automatically synced:

• Snyk Open Source

• Snyk Code

• Snyk IaC

• Snyk Container

Each connected integration enables you to:

• Pause data syncing

• Modify integration profiles and configurations

• Delete the integration

• Check when the integration was last synced and when the next sync is scheduled.

See the Integration syncing time for more details about the time required to sync for each action.

Wildcard SCM integration

The wildcard integration allows you to use a special character to detect and integrate multiple SCM organizations simultaneously.

The wildcard integration applies to the GitHub integration and offers support when you set it up using Snyk Broker.

You can use the wildcards while setting up your integration using the Integration Hub:

• Open the Integration Hub menu.

• Select the SCM tag and search for GitHub or Azure DevOps.

• Click the Add button.

• In the Organizations field, add the Organization details by using the * symbol. For example, using *snyk integrates all SCM Organizations that have Snyk in their name.

• All the Organizations that match with the wildcard, * symbol will be added.

The wildcard, * symbol is considered a living command and will be applied every time you are rescanning your repositories.

Snyk Essentials and Snyk AppRisk integrations ecosystem

You can refer to the table below to verify the availability and compatibility of all integrations for Snyk Essentials and Snyk AppRisk. The integrations are categorized by type, listed by name, and indicated as available or not for both Snyk Essentials and Snyk AppRisk.

Integration type	Integration name	Snyk Essentials	Snyk AppRisk
SCM	GitHub BitBucket GitLab Azure DevOps	✔️	✔️
Dev portals and Service catalogs	Backstage catalog ServiceNow CMDB Atlassian Compass Harness OpsLevel Datadog Org Context (Service Catalog)	✔️	✔️
Risk management collaboration	Jira Slack Email	✔️	✔️
AST	NightFall GitGuardian	✖️	✔️
Runtime security and observability	Snyk runtime sensor Sysdig Dynatrace	✖️	✔️

Using the Integration Hub

Use the Integration Hub page to onboard integrations and populate Snyk Essentials with data from SCM tools.

See the Snyk Web UI page for step-by-step instructions on how to set up an integration.

After the integration is validated, a card is displayed on the Integrations page, allowing you to enable or disable the connection, edit the settings, or remove the connection from your configuration.

If you modify the permissions and scopes after the initial configuration, it is essential to either initiate an import or implement a change within the repository. This action allows Snyk to acknowledge and incorporate the updates effectively.