Achieve DevSecOps with Bitbucket Pipelines and Snyk Pipe

This tutorial outlines how to secure your build workflow on Bitbucket Pipelines with Snyk. An important step in securing your environment is to scan and analyze both your application and Linux-based container project for known vulnerabilities, which helps you identify and mitigate security vulnerabilities. The exercises in this tutorial will help secure your application and container by leveraging the Snyk Pipe for Bitbucket Pipelines to scan the application manifest file and the container base image for its dependencies. 

The tutorial, How Snyk and Bitbucket Cloud enable DevSecOps, focused on application dependencies. However, by also scanning your container base image you can detect: 

• The operating system (OS) packages installed and managed by the package manager
• Key binaries —layers that were not installed through the package manager

Based on these results, Snyk provides advice and guidance, including:

• Origins of the vulnerabilities in OS packages and key binaries
• Base image upgrade details or a recommendation to rebuild the image
• Dockerfile layer where the affected package was introduced
• Fixed-in version of the operating system and key binary packages

Audience:

• Developers
• Security/application teams
• DevOps/DevSecOps engineers

Prerequisites:

You have a Snyk and Atlassian Bitbucket account.

• Register for a free Snyk account here.
• Log in to your Snyk account here.
• Register for a free Atlassian account here.
• Log in to your Atlassian account here.

This example leverages the Snyk Scan pipe in the pipeline to perform a scan of the application. The source contains a complete, YAML definition of all supported variables, but only those included in this snippet are necessary for this purpose.

Here’s a closer look at a few of these:

1. SNYK_TOKEN is passed into the pipe as a repository variable previously defined in the [Bitbucket Configuration] module.

2. PROJECT_FOLDER is the folder where the project resides and normally defaults to. However, in this example, we set this to app/goof and pass this as an artifact to other steps in ther pipeline.

3. CODE_INSIGHTS_RESULTS defaults to false. However, since we want to create a Code Insight report with Snyk test results, set this to true.

4. SEVERITY_THRESHOLD reports on issues equal or higher to the provided level. The default is low. But in this case, we are interested only in high, so we defined this variable accordingly.

5. The DONT_BREAK_BUILD default is false, which is expected. Under normal circumstances, you would want to break the build if issues are found. However, for the purpose of this learning exercise, set this to true.

By 2022, more than 75 percent of global organizations will run containerized applications in production (Gartner). Alongside widespread adoption, there has been a surge in container vulnerabilities, with a four-times increase in reported operating system vulnerabilities in 2018. And yet 80 percent of developers say they don’t test their container images during development. They either say it’s not their responsibility or they are accustomed to someone down the road catching issues, which makes scaling container security a challenge for fast-growing businesses.

This is building the container image and tagging it, then leveraging the Snyk Scan pipe in the pipeline to perform a scan of the container image. Keep the same values for CODE_INSIGHTS_RESULTS, SEVERITY_THRESHOLD and DONT_BREAK_BUILD. This also passes a few additional supported variables relevant for the Snyk Pipe in order to understand the request for a container image scan instead of an application scan. These are namely setting LANGUAGE to docker, declaring the IMAGE_NAME, and passing the appropriate repository variable, as well as setting the TARGET_FILE to Dockerfile.

Your pipeline now scans the container image for known vulnerabilities, as well as your application code.

See more integrations for Atlassian Open DevOps