Links

Snyk Broker - Code Agent

This feature is currently in Beta. If you would like to set it up in your Organization, contact your Snyk Integration Consultant/Technical Success Manager or Snyk Support.
To connect Snyk Code to your self-hosted Git server via the Snyk Broker, you must add the Code Agent component to the Snyk Broker deployment structure. By using the Code Agent component with the Snyk Broker, you can scan repositories that are stored on your self-hosted Git provider, and apply the Snyk Code analysis to these repositories in order to find, prioritize, and fix potential vulnerabilities in your source code.
For more information on the Snyk Broker deployment method, see Snyk Broker.
The Automatic PR Checks feature is currently not supported in the Snyk Broker - Code Agent deployment method.

Snyk Code - deployment components for accessing a self-hosted Git provider

To apply the Snyk Code analysis to repositories that are stored on your self-hosted Git server, you need the following components:
The Broker Client and Code Agent components are deployed in your infrastructure, creating two separate services. Together with the Broker Server, the Snyk Code AI Engine, and the Snyk Web UI, these components are responsible for the following Code Analysis workflow:
1. On the Snyk Web UI, a request is initiated by a user to import a repository from a self-hosted Git server to Snyk for Code Analysis. The request can also be initiated from the Snyk API v1, by using the Import targets request.
2. The request arrives at the Broker Server, which is hosted by Snyk. The Broker Server sends the request to the Broker Client, which sends it to the Code Agent. The Broker Client automatically provides the Code Agent with the connection details to the integrated SCM, which stores the required repositories.
3. The Code Agent connects to the integrated SCM, and clones the local repository in a secured manner in your infrastructure. The cloned repository is stored temporarily on the Code Agent container. The cloning is performed via HTTPS connection. If your SCM does not support HTTPS, you can work around this with a reverse proxy. For more details reach out to your technical contact at Snyk.
4. The Code Agent filters the cloned repository for supported files and sends them to the Snyk Code AI Engine.
5. The Snyk Code AI Engine analyzes the code files in search of vulnerability issues. The analysis results are sent back to the Snyk Web UI. The cloned files are cached for up to 24 hours before they are deleted. For more information, see How Snyk handles your data.
nyk Code Analysis workflow with Broker
Snyk Code Analysis workflow with Broker
© 2022 Snyk Limited