All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Docker V170 1.1.8Ensure auditing is configured for Docker files and directories - containerd.sockVotes: 0GitHub stars: 2,182
- Cis Docker V170 1.1.9Ensure auditing is configured for Docker files and directories - docker.sockVotes: 0GitHub stars: 2,182
- Cis Docker V170 1.2.1Ensure the container host has been HardenedVotes: 0GitHub stars: 2,182
- Cis Docker V170 1.2.2Ensure that the version of Docker is up to dateVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.1Run the Docker daemon as a non-root user, if possibleVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.10Ensure the default cgroup usage has been confirmedVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.11Ensure base device size is not changed until neededVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.12Ensure that authorization for Docker client commands is enabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.13Ensure centralized and remote logging is configuredVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.14Ensure containers are restricted from acquiring new privilegesVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.15Ensure live restore is enabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.16Ensure Userland Proxy is DisabledVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.17Ensure that a daemon-wide custom seccomp profile is applied if appropriateVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.18Ensure that experimental features are not implemented in productionVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.2Ensure network traffic is restricted between containers on the default bridgeVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.3Ensure the logging level is set to 'info'Votes: 0GitHub stars: 2,182
- Cis Docker V170 2.4Ensure Docker is allowed to make changes to iptablesVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.5Ensure insecure registries are not usedVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.6Ensure aufs storage driver is not usedVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.7Ensure TLS authentication for Docker daemon is configuredVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.8Ensure the default ulimit is configured appropriatelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 2.9Enable user namespace supportVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.1Ensure that the docker.service file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.10Ensure that TLS CA certificate file permissions are set to 444 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.11Ensure that Docker server certificate file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.12Ensure that the Docker server certificate file permissions are set to 444 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.13Ensure that the Docker server certificate key file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.14Ensure that the Docker server certificate key file permissions are set to 400Votes: 0GitHub stars: 2,182
- Cis Docker V170 3.15Ensure that the Docker socket file ownership is set to root:dockerVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.16Ensure that the Docker socket file permissions are set to 660 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.17Ensure that the daemon.json file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.18Ensure that daemon.json file permissions are set to 644 or more restrictiveVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.19Ensure that the /etc/default/docker file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.2Ensure that docker.service file permissions are appropriately setVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.20Ensure that the /etc/default/docker file permissions are set to 644 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.21Ensure that the /etc/sysconfig/docker file permissions are set to 644 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.22Ensure that the /etc/sysconfig/docker file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.23Ensure that the Containerd socket file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.24Ensure that the Containerd socket file permissions are set to 660 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.3Ensure that docker.socket file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.4Ensure that docker.socket file permissions are set to 644 or more restrictiveVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.5Ensure that the /etc/docker directory ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.6Ensure that /etc/docker directory permissions are set to 755 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.7Ensure that registry certificate file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.8Ensure that registry certificate file permissions are set to 444 or more restrictivelyVotes: 0GitHub stars: 2,182
- Cis Docker V170 3.9Ensure that TLS CA certificate file ownership is set to root:rootVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.1Ensure that a user for the container has been createdVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.10Ensure secrets are not stored in DockerfilesVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.11Ensure only verified packages are installedVotes: 0GitHub stars: 2,182
- Cis Docker V170 4.12Ensure all signed artifacts are validatedVotes: 0GitHub stars: 2,182