Enable Artifact Analysis scanning for Artifact Registry container images

How it is checked

Audit method: Shell command

v=$(gcloud services list --enabled ${GKE_PROJECT:+--project=$GKE_PROJECT} --filter='config.name=containerscanning.googleapis.com' --format='value(config.name)') || exit 1
if [ "$v" = containerscanning.googleapis.com ]; then echo compliant; else echo "noncompliant: Container Scanning API disabled"; fi

Expected output

compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Enable Artifact Analysis automatic vulnerability scanning for container images stored in Artifact Registry and used by GKE Autopilot workloads. Enabling the Container Scanning API activates automatic scanning for images pushed to standard and remote Docker repositories in Artifact Registry, and it also enables the Container Analysis API for vulnerability metadata storage and retrieval. Enable the required project APIs: gcloud services enable artifactregistry.googleapis.com containerscanning.googleapis.com \ --project=$PROJECT_ID If scanning was disabled on a specific Artifact Registry repository, update the repository to allow vulnerability scanning: gcloud artifacts repositories update $REPOSITORY \ --project=$PROJECT_ID \ --location=$LOCATION \ --allow-vulnerability-scanning Note: Repeat the repository update command for each Docker repository that stores images deployed to GKE ...

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

tmaegis scan --target gke-autopilot --level 2