QuestionQ43

Securing communications and establishing boundary protection

Your organization is concerned by recent news headlines about vulnerabilities in production applications that have resulted in security breaches. You want to automatically scan your deployment pipeline for vulnerabilities and ensure that only scanned and verified containers can run in the environment. What should you do?

  • A Use Kubernetes role-based access control (RBAC) as the source of truth for cluster access by granting “container.clusters.get” to limited users. Restrict deployment access by allowing these users to generate a kubeconfig file containing the configuration access to the GKE cluster.
  • B Use gcloud artifacts docker images describe LOCATION-docker.pkg.dev/PROJECT_ID/REPOSITORY/IMAGE_ID@sha256:HASH --show-package-vulnerability in your CI/CD pipeline, and trigger a pipeline failure for critical vulnerabilities.
  • C Enforce the use of Cloud Code for development so users receive real-time security feedback on vulnerable libraries and dependencies before they check in their code.
  • D Enable Binary Authorization and create attestations of scans.
Explanation

Binary Authorization can enforce a deployment policy requiring attestations that certify a container image completed a vulnerability scan. At deployment time, it verifies the required attestations and permits only verified images to run; images without valid required attestations can be blocked.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!