An online gaming enterprise hosts multiplayer matchmaking services on Google Kubernetes Engine (GKE) and stores container images in Artifact Registry. The lead security architect must design a container security strategy to achieve two goals: automatically scan container images for operating system vulnerabilities immediately upon push to the registry, and continuously detect runtime container compromises (such as unexpected binary execution or reverse shells) without deploying or managing security monitoring agents on cluster nodes. Which architectural approach fulfills these security and operational requirements?
- Enable Container Analysis vulnerability scanning on Artifact Registry, enforce deployment controls with Binary Authorization, and enable Container Threat Detection in Security Command Center Premium.Cevap
- BConfigure VPC Service Controls around Artifact Registry, grant the primitive Owner role to cluster node service accounts, and rely on standard Cloud Logging export rules to identify runtime anomalies.
- CGrant the Service Account Admin role to GKE deployment pipelines to allow image scanning, and deploy custom daemonsets on GKE nodes to capture low-level system calls for threat monitoring.
- DImplement VPC Service Controls to restrict image downloads, restrict master access using Private Cluster authorized networks, and run manual vulnerability scripts during image builds.
Cevap
Enable Container Analysis vulnerability scanning on Artifact Registry, enforce deployment controls with Binary Authorization, and enable Container Threat Detection in Security Command Center Premium.
The combination of Container Analysis (for automatic Artifact Registry image vulnerability scanning) and Security Command Center Premium Container Threat Detection (for agentless runtime threat monitoring via node hypervisor logs) delivers end-to-end security compliance with zero agent management overhead.
Adım Adım Çözüm
Anahtar Kavram
Container Security Pipeline & Agentless Threat Detection