> [!CAUTION]
> **Caution:** Starting on July 23, 2024, container OS vulnerability scanning is deprecated and is scheduled for shutdown on July 31, 2025. Starting on June 16, 2025, Advanced Vulnerability Insights is deprecated and is scheduled for shutdown on June 16, 2026. For more information about deprecation and shutdown dates, see [Vulnerability scanning removal from GKE](https://docs.cloud.google.com/kubernetes-engine/docs/deprecations/vulnerability-scanning-gkee.md.txt).

This page describes workload vulnerability scanning, a feature of the Google Kubernetes Engine (GKE)
security posture dashboard. This feature helps you improve the security of your
deployments by automatically scanning for vulnerabilities in your container
images and language packages during runtime. You can view identified vulnerability
issues and recommended actions in the security posture dashboard.

This page is for Security specialists with information for making informed
decisions and details about using workload vulnerability scanning when
implementing a first-party vulnerability detection solution within Google Cloud. To learn more about
common roles and example tasks that we reference in Google Cloud content, see
[Common GKE user roles and tasks](https://docs.cloud.google.com/kubernetes-engine/enterprise/docs/concepts/roles-tasks.md.txt).

Before reading this page, ensure that you're familiar with information about how the security posture dashboard fits into your
security strategy by reading
[Usage as part of a broad security strategy](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-security-posture-dashboard.md.txt#broad-security-strategy).

## Types of vulnerability scanning

Workload vulnerability scanning includes the following capabilities:

- Container operating system (OS) vulnerability scanning
- Language package vulnerability scanning

If a vulnerability is found in your container images or language packages,
GKE displays the results in the security posture dashboard in
the Google Cloud console. GKE also adds entries to Cloud Logging
for auditing and traceability.

### Container OS vulnerability scanning

GKE continuously scans container images that run on enrolled
GKE clusters. GKE uses vulnerability data from
public CVE databases such as [NIST](https://nvd.nist.gov/vuln/search).
The images can come from any image registry. The OS version must be supported
for scanning. For a list of supported operating systems, see
[Supported Linux versions](https://docs.cloud.google.com/artifact-analysis/docs/os-overview#linux-versions).

For instructions, see
[Enable container OS vulnerability scanning](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/security-posture-vulnerability-scanning.md.txt#enable).

### Language package vulnerability scanning

GKE continuously scans containers for known vulnerabilities in
language packages, such as Go or Maven packages. We get vulnerability data
from public sources such as the
[GitHub Advisory Database](https://github.com/advisories).
The scanner is the Artifact Analysis scanner, which you can separately
implement to safeguard your Artifact Registry repositories. In the
security posture dashboard, the container images can come from any image
registry because GKE scans the images while the workloads run.
For information about Artifact Analysis scanning, see
[Types of scanning](https://docs.cloud.google.com/artifact-analysis/docs/scanning-types.md.txt).

GKE provides *continuous* scanning of your language packages
instead of only scanning on-demand or when your workflows push changes to your
container images. Continuous scanning ensures that you're notified of new
vulnerabilities as soon as fixes are available, which reduces your time to
discovery and remediation.

GKE scans the following language packages:

- Go
- Maven
- Javascript
- Python

Only vulnerabilities that have an associated CVE number are displayed in the
security posture dashboard.

## Enable vulnerability scanning in GKE

You can enable vulnerability scanning for GKE
clusters as follows:

| Tier | Enabled capabilities | GKE version requirement |
|---|---|---|
| [Standard](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/security-posture-vulnerability-scanning.md.txt#enable) `standard` | Container OS vulnerability scanning | - **GKE Enterprise edition**: Enabled by default in all new clusters running version 1.27 and later - **GKE Standard edition**: Disabled by default in all new clusters. |
| [Advanced vulnerability insights](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/security-posture-vulnerability-scanning.md.txt#enable-advanced-insights) `enterprise` | - Container OS vulnerability scanning - Language package vulnerability scanning | - **GKE Enterprise edition**: Enabled by default in all new clusters running version 1.27 and later - **GKE Standard edition**: Disabled by default in all new clusters. |

For enablement instructions, see
[Automatically scan workloads for known vulnerabilities](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/security-posture-vulnerability-scanning.md.txt).

## Pricing

For pricing information, see
[GKE security posture dashboard pricing](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-security-posture-dashboard.md.txt#pricing)

## What actions does GKE suggest?

Each vulnerability in the security posture dashboard has detailed information
such as the following:

- A full description of the vulnerability, including potential impact, attack pathways, and severity.
- Fixed packages and version numbers.
- Links to the relevant entries in public CVE databases.

GKE doesn't show a vulnerability if there is no corresponding
CVE with an actionable mitigation.

For an overview of the security posture dashboard interface, see
[About the security posture dashboard](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-security-posture-dashboard.md.txt#about-interface).

## Limitations

- GKE doesn't support scanning of proprietary packages and their dependencies.
- GKE only displays results for vulnerabilities that have an available fix and an available CVE number in the security posture dashboard. You might see more results, such as vulnerabilities without an available fix, if you scan the same container images in a container registry.
- GKE uses the following memory on each worker node for workload vulnerability scanning:
  - Container OS scanning: 50 MiB
  - Advanced vulnerability insights: 100 MiB
- GKE has the following limitations on the size of each file that contains package data in your images. GKE won't scan files that exceed the size limit.
  - Container OS scanning: 30 MiB
  - Advanced vulnerability insights: 60 MiB
- Windows Server containers aren't supported.
- Workload vulnerability scanning is only available for clusters with less than 1000 nodes.
- GKE doesn't scan nodes that use Arm architecture, such as the T2A machine type.
- The security posture dashboard supports up to 150,000 active
  workload vulnerability scanning findings for each cluster. When the number of
  findings for a cluster exceeds this maximum, the
  security posture dashboard stops showing vulnerability findings for that
  cluster.

  To resolve this issue, use a scanning mechanism at the registry level to
  identify vulnerabilities in images and apply patches. Alternatively, in a new
  cluster, deploy your workloads in batches to identify and mitigate
  vulnerabilities. When the number of vulnerability findings is less than
  150,000, the security posture dashboard starts displaying findings for the
  cluster.
- For each cluster, the GKE security posture database tracks all of the
  top-level workload objects in the Kubernetes API. For example, a Deployment
  that manages 20 replicas is tracked as a single object. A static Pod is also a
  single object.

  The database can process up to 5,000 object deletion and creation operations
  in a single transaction. For example, deleting a Deployment is a single
  operation, and re-creating a static Pod is two operations (deletion and
  creation). If the number of operations exceeds 5,000, the
  security posture dashboard stops showing findings for that cluster.

  If your dashboard isn't updating, and you recently scaled the number of
  top-level workloads in your cluster, you can
  [create a support case with Cloud Customer Care](https://docs.cloud.google.com/support/docs/customer-care-procedures.md.txt#create_a_support_case)
  to reset the database state.

## What's next

- [Enable and use workload vulnerability scanning](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/security-posture-vulnerability-scanning.md.txt)
- [Learn about other scanning capabilities in the security posture dashboard](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/about-security-posture-dashboard.md.txt#how-it-works)