Container supply chain security in GCP - Time & Space Complexity

Time Complexity: Container supply chain security

O(n)

Understanding Time Complexity

We want to understand how the time needed to secure container supply chains changes as we add more containers or steps.

Specifically, how does the number of security checks and scans grow when the supply chain grows?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Pseudocode for container supply chain security steps
for each container_image in container_images_list:
  scan container_image for vulnerabilities
  verify container_image signature
  deploy container_image if checks pass

This sequence scans and verifies each container image before deployment to ensure security.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Scanning and verifying each container image.
• How many times: Once per container image in the list.

How Execution Grows With Input

As the number of container images increases, the total number of scans and verifications grows proportionally.

Input Size (n)	Approx. Api Calls/Operations
10	10 scans + 10 verifications = 20 operations
100	100 scans + 100 verifications = 200 operations
1000	1000 scans + 1000 verifications = 2000 operations

Pattern observation: The operations increase directly with the number of container images.

Final Time Complexity

Time Complexity: O(n)

This means the time to secure the supply chain grows linearly with the number of container images.

Common Mistake

[X] Wrong: "Adding more container images won't affect the total security check time much because scans run fast."

[OK] Correct: Each container image requires its own scan and verification, so total time adds up directly with more images.

Interview Connect

Understanding how security steps scale helps you design systems that stay safe even as they grow.

This skill shows you can think about real-world cloud security challenges clearly and simply.

Self-Check

"What if we introduced parallel scanning for container images? How would the time complexity change?"

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