Back to articles
Security & Anti-DDoS

Detailed Guide to Docker Hardening According to CIS Benchmark for Enhanced Container Security

A detailed guide on hardening Docker using the CIS Benchmark to strengthen container system security, including safe configuration, access control, and advanced security measures.

DPTCloud Engineering4 min read
Detailed Guide to Docker Hardening According to CIS Benchmark for Enhanced Container Security

Introduction to Docker Hardening with CIS Benchmark

Hardening Docker involves optimizing and enhancing the security of container environments by applying strict security standards such as the CIS Docker Benchmark. This detailed guide helps you implement security measures according to the CIS standard to reduce risks from security vulnerabilities, network attacks, and unauthorized access to container systems.

1. Install and Configure Docker Securely

To begin, ensure Docker is installed in the latest version and configured following secure guidelines.

1.1. Install Docker

Run the following commands on Linux (Ubuntu/Debian):

sudo apt update
sudo apt install -y docker.io
sudo systemctl enable docker
sudo systemctl start docker

1.2. Configure Docker with Rootless Mode

Rootless mode reduces the risk of system compromise if a container is attacked.

# Configure rootless mode
sudo usermod -aG docker $USER
dockerd-rootless-setuptool.sh install

2. Apply CIS Docker Benchmark

The CIS Docker Benchmark provides a detailed list of security checks. Below are key steps for Docker hardening.

2.1. Container Access Control

Only allow containers to run with minimal privileges.

# Run container with restricted privileges
docker run --rm --security-opt=no-new-privileges --cap-drop=ALL -it ubuntu

2.2. Configure Docker Daemon

Modify the Docker daemon configuration file to enhance security.


{
  "security": {
    "seccomp": "default",
    "apparmor": "default"
  },
  "userns-remap": "default",
  "default-ulimits": {
    "nofile": {
      "Name": "nofile",
      "Soft": 1024,
      "Hard": 4096
    }
  }
}

Save the file to /etc/docker/daemon.json and restart Docker:

sudo systemctl restart docker

3. Security Verification and Testing

After configuration, verify the security settings.

3.1. Use CIS Docker Benchmark Tool

Use the docker-bench-security tool to perform checks:

docker run --rm -i --net host --pid host --privileged --cap-add=SYS_ADMIN \
    --name docker-bench-security docker/docker-bench-security

3.2. Verify Configuration

Run the following command to check security settings:

docker info | grep -i security

4. Additional Security Measures

Beyond CIS Benchmark, apply advanced security practices.

4.1. Use Kata Containers

Kata Containers provide a MicroVM sandbox environment, ideal for untrusted applications.

Refer to the article: Container Security with Kata Containers.

4.2. Configure Container Networking

Allow connections to containers only through permitted ports.

docker run -p 80:80 --network host --name webapp nginx

5. Troubleshooting and Maintenance

Keep the system updated and monitor security patches.

5.1. Update Docker and System

sudo apt update && sudo apt upgrade -y

5.2. Check Docker Logs

sudo journalctl -u docker.service --no-pager | tail -20

References

Related infrastructure & engineering guides: Cloud VPS with L3/L4/L7 Anycast Anti-DDoS

DPTCloud Tier III Infrastructure

Recommended NVMe Cloud VPS Plans to Deploy This Setup

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02

VPS-2E

94.600 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 2 GB
  • SSD: 30 GB NVMe
ECO · vn-02Recommended

VPS-3E

170.500 ₫ / mo

10% VAT included

  • CPU: 2 vCPU
  • RAM: 4 GB
  • SSD: 50 GB NVMe
BASIC · vn-01Recommended

VPS-05

457.600 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478