All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Ubuntu2004 V300 5 3 3 4 1Ensure pam_unix does not include nullokVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 3 3 4 2Ensure pam_unix does not include rememberVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 3 3 4 3Ensure pam_unix includes a strong password hashing algorithmVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 3 3 4 4Ensure pam_unix includes use_authtokVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 1Ensure password expiration is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 2Ensure minimum password days is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 3Ensure password expiration warning days is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 4Ensure strong password hashing algorithm is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 5Ensure inactive password lock is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 1 6Ensure all users last password change date is in the pastVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 1Ensure root is the only UID 0 accountVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 2Ensure root is the only GID 0 accountVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 3Ensure group root is the only GID 0 groupVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 4Ensure root account access is controlledVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 5Ensure root path integrityVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 6Ensure root user umask is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 7Ensure system accounts do not have a valid login shellVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 2 8Ensure accounts without a valid login shell are lockedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 3 1Ensure nologin is not listed in /etc/shellsVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 3 2Ensure default user shell timeout is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 5 4 3 3Ensure default user umask is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 1 1Ensure AIDE is installedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 1 2Ensure filesystem integrity is regularly checkedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 1 3Ensure cryptographic mechanisms are used to protect the integrity of audit toolsVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 1 1Ensure journald service is enabled and activeVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 1 2Ensure journald log file access is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 1 3Ensure journald log file rotation is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 1 1Ensure systemd-journal-remote is installedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 1 2Ensure systemd-journal-upload authentication is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 1 3Ensure systemd-journal-upload is enabled and activeVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 1 4Ensure systemd-journal-remote service is not in useVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 2Ensure journald ForwardToSyslog is disabledVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 3Ensure journald Compress is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 2 4Ensure journald Storage is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 1Ensure rsyslog service is enabled and activeVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 2Ensure rsyslog is installedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 3Ensure journald is configured to send logs to rsyslogVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 4Ensure rsyslog log file creation mode is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 5Ensure rsyslog logging is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 6Ensure rsyslog is configured to send logs to a remote log hostVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 7Ensure rsyslog is not configured to receive logs from a remote clientVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 3 8Ensure logrotate is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 2 4 1Ensure access to all logfiles has been configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 1 1Ensure auditd packages are installedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 1 2Ensure auditd service is enabled and activeVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 1 3Ensure auditing for processes that start prior to auditd is enabledVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 1 4Ensure audit_backlog_limit is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 2 1Ensure audit log storage size is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 2 2Ensure audit logs are not automatically deletedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 2 3Ensure system is disabled when audit logs are fullVotes: 0GitHub stars: 2,182