All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Ubuntu2004 V300 6 3 2 4Ensure system warns when audit logs are low on spaceVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 1Ensure changes to system administration scope (sudoers) is collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 10Ensure successful file system mounts are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 11Ensure session initiation information is collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 12Ensure login and logout events are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 13Ensure file deletion events by users are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 14Ensure events that modify the system's Mandatory Access Controls are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 15Ensure successful and unsuccessful attempts to use the chcon command are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 16Ensure successful and unsuccessful attempts to use the setfacl command are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 17**Control:** Ensure successful and unsuccessful attempts to use the chacl command are collected **Profile Applicability:** Level 2 - Server, Level 2 - Workstation **Description:** The operating system must generate audit records for successful/unsuccessful uses of the chacl command. chacl is an IRIX-compatibility command, and is maintained for those users who are familiar with its use from either XFS or IRIX. **Rationale:** chacl changes the ACL(s) for a file or directory. Without generating ...Votes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 18**Control:** Ensure successful and unsuccessful attempts to use the usermod command are collected **Profile Applicability:** Level 2 - Server, Level 2 - Workstation **Description:** The operating system must generate audit records for successful/unsuccessful uses of the usermod command. **Rationale:** The usermod command modifies the system account files to reflect the changes that are specified on the command line. Without generating audit records that are specific to the security and missio...Votes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 19**Control:** Ensure kernel module loading unloading and modification is collected **Profile Applicability:** Level 2 - Server, Level 2 - Workstation **Description:** Monitor the loading and unloading of kernel modules. All the loading / listing / dependency checking of modules is done by kmod via symbolic links. The following system calls control loading and unloading of modules: - init_module - load a module - finit_module - load a module (used when the overhead of using cryptographically si...Votes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 2Ensure actions as another user are always loggedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 20**Control:** Ensure the audit configuration is immutable **Profile Applicability:** Level 2 - Server, Level 2 - Workstation **Description:** Set system audit so that audit rules cannot be modified with auditctl. Setting the flag "-e 2" forces audit to be put in immutable mode. Audit changes can only be made on system reboot. Note: This setting will require the system to be rebooted to update the active auditd configuration settings. **Rationale:** In immutable mode, unauthorized users cannot ...Votes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 21**Control:** Ensure the running and on disk configuration is the same **Profile Applicability:** Level 2 - Server, Level 2 - Workstation **Description:** Verify that the on disk and running audit configurations are the same to ensure that audit logging is consistent and captures all expected events. **Rationale:** Ensuring the on disk and running configurations match prevents situations where audit rules are configured but not active, potentially missing critical security events. Discrepancie...Votes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 3Ensure events that modify the sudo log file are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 4Ensure events that modify date and time information are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 5Ensure events that modify the system's network environment are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 6Ensure use of privileged commands are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 7Ensure unsuccessful file access attempts are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 8Ensure events that modify user/group information are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 3 9Ensure discretionary access control permission modification events are collectedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 1- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 10- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 2- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 3- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 4- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 5- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 6- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 7- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 8- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 6 3 4 9- Level 2 - Server - Level 2 - WorkstationVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 1Ensure access to /etc/passwd is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 10Ensure access to /etc/security/opasswd is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 11Ensure world writable files and directories are securedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 12Ensure no files or directories without an owner and a group existVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 13Ensure SUID and SGID files are reviewedVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 2Ensure access to /etc/passwd- is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 3Ensure access to /etc/group is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 4Ensure access to /etc/group- is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 5Ensure access to /etc/shadow is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 6Ensure access to /etc/shadow- is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 7Ensure access to /etc/gshadow is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 8Ensure access to /etc/gshadow- is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 1 9Ensure access to /etc/shells is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 2 1Ensure accounts in /etc/passwd use shadowed passwordsVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 2 10Ensure local interactive user dot files access is configuredVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 2 2Ensure /etc/shadow password fields are not emptyVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 2 3Ensure all groups in /etc/passwd exist in /etc/groupVotes: 0GitHub stars: 2,182
- Cis Ubuntu2004 V300 7 2 4Ensure shadow group is emptyVotes: 0GitHub stars: 2,182