Snyk Broker

Feature availability Snyk Broker is available with Enterprise plans. See pricing plans for more details.
Multi-tenant settings for EU and AU When you set up Broker, Code Agent, or both for use in EU or AU Multi-tenant environments, additional environment variables with the specific URLs are required. Example: -e BROKER_SERVER_URL= For the URLs, see EU and AU account datacenter creation.

Introduction to Snyk Broker

Snyk Broker is an open-source tool that acts as a proxy between Snyk and special integrations, to allow access to your code for scanning and returning results to you. SCM integrations with Broker support Snyk Open Source, Snyk Code, Snyk Container (Dockerfile), and Snyk IaC. Supported integrations with Broker include the following:
  • Your Source Code Management (SCM) that is not internet reachable
  • Your publicly-accessible SCM, allowing you to view and control Snyk activity for increased data security
  • Network-restricted container registries
  • Infrastructure as code (IaC) configuration files using Snyk IaC located on private Git-based repositories
You can also use Snyk Broker to enable a secure connection with your on-premise Jira installation or JFrog Artifactory installation.
Snyk Broker is designed to connect Snyk products to self-hosted integrations that are not publicly accessible from the internet. Snyk Broker also allows you to do the following:
  • Control Snyk access to your network, by limiting the files to which Snyk has access and the actions that Snyk can perform.
  • Manage a fixed private IP for your integration, targeting the Broker.
The Snyk Broker project is hosted at GitHub and published as a set of Docker images for specific integrations. For more information see Integrations with Snyk Broker on this page.

Components of Snyk Broker

Snyk Broker has a Server and a Client, basic components that are the same across all integrations:
  • Broker Server - running on the Snyk SaaS backend The Broker Server is provided by Snyk, and no installation is required on your part.
  • Broker Client - a Docker image deployed in your infrastructure
The Broker Client and Server together act as a tunnel to your code, sending requests by proxy from to a Git repository and fetching manifest files from monitored repositories, and fetching results using webhooks posted by the Git service. The tunnel allows for scanning using only requests on an approved data list. This narrows the access permissions to the absolute minimum required for Snyk to actively monitor a repository. For details see Approved data list for Snyk Broker on this page.
For information about components that are required for using Snyk Code Agent, Snyk Container Registry Agent, and Snyk Broker for Infrastructure as Code, see Define your Broker deployment components.
The diagram that follows illustrates how the basic components operate.
  • All data, both in transit and at rest, is encrypted.
  • Communication between the Client and the Server takes place over a secure WebSocket connection.
  • There is no need to open incoming ports since the communication is initiated outbound.
  • Once the connection is initiated, the WebSocket connection is bi-directional.
Snyk Broker WebSocket initiated by Client over HTTPS
Snyk Broker WebSocket initiated by Client over HTTPS

Using inbound and outbound connections with Snyk Broker

The Broker client runs within your internal network, keeping sensitive data such as Git tokens within the network perimeter.

Inbound connection from Snyk to the Broker Client

There is no direct inbound connection from Snyk to the Broker Client.
The Broker Client makes an outbound connection to, which establishes a WebSocket connection. This allows communication with the Broker Server.
Thus there is no need to allowlist a Snyk IP address. Instead you can allow the Broker Client IP/port.

Outbound connection from the Broker Client

The Broker Client initiates the outbound connection to establish the WebSocket.
After the WebSocket connection initiated by the Broker Client is established, Snyk can send inbound requests to the Broker Client via the WebSocket.
Thus you do not need to allow inbound connections to the Broker Client from Snyk-specific IP addresses or other external IP addresses.

Approved data list for Snyk Broker

The Broker Client maintains an approved data list for inbound and outbound data requests. Only data on this approved list may be requested. This narrows the access permissions to the absolute minimum required for Snyk to actively monitor a repository.

Inbound requests allowed

For Snyk Open Source:
  • is allowed to fetch and view only dependency manifest files and the .snyk policy file.
  • No other source code is viewed, extracted, or modified.
  • You may check in additional .snyk files to support the Snyk patch mechanism and for any ignore instructions included in your vulnerability policy.
Snyk Code and Snyk IaC need access to the entire repository.
See How Snyk handles your data for more details. For information about using Snyk Broker with Snyk Container and requirements for open source, code analysis, and IaC, see Using Snyk Broker to scan your code.

Outbound requests allowed

When you configure your Broker Client setup, Git repository webhooks are set to enable automatic Snyk scans that are triggered when your developers submit new pull requests or merge events.
Webhook notifications are delivered to Snyk via the Broker Client only for events relevant to Snyk actions: push to branch and open pull request and only when the event data also includes a dependency manifest file or a .snyk policy file.

Default approved data list and accept.json file

Because of the limitations of the default approved data list, if you want to scan Infrastructure as Code files with Snyk Broker, you must add and configure an accept.json file in your Broker deployment.
To learn more about the approved data list and the accept.json file, see Install and configure the Snyk Broker Client, Custom approved-listing filter section.

Using Snyk Broker to scan your code

To use Snyk Open Source with Snyk Broker, you need only the Broker Server and the Broker Client components. The Broker Client is published as a set of Docker images, each configured for a specific Git service. Configure each type of integration using environment variables as explained in the Snyk Broker - Client integration setups.
To scan other types of code with Snyk Broker, you must add a component or configurations and add parameters to the Broker Client setup:
  • Snyk Code – add the Code Agent component to enable Snyk Code analysis of repositories in SCMs that are integrated through Snyk Broker.
  • Snyk Container – add the Container Registry Agent to enable the connection to network-restricted container registries container registries and the analysis of container images.
  • Snyk Infrastructure as Code – configure the accept.json file with additional parameters to detect and analyze Terraform, CloudFormation, and Kubernetes configuration files through Snyk Broker.

Integrations with Snyk Broker

The Broker Client is published as a set of Docker images, each configured for a specific Git service. Configure each type of integration using environment variables as explained in the Snyk Broker Client integration setups. Snyk Broker currently integrates with the following Git repository systems:
In addition, Snyk Broker integrates with Jira Server/Jira Data Center, JFrog Artifactory, and Nexus Repository Manager.
With the Container Registry Agent, Snyk Broker also connects to all Snyk-supported container registries.

Common questions about Snyk Broker

How often is Snyk Broker updated? Snyk Broker is updated any time there are new features available and when there are fixes.
How often is Snyk Broker checked for vulnerabilities? The Snyk Broker application and images are being tested on a daily basis for vulnerabilities.
What is the SLA to fix vulnerabilities? There is a 14-day SLA for fixing high vulnerabilities and five-day SLA for fixing critical vulnerabilities in public images.
© 2023 Snyk Limited | All product and company names and logos are trademarks of their respective owners.