Rule explorer
Browse every hardening rule in the catalogue. Filter by platform, severity, profile level and whether the check can be automated.
119 rules foundof 16,927Page 1 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-DOCKER-2.8 | Ensure TLS authentication for Docker daemon is configureddocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-3.15 | Ensure that the Docker socket file ownership is set to root:dockerdocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-3.16 | Ensure that the Docker socket file permissions are set to 660 or more restrictivelydocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-5.5 | Ensure that privileged containers are not useddocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-5.32 | Ensure that the Docker socket is not mounted inside any containersdocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-NO-PRIVILEGED | Ensure no running container is privilegeddocker · Level 1 | docker | Critical | 1 | Automated |
| TMA-DOCKER-2.1 | Run the Docker daemon as a non-root user, if possibledocker · Level 1 | docker | High | 1 | Manual review |
| TMA-DOCKER-2.5 | Ensure insecure registries are not useddocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-2.15 | Ensure containers are restricted from acquiring new privilegesdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.1 | Ensure that the docker.service file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.2 | Ensure that docker.service file permissions are appropriately setdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.3 | Ensure that docker.socket file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.4 | Ensure that docker.socket file permissions are set to 644 or more restrictivedocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.5 | Ensure that the /etc/docker directory ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.6 | Ensure that /etc/docker directory permissions are set to 755 or more restrictivelydocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.7 | Ensure that registry certificate file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.8 | Ensure that registry certificate file permissions are set to 444 or more restrictivelydocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.9 | Ensure that TLS CA certificate file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.10 | Ensure that TLS CA certificate file permissions are set to 444 or more restrictivelydocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.11 | Ensure that Docker server certificate file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.12 | Ensure that the Docker server certificate file permissions are set to 444 or more restrictivelydocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.13 | Ensure that the Docker server certificate key file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.14 | Ensure that the Docker server certificate key file permissions are set to 400docker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.23 | Ensure that the Containerd socket file ownership is set to root:rootdocker · Level 1 | docker | High | 1 | Automated |
| TMA-DOCKER-3.24 | Ensure that the Containerd socket file permissions are set to 660 or more restrictivelydocker · Level 1 | docker | High | 1 | Automated |