Comment on page

How Snyk handles your data

Snyk is a developer security platform, and thus Snyk places the utmost importance on data security. Fully understanding your privacy and security needs, Snyk provides this document with the goal of providing you with transparency as to how and what data is accessed, transferred, and stored by Snyk.
The data handled by Snyk varies depending on the product you are using, how you are integrating with Snyk and your Snyk deployment. Because Snyk is subject to fast-moving changes, the types of data accessed and stored might change with the introduction of a new capability or changes to an existing capability.

Flexible deployment options

Snyk leverages the latest software development practices and technologies to provide customers with the flexibility to use Snyk’s developer security platform in the manner that best suits the needs of their business.
Snyk’s cloud-first deployment options offer ease of use and scalability while also providing the required level of data protection with multi- and single-tenancy options supported in the US, EU, and AUS. Additional regions will be supported in the future.
  • Multi-Tenant SaaS: The simplest, most common, and most cost-effective way to use Snyk’s developer security platform
  • Single-Tenant SaaS: Private Cloud - An isolated and fully managed instance of the Snyk developer security platform on AWS. For details, see Snyk Deployment Options.
  • Snyk Broker: A client service installed on your private infrastructure, acting as a proxy between the Snyk developer security platform (multi- or single-tenant) and your on-premise codebase. Snyk Broker securely handles inbound and outbound connections, encrypting data during transit and deliberately controlling the access Snyk has to your data. Sensitive credentials stay behind your firewall.
Be sure to reach out to your Snyk contact for more details on how these different options can be leveraged to meet your needs.

Customer data flows across Snyk

Snyk provides a wide range of development tools and integration points, requiring different types of data and involving different data interactions. The sections that follow provide an overview of both the common types of data Snyk accesses and stores and product and integration-specific types. The information is reviewed at least twice per year or when a significant change occurs within the product operations.

Common data types

  • Vulnerability data - Snyk stores information on the vulnerabilities identified in customer applications and related fix context.
  • Vulnerability source - Snyk stores information on where the vulnerability was identified. Examples: source code repository or registry, file name and location, dependency tree, vulnerability path.
  • Integration-related data - Snyk stores information required to set up an integration with Snyk. Examples: tokens and configurations.
  • User data - Snyk stores user information required to access and use the platform. Examples: user name, IDs (for example, GitHub user ID), email address, IP address.
  • User list - For purposes of accurate contributor counting, Snyk accesses commits from the last 90 days for repositories monitored. Upon request, an unhashed version of user emails is produced.
  • Billing data - Snyk stores information required for billing your Snyk account.
  • User behavior analytics - Snyk stores various types of information pertaining to usage patterns. Examples: platform navigation and executed CLI commands.

Product-specific data types

Snyk knows how important it is for you to protect your data. Snyk products only access and store the information needed to provide you with Snyk services and to ensure accurate analysis.
Snyk Open Source
Snyk Code
Snyk Container
Snyk IaC

Snyk Open Source

Snyk Open Source
  • Snyk accesses manifest files, lock files, and related configuration files in order to identify your open-source dependencies.
  • By default, Snyk does not access your source code with this exception: for CLI scans using the --unmanaged option, Snyk accesses your source code files to convert them to file signatures (hashes) and store the file signatures and file names.
  • For SCA Scans, Snyk does not access your source code.
  • Snyk accesses and stores the names and version numbers of your dependencies.
  • Snyk stores the names of associated licenses, including copyright and attribution information.
  • Snyk accesses and stores repository-specific information.
  • Snyk accesses and stores Git provider push and pull-specific information. Examples: contributor name, filenames, timestamps.
Optional ADD-ONS (opt-in)
Your account is subject to contract terms which might restrict your ability to enable these features. By enabling these features, you agree on behalf of your company to changes to your contract terms to allow these features, and you will be responsible for the use of these features based on your own circumstances.
  • For Go Modules full source code analysis feature - Snyk will access and store the contents of your git repository to facilitate the building of an accurate dependency graph. After the Snyk analysis is complete, your code is deleted from the Snyk system.
  • For the Reachable Vulnerabilities feature - Snyk will access and store the contents of your git repository to facilitate the building of a call graph. When the analysis completes, your code is deleted from the Snyk system. Only the call graph and function names are maintained.

Snyk Code

Snyk Code
  • Snyk accesses your repository code for a one-time analysis, caching it for up to 12 hours. After this period, only the location (file path, line, and column) of the issues found, the issue id, and explanations are maintained. Your code is removed and is not stored in the Snyk network or logs.
  • Results are stored in a database and used for analytic and monitoring purposes by Snyk.
  • When you are viewing Snyk Code issue details on the Snyk Web UI, note that the associated files are loaded and cached for up to 12 hours.
  • Snyk Code does not use any customer code (1) for engine training purposes or (2) to extract examples to show possible fixes.
  • The AI model for Snyk Code Fix Suggestions is trained on public repositories with permissive licenses, where any data from repositories with changing licenses are immediately removed. Static analysis, automated assessment, and partial human labeling are used during the data collection.
  • The scan results do not contain original source code but rather pointers to positions (for example, files, line, and column numbers), plus identification meta-information so that results are displayed using the correct source code version.
  • Snyk stores repository-specific information. Examples: Name of the Git repository and file names.
  • The server infrastructure ensures separation between customers by using authentication and authorization. Snyk Code uses software controls to ensure customer data segregation. All communication is encrypted using high-grade industry-standard protocols.

Snyk Container

Snyk Container
  • Snyk accesses and stores package versions, executable hashes and versions, operating system, container image metadata (for example, rootfs hashes, history), image ID.
  • Snyk accesses and stores information pertaining to the parent image - name, version, tag.
  • Snyk accesses and stores RUN instructions from Dockerfile.
  • Kubernetes configurations - Snyk accesses workload security settings (for example, ‘run as root’). This is only accessed if you use Snyk’s Kubernetes integration.
  • Container registry integrations - Snyk accesses and then stores a short-term copy of the container image (unless a broker is used). This copy is removed from the Snyk network after analysis.

Snyk Infrastructure as Code

Snyk Infrastructure as Code
  • CLI tests are performed locally. When results are shared with the Snyk platform via the --report option, resource configurations are also included.
  • SCM tests require access to your infrastructure as code files. Snyk stores them for the duration of the analysis and subsequently deletes them from the Snyk system. Snyk retains parsed resource configurations to provide context for issues and resources.
  • Terraform Cloud and Terraform Enterprise tests analyze plan files. Snyk removes secrets and sensitive values and retains resource configurations to provide context for issues and resources.
  • For drift detection via snyk iac describe, Snyk relies on the principle of least privilege and requires only read-only access to AWS, Azure, Google, or GitHub. Provider credentials are not sent to or stored by Snyk.
  • Snyk relies on local read-only Terraform State file access and extracts and sends relevant resource configuration data to the platform.


  • Snyk Cloud scans cloud platform APIs to gather information on configured infrastructure deployed in AWS Accounts and Google Cloud Subscriptions.
  • To perform scans, Snyk relies on the principle of least privilege, leveraging different authentication mechanisms which are supported by each Cloud platform.
    • For Amazon Web Services (AWS), a read-only AWS IAM role must be provisioned in your AWS Account(s) to provide secure access to required AWS APIs.
    • For Google Cloud, a read-only Google Cloud Service Account must be provisioned to enable secure access to required Google Cloud APIs.
  • During scans, Snyk gathers and stores a resource configuration state to perform analysis, and stores the results of that analysis, including the details of misconfigurations which result in issues.
  • Snyk Cloud retains resource configuration states found in scans to provide context for Issues and resources but does not store secrets or sensitive values.

Snyk integrations: Git repository cloning

This feature is in open beta for GitHub, GitHub Enterprise, GitLab, Bitbucket Server, Bitbucket Cloud App, Bitbucket Cloud (Legacy), and Azure Repos integrations.
Full Git repository cloning allows Snyk to provide more reliable and accurate results when scanning your source code through the SCM integrations, helping you develop fast and stay secure.

How Git cloning supports more reliable results

Traditionally, Snyk has accessed repository contents using SCM APIs, which impose primary and secondary rate limits, and content limits. For example, the APIs are rate-limited to allow only a certain number of requests per hour, and there is a limit on the number of tree entries that can be retrieved from the Git database.
When repository contents are retrieved over these APIs, these limitations inhibit Snyk’s providing a complete analysis in a number of ways, especially across a very large number of repositories, or for repositories containing more than 100,000 files, sometimes referred to as monorepos.
Through cloning, these limitations are removed.

How Git cloning supports more accurate results

The accuracy of results is improved in a number of ways through cloning. Since Snyk can access a complete view of a source code repository at a specific commit SHA, including repositories containing more than 100,000 files, the analysis is also more complete through cloning.

Snyk data ingestion

When Git repository cloning is enabled, Snyk will ingest, through configured SCM integrations, a temporary snapshot of repository contents at a given commit and all commit metadata (including the commit message, authors, and timestamp).

How Snyk processes this data

Snyk uses cloud products from Amazon Web Services (AWS) and Google Cloud Platform (GCP) to process and store the data in a cache.
Data is cached for 24 hours “per commit”, meaning that for every commit pushed to a repository that Snyk is tracking, the contents of that commit will be held in a cache for up to 24 hours. Multiple commits within a single 24-hour period will result in multiple caches with their own 24-hour lifecycle. At the end of each 24-hour lifecycle, the cache is automatically deleted according to cloud provider policies.

Safeguards Snyk puts in place to ensure data is secure

  • Snyk will perform a clone only when an SCM integration flow requires it, for example, PR check, import, and test.
  • Communication between the cloning service and cache is encrypted with TLS 1.2.
  • Cloned assets are deleted from the file system immediately after populating the cache.
  • The cache for a clone is deleted after a maximum of 24 hours.
  • All data is handled by Snyk in accordance with the SOC 2 standard. For more details, see Snyk certifications.
  • Your data is analyzed only for the purposes of improving code security and code quality and in accordance with your Data Processing Addendum.

Git repository cloning protocols

Repositories are cloned using HTTPS. SSH-based clones are currently unavailable.

Flows used in Git repository cloning

PR checks, import, and recurring tests will all make use of Git repository cloning for all Projects imported using an SCM integration.

Snyk Broker interactions

Brokered connections are supported when Git operations are allowed through Broker.
This will override restrictions from accept.json. For more information, see Clone capability with Broker for Docker.

Git cloning applicable contract terms

By enabling this feature, you agree that your Git repository is a Protected Asset as defined in the contract between your company and Snyk.

Snyk certifications

Soc 2 Type 2 AICPA Soc
Soc 2 Type 2 AICPA Soc
Snyk is certified to ISO 27001:2013 with the additional objective controls of ISO 27017:2015.
Coalfire ISO 27001 certified ISO
Coalfire ISO 27001 certified ISO

Snyk policies

For additional information, see the following pages on the Snyk website: