Container vulnerability scanning in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to trigger vulnerability scanning on a Google Cloud container image.

GCP

gcloud container images scan [1]

Drag options to blanks, or click blank then click option'

Agcr.io/my-project/my-image@sha256:abc123

Bgcr.io/my-project/my-image:latest

Cgcr.io/my-project/my-image:vuln-scan

Dgcr.io/my-project/my-image:scan

Attempts:

3 left

💡 Hint

Common Mistakes

Using a tag like ':latest' instead of the image digest.

Using a non-existent tag for scanning.

The command scans the image by its digest to ensure the exact image is scanned for vulnerabilities.

2fill in blank

medium

Complete the command to list vulnerability scans for a container image in Google Cloud.

GCP

gcloud container images [1] gcr.io/my-project/my-image@sha256:abc123 --format=json

Drag options to blanks, or click blank then click option'

Adescribe

Blist-vulnerabilities

Clist-tags

Dlist-scans

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'list-tags' which only lists image tags.

Using 'describe' which shows metadata but not vulnerabilities.

The 'list-vulnerabilities' command shows vulnerability scan results for the specified image.

3fill in blank

hard

Complete the command to trigger vulnerability scanning on a container image.

GCP

gcloud container images [1] gcr.io/my-project/my-image:latest

Drag options to blanks, or click blank then click option'

Ascan-enable

Bvulnerability-scan

Cenable-scanning

Dscan

Attempts:

3 left

💡 Hint

Common Mistakes

Using made-up subcommands like 'scan-enable'.

Using incorrect subcommands like 'vulnerability-scan'.

The correct subcommand to trigger scanning is 'scan'. Other options are invalid commands.

4fill in blank

hard

Fill in the blank to create a filter that lists only HIGH severity vulnerabilities for a container image.

GCP

gcloud container images list-vulnerabilities gcr.io/my-project/my-image@sha256:abc123 --filter='severity[1]HIGH'

Drag options to blanks, or click blank then click option'

A==

B!=

C:

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using single '=' which is invalid in gcloud filters.

Using ':' which is for substring matching, not exact equality.

The filter uses 'severity==HIGH' to specify exact match on HIGH severity.

5fill in blank

hard

Fill all three blanks to create a command that lists vulnerability scan results in JSON format.

GCP

gcloud container images [1] gcr.io/my-project/my-image@sha256:abc123 --[2] json --[3]

Drag options to blanks, or click blank then click option'

Alist-vulnerabilities

Bformat

Cscan-enable

Dquiet

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'scan-enable' as the action instead of 'list-vulnerabilities'.

Omitting '--quiet' which may cause interactive prompts.

The command lists vulnerabilities, formats output as JSON, and uses quiet mode to suppress prompts.

Practice

1. What is the main purpose of container vulnerability scanning in Google Cloud Platform?

easy

A. To find security issues in container images before deployment

B. To increase the speed of container startup

C. To reduce the size of container images

D. To monitor container CPU usage

Solution

1. Step 1: Understand container vulnerability scanning

   It is a process to detect security problems in container images.

2. Step 2: Identify the main goal in GCP context

   GCP uses scanning to find vulnerabilities before containers run, keeping apps safe.

3. Final Answer:

   To find security issues in container images before deployment -> Option A

4. Quick Check:

   Purpose = Find security issues [OK]

Hint: Focus on security purpose, not performance or size [OK]

Common Mistakes:

• Confusing scanning with performance monitoring
• Thinking scanning reduces image size
• Assuming scanning manages CPU usage

2. Which gcloud command correctly scans a container image named gcr.io/my-project/my-image:latest for vulnerabilities?

easy

A. gcloud container images describe gcr.io/my-project/my-image:latest --show-vulnerabilities

B. gcloud container images scan gcr.io/my-project/my-image:latest

C. gcloud container images list-tags gcr.io/my-project/my-image:latest --vulnerabilities

D. gcloud container images scan-vulnerabilities gcr.io/my-project/my-image:latest

Solution

1. Step 1: Recall correct gcloud syntax for vulnerability scanning

   The command to view vulnerabilities is gcloud container images describe with --show-vulnerabilities.

2. Step 2: Check each option's validity

   gcloud container images describe gcr.io/my-project/my-image:latest --show-vulnerabilities matches the correct syntax; others are invalid or do not exist.

3. Final Answer:

   gcloud container images describe gcr.io/my-project/my-image:latest --show-vulnerabilities -> Option A

4. Quick Check:

   Correct command = describe + --show-vulnerabilities [OK]

Hint: Use 'describe' with '--show-vulnerabilities' to scan images [OK]

Common Mistakes:

• Using non-existent 'scan' command
• Confusing 'list-tags' with scanning
• Omitting the '--show-vulnerabilities' flag

3. Given the command gcloud container images describe gcr.io/my-project/app:1.0 --show-vulnerabilities, what output should you expect if the image has no vulnerabilities?

medium

A. A list of vulnerabilities with severity levels

B. An error saying image not found

C. A summary of image size and tags only

D. An empty vulnerabilities section or message indicating no issues

Solution

1. Step 1: Understand the command's purpose

   The command shows vulnerability details for the specified image.

2. Step 2: Predict output when no vulnerabilities exist

   The output will show an empty vulnerabilities section or a message indicating no issues found.

3. Final Answer:

   An empty vulnerabilities section or message indicating no issues -> Option D

4. Quick Check:

   No vulnerabilities = empty or no issues message [OK]

Hint: No vulnerabilities means empty or no issues message [OK]

Common Mistakes:

• Expecting a list when none exist
• Confusing errors with no vulnerabilities
• Looking for unrelated image metadata

4. You run gcloud container images describe gcr.io/my-project/app:latest --show-vulnerabilities= but get an error: ERROR: (gcloud.container.images.describe) argument --show-vulnerabilities: Expected bool value. What is the likely cause?

medium

A. The image name is incorrect

B. You need to authenticate with gcloud first

C. You forgot to provide a value for --show-vulnerabilities flag

D. The command does not support vulnerability scanning

Solution

1. Step 1: Analyze the error message

   The error says the flag --show-vulnerabilities expects a boolean value (true or false).

2. Step 2: Identify the command mistake

   The flag was used without specifying true or false, causing the error.

3. Final Answer:

   You forgot to provide a value for --show-vulnerabilities flag -> Option C

4. Quick Check:

   Flag needs true/false value [OK]

Hint: Always provide true or false for boolean flags [OK]

Common Mistakes:

• Omitting the boolean value for flags
• Assuming image name causes this error
• Ignoring authentication errors

5. You want to automate vulnerability scanning for all container images pushed to your GCP project. Which approach best ensures every new image is scanned automatically?

hard

A. Manually run gcloud container images describe --show-vulnerabilities after each push

B. Set up Container Analysis API for automatic scanning of images on push

C. Use Stackdriver logs to detect image pushes and scan images manually

D. Schedule a daily cron job to scan all images regardless of push events

Solution

1. Step 1: Understand automation needs for scanning

   Automatic scanning requires integration with image push events.

2. Step 2: Evaluate options for automatic scanning

   Container Analysis API automatically scans images on push, ensuring no image is missed.

3. Step 3: Compare alternatives

   Manual commands or cron jobs are less efficient and risk missing images or delays.

4. Final Answer:

   Set up Container Analysis API for automatic scanning of images on push -> Option B

5. Quick Check:

   Automate scanning on push = Container Analysis API [OK]

Hint: Use triggers to scan images automatically on push [OK]

Common Mistakes:

• Relying on manual scanning after push
• Using logs instead of triggers for automation
• Scheduling scans without event triggers