Question

Difficulty: MediumVulnerability Scanning, Container Security, and Threat Detection

Match each Google Cloud security product or feature to its corresponding container vulnerability management or threat detection role within an enterprise architecture.

  • Binary AuthorizationEnforces deploy-time signature validation policies to block unverified container images from being scheduled on GKE clusters.
  • Event Threat Detection (ETD)Analyzes Cloud Logging streams near real-time across the organization to detect threats like crypto-mining, data exfiltration, or anomalous IAM usage.
  • Artifact Registry Vulnerability ScanningScans container image layers stored in repositories for known CVE vulnerabilities upon upload and continuously as vulnerability databases update.
  • Container Threat Detection (CTD)Monitors kernel-level telemetry and container runtime execution inside GKE nodes to detect reverse shells, unauthorized binaries, and runtime anomalies.

Answer

Binary Authorization matches deploy-time signature verification policies; Event Threat Detection matches organization-wide log stream threat analysis; Artifact Registry Vulnerability Scanning matches container image CVE monitoring; Container Threat Detection matches kernel-level GKE node runtime monitoring.
Each service addresses a distinct phase in the container lifecycle: Artifact Registry Vulnerability Scanning handles repository inspection, Binary Authorization enforces deployment policy gates, Container Threat Detection monitors live GKE container runtimes, and Event Threat Detection monitors GCP audit and stream logs across the organization.

Step-by-Step Solution

1
Identify the deploy-time prevention control.
Binary Authorization requires attestations before image deployment on GKE.
Prevents unsigned or unauthorized container builds from running in production environments.
2
Distinguish between log analysis and node kernel runtime inspection.
Event Threat Detection analyzes Cloud Logging log events, whereas Container Threat Detection monitors low-level kernel activities inside GKE worker nodes.
Security Command Center separates log-based threat detection (ETD) from active node workload runtime detection (CTD).
3
Identify image repository scanning controls.
Artifact Registry Vulnerability Scanning handles pre-deployment CVE detection directly within the image storage registry.
Ensures container images are evaluated for software vulnerabilities before deployment.

Key Concept

Defense-in-depth container security, vulnerability scanning, and threat detection in GCP
Rate this question