Skip to main content
In this lesson, we’ll explore Static Application Security Testing (SAST), also known as static analysis. SAST examines your source code to identify security vulnerabilities before runtime, scanning the application code and reporting potential issues. By contrast, Dynamic Application Security Testing (DAST) runs tests against a deployed application. For our SAST examples, we’ll use SonarQube.

​
Why SonarQube for SAST?

SonarQube is an open-source platform by SonarSource that performs continuous inspection of code quality through automatic static analysis. It gives you visibility into your code by pinpointing specific lines where issues occur and offering remediation guidance. You can also enforce quality gates—thresholds on code metrics—to ensure that every commit meets your organization’s standards.
The image is an informational slide about SonarQube, an open-source platform for code quality inspection, highlighting its benefits, problems it addresses, and solutions like quality gates. It includes a screenshot of a code analysis and a table of conditions on code metrics.

​
Defining Quality Gates

With quality gates, you can set conditions such as:
  • Number of code smells
  • Number of security hotspots
  • Code coverage percentage
If any condition fails, the build is marked as failed—blocking merges until all checks pass.

​
Installing SonarQube with Docker

A quick way to get SonarQube up and running is via the official Docker image. Run:
The environment variable SONAR_ES_BOOTSTRAP_CHECKS_DISABLE=true disables Elasticsearch bootstrap checks for development environments. Do not use this in production.
Once the container launches, tail the logs:
Sample output:
After SonarQube starts, open your browser to http://<your-host>:9000. The default credentials are admin/admin.

​
Next Steps

We will now integrate SonarQube into a Jenkins pipeline to automate static security analysis on every build.

Watch Video