All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Docker 3.19Ensure that the /etc/default/docker file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.2Ensure that docker.service file permissions are appropriately setVotes: 0GitHub stars: 2,182
- Cis Docker 3.20Ensure that the /etc/default/docker file permissions are set to 644 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker 3.21Ensure that the /etc/sysconfig/docker file permissions are set to 644 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker 3.22Ensure that the /etc/sysconfig/docker file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.23Ensure that the Containerd socket file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.24Ensure that the Containerd socket file permissions are set to 660 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker 3.3Ensure that docker.socket file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.4Ensure that docker.socket file permissions are set to 644 or more restrictiveVotes: 0GitHub stars: 2,182
- Cis Docker 3.5Ensure that the /etc/docker directory ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.6Ensure that /etc/docker directory permissions are set to 755 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker 3.7Ensure that registry certificate file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 3.8Ensure that registry certificate file permissions are set to 444 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker 3.9Ensure that TLS CA certificate file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker 4.1Ensure that a user for the container has been createdVotes: 0GitHub stars: 2,182
- Cis Docker 4.10Ensure secrets are not stored in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker 4.11Ensure only verified packages are installedVotes: 0GitHub stars: 2,182
- Cis Docker 4.12Ensure all signed artifacts are validatedVotes: 0GitHub stars: 2,182
- Cis Docker 4.2Ensure that containers use only trusted base imagesVotes: 0GitHub stars: 2,182
- Cis Docker 4.3Ensure that unnecessary packages are not installed in the containerVotes: 0GitHub stars: 2,182
- Cis Docker 4.4Ensure images are scanned and rebuilt to include security patchesVotes: 0GitHub stars: 2,182
- Cis Docker 4.5Ensure Content trust for Docker is EnabledVotes: 0GitHub stars: 2,182
- Cis Docker 4.6Ensure that HEALTHCHECK instructions have been added to container imagesVotes: 0GitHub stars: 2,182
- Cis Docker 4.7Ensure update instructions are not used alone in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker 4.8Ensure setuid and setgid permissions are removedVotes: 0GitHub stars: 2,182
- Cis Docker 4.9Ensure that COPY is used instead of ADD in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker 5.1Ensure swarm mode is not Enabled, if not neededVotes: 0GitHub stars: 2,182
- Cis Docker 5.10Ensure that the host's network namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker 5.11Ensure that the memory usage for containers is limitedVotes: 0GitHub stars: 2,182
- Cis Docker 5.12Ensure that CPU priority is set appropriately on containersVotes: 0GitHub stars: 2,182
- Cis Docker 5.13Ensure that the container's root filesystem is mounted as read onlyVotes: 0GitHub stars: 2,182
- Cis Docker 5.14Ensure that incoming container traffic is bound to a specific host interfaceVotes: 0GitHub stars: 2,182
- Cis Docker 5.15Ensure that the 'on-failure' container restart policy is set to '5'Votes: 0GitHub stars: 2,182
- Cis Docker 5.16Ensure that the host's process namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker 5.17Ensure that the host's IPC namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker 5.18Ensure that host devices are not directly exposed to containersVotes: 0GitHub stars: 2,182
- Cis Docker 5.19Ensure that the default ulimit is overwritten at runtime if neededVotes: 0GitHub stars: 2,182
- Cis Docker 5.2Ensure that, if applicable, an AppArmor Profile is enabledVotes: 0GitHub stars: 2,182
- Cis Docker 5.20Ensure mount propagation mode is not set to sharedVotes: 0GitHub stars: 2,182
- Cis Docker 5.21Ensure that the host's UTS namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker 5.22Ensure the default seccomp profile is not DisabledVotes: 0GitHub stars: 2,182
- Cis Docker 5.23Ensure that docker exec commands are not used with the privileged optionVotes: 0GitHub stars: 2,182
- Cis Docker 5.24Ensure that docker exec commands are not used with the user=root optionVotes: 0GitHub stars: 2,182
- Cis Docker 5.25Ensure that cgroup usage is confirmedVotes: 0GitHub stars: 2,182
- Cis Docker 5.26Ensure that the container is restricted from acquiring additional privilegesVotes: 0GitHub stars: 2,182
- Cis Docker 5.27Ensure that container health is checked at runtimeVotes: 0GitHub stars: 2,182
- Cis Docker 5.28Ensure that Docker commands always make use of the latest version of their imageVotes: 0GitHub stars: 2,182
- Cis Docker 5.29Ensure that the PIDs cgroup limit is usedVotes: 0GitHub stars: 2,182
- Cis Docker 5.3Ensure that, if applicable, SELinux security options are setVotes: 0GitHub stars: 2,182
- Cis Docker 5.30Ensure that Docker's default bridge docker0 is not usedVotes: 0GitHub stars: 2,182