Security benchmarks (CIS Docker) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to scan Docker images using the CIS benchmark tool.

Docker

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock [1]

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

Anginx

Bubuntu

Ccisecurity/cis-docker-benchmark

Dalpine

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated images like 'ubuntu' or 'nginx' which do not perform CIS scans.

The official CIS Docker Benchmark image is 'cisecurity/cis-docker-benchmark' which scans Docker images for security compliance.

2fill in blank

medium

Complete the command to run the CIS Docker Benchmark with verbose output.

Docker

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock cisecurity/cis-docker-benchmark [1]

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

A--help

B--quiet

C--silent

D--verbose

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--quiet' or '--silent' which reduce output instead of increasing it.

The '--verbose' flag enables detailed output during the CIS Docker Benchmark scan.

3fill in blank

hard

Fix the error in this Docker CIS benchmark command to correctly mount the Docker socket.

Docker

docker run --rm -v [1]:/var/run/docker.sock cisecurity/cis-docker-benchmark

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

A/var/run/docker.sock

B/docker.sock

C/var/lib/docker.sock

D/run/docker.sock

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect paths like '/docker.sock' or '/var/lib/docker.sock' which do not exist.

The Docker socket is located at '/var/run/docker.sock' on the host and must be mounted to the same path inside the container.

4fill in blank

hard

Fill both blanks to create a Docker command that runs the CIS benchmark and saves the report to a local directory.

Docker

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v [1]:/report cisecurity/cis-docker-benchmark [2]

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

A/home/user/cis_reports

B--output

C--save

D/tmp/reports

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect flags like '--save' which is not supported.

Mounting wrong directories that do not exist.

Mount the local directory '/home/user/cis_reports' to '/report' in the container and use the '--output' flag to save the report.

5fill in blank

hard

Fill all three blanks to create a command that runs the CIS Docker Benchmark, outputs in JSON format, and saves the report to a mounted directory.

Docker

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v [1]:/report cisecurity/cis-docker-benchmark [2] [3]

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

A/var/lib/cis_reports

B--output

Cjson

D--format

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up '--output' and '--format' flags.

Using unsupported output formats.

Mount '/var/lib/cis_reports' to '/report', use '--output' to specify saving, and '--format' to set output format like 'json'.

Practice

1. What is the main purpose of the CIS Docker Security Benchmark?

easy

A. To provide guidelines for securing Docker containers

B. To speed up Docker container startup time

C. To increase Docker image size for better performance

D. To automate Docker container deployment

Solution

1. Step 1: Understand CIS Docker Benchmark purpose

   The CIS Docker Security Benchmark is designed to help users secure Docker containers by providing best practice guidelines.

2. Step 2: Compare options with purpose

   Options B, C, and D relate to performance or automation, not security guidelines.

3. Final Answer:

   To provide guidelines for securing Docker containers -> Option A

4. Quick Check:

   Security guidelines = A [OK]

Hint: CIS benchmarks focus on security rules and best practices [OK]

Common Mistakes:

• Confusing security with performance improvements
• Thinking CIS automates deployment
• Assuming CIS increases image size

2. Which command runs the Docker Bench Security script to check your Docker host against CIS benchmarks?

easy

A. docker bench run security

B. docker run --rm -it docker/docker-bench-security

C. docker security scan bench

D. docker run bench-security

Solution

1. Step 1: Recall the official Docker Bench Security command

   The correct command is to run the official Docker image with docker run --rm -it docker/docker-bench-security.

2. Step 2: Check other options for syntax errors or invalid commands

   Options B, C, and D are not valid Docker commands or do not match the official usage.

3. Final Answer:

   docker run --rm -it docker/docker-bench-security -> Option B

4. Quick Check:

   Official Docker Bench command = A [OK]

Hint: Use official Docker image with docker run --rm -it [OK]

Common Mistakes:

• Using incorrect or incomplete docker run syntax
• Assuming 'docker bench' is a built-in command
• Mixing up command order or flags

3. After running Docker Bench Security, you see this output line:
[WARN] 4.1 - Ensure that containers are not running in privileged mode
What does this warning mean?

medium

A. Containers are using too much CPU

B. Containers are missing network access

C. Containers are running with extra permissions that can be risky

D. Containers are not logging output

Solution

1. Step 1: Understand privileged mode in Docker

   Privileged mode gives containers extended permissions on the host, which can be a security risk.

2. Step 2: Interpret the warning message

   The warning indicates containers are running with these risky extra permissions.

3. Final Answer:

   Containers are running with extra permissions that can be risky -> Option C

4. Quick Check:

   Privileged mode risk = C [OK]

Hint: Privileged mode means extra risky permissions [OK]

Common Mistakes:

• Confusing privileged mode with resource usage
• Thinking it relates to network or logging
• Ignoring security implications of privileged mode

4. You ran Docker Bench Security and got this error:
ERROR: 5.1 - Ensure Docker daemon is configured to use user namespaces: Not configured
How can you fix this issue?

medium

A. Restart Docker containers without changes

B. Remove all Docker images and rebuild

C. Increase Docker daemon CPU limits

D. Enable user namespaces in the Docker daemon configuration file

Solution

1. Step 1: Understand user namespaces in Docker

   User namespaces isolate container users from host users, improving security.

2. Step 2: Fix the error by enabling user namespaces

   This requires editing the Docker daemon config (e.g., /etc/docker/daemon.json) to enable user namespaces and restarting Docker.

3. Final Answer:

   Enable user namespaces in the Docker daemon configuration file -> Option D

4. Quick Check:

   User namespaces fix = B [OK]

Hint: Enable user namespaces in daemon config to fix error [OK]

Common Mistakes:

• Restarting containers without config changes
• Changing CPU limits unrelated to namespaces
• Deleting images instead of fixing config

5. You want to improve your Docker host security by applying CIS Docker Benchmark recommendations. Which combination of actions is best?

hard

A. Run Docker Bench Security regularly, fix warnings, and restrict container privileges

B. Only update Docker to the latest version and ignore warnings

C. Disable Docker logging to improve performance and skip scans

D. Run containers as root for easier management and skip security checks

Solution

1. Step 1: Identify best practices from CIS Docker Benchmark

   Regular scanning, fixing warnings, and limiting container privileges are key security steps.

2. Step 2: Evaluate other options for security risks

   Options A, B, and C ignore warnings or increase risks by disabling logs or running as root.

3. Final Answer:

   Run Docker Bench Security regularly, fix warnings, and restrict container privileges -> Option A

4. Quick Check:

   Regular scans + fixes + least privilege = D [OK]

Hint: Scan often, fix issues, and limit privileges for best security [OK]

Common Mistakes:

• Ignoring warnings thinking updates are enough
• Disabling logs reduces visibility and security
• Running containers as root increases risk