Rule explorer
Browse every hardening rule in the catalog. Filter by platform, severity, profile level and whether the check can be automated.
119 rules foundof 16,927Page 4 of 5
| ID | Title | Platform | Severity | Level | Check |
|---|---|---|---|---|---|
| TMA-DOCKER-4.1 | Ensure that a user for the container has been createddocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-4.2 | Ensure that containers use only trusted base imagesdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-4.3 | Ensure that unnecessary packages are not installed in the containerdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-4.4 | Ensure images are scanned and rebuilt to include security patchesdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-4.6 | Ensure update instructions are not used alone in Dockerfilesdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-4.7 | Ensure setuid and setgid permissions are removeddocker · Level 2 | docker | Medium | 2 | Manual review |
| TMA-DOCKER-4.8 | Ensure that COPY is used instead of ADD in Dockerfilesdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-4.10 | Ensure only verified packages are installeddocker · Level 2 | docker | Medium | 2 | Manual review |
| TMA-DOCKER-5.1 | Ensure swarm mode is not Enabled, if not neededdocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.2 | Ensure that, if applicable, an AppArmor Profile is enableddocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.3 | Ensure that, if applicable, SELinux security options are setdocker · Level 2 | docker | Medium | 2 | Automated |
| TMA-DOCKER-5.4 | Ensure that Linux kernel capabilities are restricted within containersdocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.7 | Ensure sshd is not run within containersdocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.8 | Ensure privileged ports are not mapped within containersdocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.9 | Ensure that only needed ports are open on the containerdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-5.11 | Ensure that the memory usage for containers is limiteddocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.12 | Ensure that CPU priority is set appropriately on containersdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-5.13 | Ensure that the container's root filesystem is mounted as read onlydocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.14 | Ensure that incoming container traffic is bound to a specific host interfacedocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.18 | Ensure that host devices are not directly exposed to containersdocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.19 | Ensure that the default ulimit is overwritten at runtime if neededdocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-5.20 | Ensure mount propagation mode is not set to shareddocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.21 | Ensure that the host's UTS namespace is not shareddocker · Level 1 | docker | Medium | 1 | Automated |
| TMA-DOCKER-5.28 | Ensure that Docker commands always make use of the latest version of their imagedocker · Level 1 | docker | Medium | 1 | Manual review |
| TMA-DOCKER-5.29 | Ensure that the PIDs cgroup limit is useddocker · Level 1 | docker | Medium | 1 | Automated |