All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Docker V170 4.2Ensure that containers use only trusted base imagesVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.3Ensure that unnecessary packages are not installed in the containerVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.4Ensure images are scanned and rebuilt to include security patchesVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.5Ensure Content trust for Docker is EnabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.6Ensure that HEALTHCHECK instructions have been added to container imagesVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.7Ensure update instructions are not used alone in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.8Ensure setuid and setgid permissions are removedVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.9Ensure that COPY is used instead of ADD in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.1Ensure swarm mode is not Enabled, if not neededVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.10Ensure that the host's network namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.11Ensure that the memory usage for containers is limitedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.12Ensure that CPU priority is set appropriately on containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.13Ensure that the container's root filesystem is mounted as read onlyVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.14Ensure that incoming container traffic is bound to a specific host interfaceVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.15Ensure that the 'on-failure' container restart policy is set to '5'Votes: 0GitHub stars: 2,182
- Cis Docker V170 5.16Ensure that the host's process namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.17Ensure that the host's IPC namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.18Ensure that host devices are not directly exposed to containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.19Ensure that the default ulimit is overwritten at runtime if neededVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.2Ensure that, if applicable, an AppArmor Profile is enabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.20Ensure mount propagation mode is not set to sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.21Ensure that the host's UTS namespace is not sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.22Ensure the default seccomp profile is not DisabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.23Ensure that docker exec commands are not used with the privileged optionVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.24Ensure that docker exec commands are not used with the user=root optionVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.25Ensure that cgroup usage is confirmedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.26Ensure that the container is restricted from acquiring additional privilegesVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.27Ensure that container health is checked at runtimeVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.28Ensure that Docker commands always make use of the latest version of their imageVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.29Ensure that the PIDs cgroup limit is usedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.3Ensure that, if applicable, SELinux security options are setVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.30Ensure that Docker's default bridge docker0 is not usedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.31Ensure that the host's user namespaces are not sharedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.32Ensure that the Docker socket is not mounted inside any containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.4Ensure that Linux kernel capabilities are restricted within containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.5Ensure that privileged containers are not usedVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.6Ensure sensitive host system directories are not mounted on containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.7Ensure sshd is not run within containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.8Ensure privileged ports are not mapped within containersVotes: 0GitHub stars: 2,182
- Cis Docker V170 5.9Ensure that only needed ports are open on the containerVotes: 0GitHub stars: 2,182
- Cis Docker V170 6.1Ensure that image sprawl is avoidedVotes: 0GitHub stars: 2,182
- Cis Docker V170 6.2Ensure that container sprawl is avoidedVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.1Ensure that the minimum number of manager nodes have been created in a swarmVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.2Ensure that swarm services are bound to a specific host interfaceVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.3Ensure that all Docker swarm overlay networks are encryptedVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.4Ensure that Docker's secret management commands are used for managing secrets in a swarm clusterVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.5Ensure that swarm manager is run in auto-lock modeVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.6Ensure that the swarm manager auto-lock key is rotated periodicallyVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.7Ensure that node certificates are rotated as appropriateVotes: 0GitHub stars: 2,182
- Cis Docker V170 7.8Ensure that CA certificates are rotated as appropriateVotes: 0GitHub stars: 2,182