Get startedGet started for free

Vulnerability scanning

1. Vulnerability scanning

Vulnerability management is a critical aspect of maintaining a strong security posture in GKE. It involves continuously identifying and addressing security weaknesses in your container images, operating systems, and application dependencies. By proactively managing vulnerabilities, you can minimize the risk of exploitation and protect your workloads from potential threats. Let's examine the vulnerability scanning process. Vulnerability scanning tools can be integrated into your CI/CD pipeline to identify vulnerabilities early in the development process. This allows you to address security issues before they reach production environments. The first phase is the build phase. When developers commit code, the CI/CD pipeline builds the container image. Immediately after the build, workload vulnerability scanning tools, like those leveraging Artifact Analysis, analyze the image. This includes OS package scanning and, with Advanced Vulnerability Insights, or AVI, language package scanning. AVI extends GKE's vulnerability scanning capabilities to include language packages within your containerized applications. It scans for known vulnerabilities in libraries and dependencies used by programming languages like Go, Maven, JavaScript, and Python. Many vulnerabilities in runtime environments reside within these language packages, not just the underlying OS. The next phase is scanning. Tools integrated into the pipeline scan the OS and language-specific packages of application dependencies for vulnerabilities. These tools often leverage the Artifact Analysis feature. After scanning has completed, the CI/CD pipeline can use security policies to stop the build if critical vulnerabilities are detected, generate reports detailing vulnerabilities and their severity, trigger automated remediation steps, or create tickets from manual fixes. If the image passes the security checks, it's stored in a container registry, like Artifact Registry. It is a recommended best practice to automate vulnerability scans to ensure regular and consistent checks for new vulnerabilities. This can be achieved through scheduled scans or by triggering scans on image updates.

2. Let's practice!

Create Your Free Account

or

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.