Container security basics in Cybersecurity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the sentence to define a container in simple terms.

Cybersecurity

A container is a [1] that packages an application and its dependencies together.

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

Anetwork protocol

Bvirtual machine

Cphysical server

Dlightweight unit

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing containers with virtual machines

Thinking containers are physical devices

A container is a lightweight unit that packages an application and its dependencies together, allowing it to run consistently across environments.

2fill in blank

medium

Complete the sentence to explain a key security risk in containers.

Cybersecurity

One common security risk in containers is [1], where a container can access resources outside its boundary.

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

Acontainer breakout

Bdata encryption

Cload balancing

Dnetwork throttling

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing with encryption or network issues

Thinking it's a performance problem

Container breakout is when a container escapes its isolation and accesses the host system or other containers, posing a security risk.

3fill in blank

hard

Fix the error in the security best practice statement.

Cybersecurity

To improve container security, always run containers as the [1] user instead of root.

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

Aguest

Bnon-root

Cadministrator

Dsystem

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing root or administrator users

Using guest which may not have enough permissions

Running containers as a non-root user limits permissions and reduces the risk if the container is compromised.

4fill in blank

hard

Fill both blanks to complete the container security scanning process.

Cybersecurity

Security scanning tools analyze [1] to detect vulnerabilities and check [2] for compliance.

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

Acontainer images

Bnetwork traffic

Cconfiguration files

Duser activity logs

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing network traffic or logs with image scanning

Ignoring configuration checks

Security scanning tools analyze container images to find vulnerabilities and check configuration files to ensure compliance with security policies.

5fill in blank

hard

Fill all three blanks to complete the container security best practices.

Cybersecurity

Use [1] to isolate containers, apply [2] updates regularly, and monitor [3] for suspicious activity.

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

Anamespaces

Bsecurity

Clogs

Dfirewalls

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing firewalls with isolation

Ignoring the importance of updates or logs

Namespaces isolate containers, security updates fix vulnerabilities, and monitoring logs helps detect suspicious activity.

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