Advanced Security

Introduction to Container Scanning

In this course, you'll learn how SonarQube container scanning finds vulnerabilities and malicious packages in the container images you ship. You'll also learn how to run scans locally or in your CI/CD pipeline and manage findings in SonarQube Cloud.

Transcript

You already check the code you write with SonarQube. And with SonarQube Advanced Security, you can scan the dependencies you import, too. But what about the container images you ship? They include three types of components: operating system packages, language runtimes, and libraries that might not be in your repository. That’s where container scanning comes in. SonarQube Advanced Security scans images for known vulnerabilities and malicious packages. Take PHP2Shell: In October 2026, two critical PHP vulnerabilities known as PHP2Shell were disclosed that let attackers run code remotely on servers without logging in. Now that patches are available, the container scanner will flag a scanned image that contains these vulnerabilities. Container scanning fits how you already work. You can run a scan locally or add it to your CI/CD pipeline. And you don’t have to rescan an unchanged image to catch new problems. SonarQube Cloud keeps checking your analyzed images for newly disclosed security risks. When your scan completes, you can review and manage your findings directly within SonarQube Cloud. Ship every image with confidence. Container scanning catches known vulnerabilities and malicious packages before they ship. Learn more at sonar.com.