Container security basics in Cybersecurity - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of container security?

Containers are widely used to package applications. What is the main goal of container security?

A To protect the containerized application and its environment from unauthorized access and vulnerabilities

B To increase the speed of container startup times

C To reduce the size of container images for faster downloads

D To automate the deployment of containers across multiple servers

💡 Hint

Think about what security means in the context of software running inside containers.

Container security focuses on protecting the container and its environment from threats like unauthorized access, vulnerabilities, and attacks. Speed or automation are important but not the main goal of security.

📋 Factual

intermediate

Which of these is a common container security risk?

Identify a typical security risk associated with containers.

A Deploying containers without a network connection

B Using containers only on local machines

C Running containers with root privileges inside the container

D Using containers with minimal resource limits

💡 Hint

Consider what happens if a container runs with too many permissions.

Running containers with root privileges inside the container can allow attackers to gain full control if they exploit vulnerabilities. This is a common security risk.

🔍 Analysis

advanced

What is the effect of using a minimal base image for containers on security?

Analyze how choosing a minimal base image impacts container security.

A It has no impact on security but improves performance

B It increases the risk because minimal images lack security patches

C It makes containers incompatible with most cloud platforms

D It reduces the attack surface by including fewer packages and dependencies

💡 Hint

Think about how fewer components affect vulnerabilities.

Minimal base images contain fewer software packages, which means fewer potential vulnerabilities. This reduces the attack surface and improves security.

❓ Reasoning

advanced

Why is scanning container images for vulnerabilities important before deployment?

Explain the reason for scanning container images for vulnerabilities before deploying them.

A To check if the image size meets deployment limits

B To detect known security issues in the image that could be exploited

C To verify the image runs faster on the target system

D To ensure the image uses the latest programming language version

💡 Hint

Consider what vulnerabilities in software images can cause.

Scanning images helps find known security flaws before deployment, preventing attackers from exploiting them in production.

❓ Comparison

expert

Which container isolation method provides the strongest security boundary?

Compare these container isolation methods and select the one that offers the strongest security boundary.

A Running containers inside virtual machines

B Using Linux namespaces and cgroups alone

C Sharing the host kernel without additional isolation

D Running containers as privileged processes on the host

💡 Hint

Think about how virtual machines differ from containers in isolation.

Running containers inside virtual machines adds an extra layer of isolation by separating the container from the host kernel, providing stronger security boundaries than namespaces and cgroups alone.

Practice

1. What is the main reason containers need special security measures?

easy

A. Containers automatically encrypt all data without configuration

B. Containers are always offline and isolated from networks

C. Containers do not run any applications

D. Containers share the host OS, so vulnerabilities can affect the whole system

Solution

1. Step 1: Understand container architecture

   Containers share the host operating system kernel, unlike virtual machines which have separate OS instances.

2. Step 2: Identify security risk from shared OS

   Because containers share the OS, a vulnerability in one container can potentially affect others or the host.

3. Final Answer:

   Containers share the host OS, so vulnerabilities can affect the whole system -> Option D

4. Quick Check:

   Shared OS = Need special security [OK]

Hint: Remember: shared OS means shared risk [OK]

Common Mistakes:

• Thinking containers are fully isolated like virtual machines
• Assuming containers do not run apps
• Believing containers encrypt data by default

2. Which of the following is the correct command to scan a Docker container image for vulnerabilities?

easy

A. docker push <image_name>

B. docker scan <image_name>

C. docker run <image_name>

D. docker build <image_name>

Solution

1. Step 1: Identify scanning command

   The docker scan command is used to check container images for known security issues.

2. Step 2: Differentiate from other commands

   docker build creates images, docker run starts containers, and docker push uploads images to a registry.

3. Final Answer:

   docker scan <image_name> -> Option B

4. Quick Check:

   Scan command = docker scan [OK]

Hint: Scan images with 'docker scan' command [OK]

Common Mistakes:

• Confusing build or run commands with scanning
• Using push command to scan images
• Not specifying image name with scan

3. Consider this Dockerfile snippet:

FROM alpine:latest
RUN apk add --no-cache curl
CMD ["curl", "http://example.com"]

What is the main security risk in this container setup?

medium

A. The CMD command is incorrect syntax

B. Alpine Linux is not supported for containers

C. Using the latest tag can introduce untested vulnerabilities

D. The container does not expose any ports

Solution

1. Step 1: Analyze the use of 'latest' tag

   Using 'latest' means the image can change over time, possibly introducing new vulnerabilities without notice.

2. Step 2: Check other options for correctness

   CMD syntax is correct, Alpine is a common lightweight base image, and not exposing ports is not a risk itself.

3. Final Answer:

   Using the latest tag can introduce untested vulnerabilities -> Option C

4. Quick Check:

   Latest tag = potential risk [OK]

Hint: Avoid 'latest' tag for stable security [OK]

Common Mistakes:

• Thinking CMD syntax is wrong
• Believing Alpine is insecure by default
• Assuming no exposed ports means no risk

4. You have a container running with root privileges. Which change improves security the most?

medium

A. Run the container as a non-root user

B. Increase the container's CPU limits

C. Add more environment variables

D. Use the host network mode

Solution

1. Step 1: Understand privilege risks

   Running containers as root can allow attackers to gain full control if compromised.

2. Step 2: Identify best security practice

   Running as a non-root user limits permissions and reduces damage from attacks.

3. Final Answer:

   Run the container as a non-root user -> Option A

4. Quick Check:

   Non-root user = better security [OK]

Hint: Never run containers as root user [OK]

Common Mistakes:

• Thinking CPU limits improve security
• Adding environment variables does not secure
• Using host network mode increases risk

5. You want to securely store API keys inside a container without exposing them in the image or logs. Which approach is best?

hard

A. Use Docker secrets or environment variables managed outside the image

B. Hardcode the keys in the Dockerfile

C. Print keys in container logs for easy access

D. Store keys in a public GitHub repository

Solution

1. Step 1: Identify secure secret management

   Docker secrets or environment variables injected at runtime keep keys out of images and logs.

2. Step 2: Evaluate insecure options

   Hardcoding keys, logging them, or storing publicly exposes secrets to attackers.

3. Final Answer:

   Use Docker secrets or environment variables managed outside the image -> Option A

4. Quick Check:

   External secret management = secure keys [OK]

Hint: Keep secrets outside images and logs [OK]

Common Mistakes:

• Hardcoding secrets in Dockerfile
• Logging secrets accidentally
• Publishing secrets publicly