Why Container supply chain security in GCP? - Purpose & Use Cases

The Big Idea

What if a tiny unnoticed flaw in your container could bring down your whole app?

The Scenario

Imagine you build a container image by manually downloading software from various websites, then packaging it yourself without checks.

You push this image to your cloud registry and deploy it to your app.

But what if some software was tampered with or had hidden vulnerabilities?

The Problem

Manually verifying every piece of software is slow and easy to miss problems.

Without automation, you risk deploying containers with malware or bugs.

This can cause outages, data leaks, or worse.

The Solution

Container supply chain security automates checks at every step.

It verifies software sources, scans images for vulnerabilities, and enforces policies before deployment.

This keeps your containers safe and trustworthy.

Before vs After

✗ Before

docker build .
docker push myregistry/myapp:latest

✓ After

gcloud builds submit --config=cloudbuild.yaml
# with automated scanning and signing steps

What It Enables

It enables confident, secure deployment of containers without manual guesswork or risk.

Real Life Example

A company uses Google Cloud Build with vulnerability scanning and binary authorization to ensure only safe container images run in production.

Key Takeaways

Manual container builds risk hidden vulnerabilities.

Supply chain security automates verification and scanning.

This protects apps and data from attacks and failures.

Practice

1. What is the main purpose of container supply chain security in Google Cloud?

easy

A. To automatically deploy containers to Kubernetes

B. To speed up container image downloads

C. To reduce the size of container images

D. To check every step from code to container for vulnerabilities

Solution

1. Step 1: Understand container supply chain security

   It focuses on protecting the app by verifying each step from code creation to container deployment.

2. Step 2: Identify the main goal

   The goal is to prevent vulnerabilities or bad code from reaching users by checking the entire build and deployment process.

3. Final Answer:

   To check every step from code to container for vulnerabilities -> Option D

4. Quick Check:

   Container supply chain security = check all steps [OK]

Hint: Focus on security checks from code to container [OK]

Common Mistakes:

• Thinking it only speeds up downloads
• Confusing with image size optimization
• Assuming it automatically deploys containers

2. Which Google Cloud service is primarily used to build, scan, and sign container images automatically?

easy

A. Cloud Build

B. Cloud Storage

C. Cloud Functions

D. Cloud Run

Solution

1. Step 1: Identify service for building and scanning containers

   Cloud Build is designed to automate building, scanning, and signing container images.

2. Step 2: Exclude other services

   Cloud Storage stores data, Cloud Functions run code, Cloud Run deploys containers but does not build or scan images.

3. Final Answer:

   Cloud Build -> Option A

4. Quick Check:

   Build and scan containers = Cloud Build [OK]

Hint: Remember: Build and scan = Cloud Build [OK]

Common Mistakes:

• Confusing Cloud Storage with build service
• Thinking Cloud Run builds images
• Assuming Cloud Functions handles container images

3. Given this Cloud Build YAML snippet, what will happen when the build runs?

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '-t', 'gcr.io/my-project/my-app', '.']
- name: 'gcr.io/cloud-builders/gcloud'
  args: ['container', 'images', 'scan', 'gcr.io/my-project/my-app']
images:
- 'gcr.io/my-project/my-app'

medium

A. Only builds the Docker image without scanning

B. Builds the Docker image and scans it for vulnerabilities

C. Scans the image before building it

D. Fails because scanning is not supported in Cloud Build

Solution

1. Step 1: Analyze the build steps

   The first step builds the Docker image tagged 'gcr.io/my-project/my-app'. The second step runs a scan on that image.

2. Step 2: Confirm scanning support

   Cloud Build supports scanning container images after building them using gcloud commands.

3. Final Answer:

   Builds the Docker image and scans it for vulnerabilities -> Option B

4. Quick Check:

   Build then scan = Builds the Docker image and scans it for vulnerabilities [OK]

Hint: Build first, then scan image in Cloud Build [OK]

Common Mistakes:

• Thinking scan happens before build
• Assuming scanning is unsupported
• Ignoring the order of steps

4. You wrote a Cloud Build config to scan container images, but the scan step fails with permission denied. What is the most likely fix?

medium

A. Change the image tag to a public registry

B. Increase the build timeout value

C. Grant Cloud Build service account the Container Analysis Viewer role

D. Remove the scan step from the build

Solution

1. Step 1: Identify cause of permission denied error

   Scanning container images requires permissions to access Container Analysis API data.

2. Step 2: Assign correct IAM role

   Granting the Cloud Build service account the Container Analysis Viewer role allows scanning without permission errors.

3. Final Answer:

   Grant Cloud Build service account the Container Analysis Viewer role -> Option C

4. Quick Check:

   Permission denied fix = assign Container Analysis Viewer role [OK]

Hint: Assign Container Analysis Viewer role to Cloud Build account [OK]

Common Mistakes:

• Increasing timeout does not fix permissions
• Changing image tag won't fix permission errors
• Removing scan step avoids problem but loses security

5. You want to ensure only signed container images are deployed to your GKE cluster. Which combination of GCP features should you use to enforce this?

hard

A. Binary Authorization with Cloud Build signing images

B. Cloud Run with automatic image scanning

C. Cloud Storage to store images and IAM policies

D. Cloud Functions to trigger deployment after scanning

Solution

1. Step 1: Understand requirement for signed images enforcement

   Binary Authorization lets you enforce policies that only allow signed images to deploy to GKE.

2. Step 2: Use Cloud Build to sign images

   Cloud Build can build and sign container images automatically, integrating with Binary Authorization.

3. Step 3: Exclude other options

   Cloud Run and Cloud Functions do not enforce signed image deployment. Cloud Storage is for storage, not enforcement.

4. Final Answer:

   Binary Authorization with Cloud Build signing images -> Option A

5. Quick Check:

   Signed image enforcement = Binary Authorization + Cloud Build [OK]

Hint: Use Binary Authorization plus signed images from Cloud Build [OK]

Common Mistakes:

• Confusing Cloud Run with enforcement tool
• Using Cloud Storage for enforcement
• Thinking Cloud Functions handle image signing