Jun 17, 2024 |
Jun 6, 2024 Functional Update- 1.2.3 Ensure repo_gpgcheck is globally activated
- 4.2.8 Ensure sshd DisableForwarding is enabled
- 4.4.3.1.3 Ensure password failed attempts lockout includes root account
- 5.2.3.19 Ensure kernel module loading unloading and modification is collected
- 5.2.3.2 Ensure actions as another user are always logged
- 5.2.3.4 Ensure events that modify date and time information are collected
- 5.2.3.6 Ensure use of privileged commands are collected
- 5.2.4.1 Ensure the audit log directory is 0750 or more restrictive
Informational Update- 1.1.1.6 Ensure squashfs kernel module is not available
- 1.1.1.7 Ensure udf kernel module is not available
- 1.1.2.3.1 Ensure separate partition exists for /home
- 1.1.2.4.1 Ensure separate partition exists for /var
- 1.1.2.5.1 Ensure separate partition exists for /var/tmp
- 1.1.2.6.1 Ensure separate partition exists for /var/log
- 1.1.2.7.1 Ensure separate partition exists for /var/log/audit
- 1.2.3 Ensure repo_gpgcheck is globally activated
- 1.5.1.5 Ensure the SELinux mode is enforcing
- 1.8.1 Ensure GNOME Display Manager is removed
- 2.2.20 Ensure X window server services are not in use
- 2.3.2 Ensure ldap client is not installed
- 3.2.1 Ensure dccp kernel module is not available
- 3.2.2 Ensure tipc kernel module is not available
- 3.2.3 Ensure rds kernel module is not available
- 3.2.4 Ensure sctp kernel module is not available
- 4.2.8 Ensure sshd DisableForwarding is enabled
- 4.3.4 Ensure users must provide password for escalation
- 4.4.3.1.3 Ensure password failed attempts lockout includes root account
- 4.5.3.1 Ensure nologin is not listed in /etc/shells
- 5.2.1.1 Ensure audit is installed
- 5.2.1.2 Ensure auditing for processes that start prior to auditd is enabled
- 5.2.1.3 Ensure audit_backlog_limit is sufficient
- 5.2.1.4 Ensure auditd service is enabled
- 5.2.2.1 Ensure audit log storage size is configured
- 5.2.2.2 Ensure audit logs are not automatically deleted
- 5.2.2.3 Ensure system is disabled when audit logs are full
- 5.2.2.4 Ensure system warns when audit logs are low on space
- 5.2.3.1 Ensure changes to system administration scope (sudoers) is collected
- 5.2.3.10 Ensure successful file system mounts are collected
- 5.2.3.11 Ensure session initiation information is collected
- 5.2.3.12 Ensure login and logout events are collected
- 5.2.3.13 Ensure file deletion events by users are collected
- 5.2.3.14 Ensure events that modify the system's Mandatory Access Controls are collected
- 5.2.3.15 Ensure successful and unsuccessful attempts to use the chcon command are recorded
- 5.2.3.16 Ensure successful and unsuccessful attempts to use the setfacl command are recorded
- 5.2.3.17 Ensure successful and unsuccessful attempts to use the chacl command are recorded
- 5.2.3.18 Ensure successful and unsuccessful attempts to use the usermod command are recorded
- 5.2.3.19 Ensure kernel module loading unloading and modification is collected
- 5.2.3.2 Ensure actions as another user are always logged
- 5.2.3.20 Ensure the audit configuration is immutable
- 5.2.3.21 Ensure the running and on disk configuration is the same
- 5.2.3.3 Ensure events that modify the sudo log file are collected
- 5.2.3.4 Ensure events that modify date and time information are collected
- 5.2.3.5 Ensure events that modify the system's network environment are collected
- 5.2.3.6 Ensure use of privileged commands are collected
- 5.2.3.7 Ensure unsuccessful file access attempts are collected
- 5.2.3.8 Ensure events that modify user/group information are collected
- 5.2.3.9 Ensure discretionary access control permission modification events are collected
- 5.2.4.1 Ensure the audit log directory is 0750 or more restrictive
- 5.2.4.10 Ensure audit tools belong to group root
- 5.2.4.2 Ensure audit log files are mode 0640 or less permissive
- 5.2.4.3 Ensure only authorized users own audit log files
- 5.2.4.4 Ensure only authorized groups are assigned ownership of audit log files
- 5.2.4.5 Ensure audit configuration files are 640 or more restrictive
- 5.2.4.6 Ensure audit configuration files are owned by root
- 5.2.4.7 Ensure audit configuration files belong to group root
- 5.2.4.8 Ensure audit tools are 755 or more restrictive
- 5.2.4.9 Ensure audit tools are owned by root
- 6.1.14 Audit system file permissions
Miscellaneous- Metadata updated.
- References updated.
- Variables updated.
|
Mar 18, 2024 Functional Update- 5.2.4.2 Ensure audit log files are mode 0640 or less permissive
- 5.2.4.3 Ensure only authorized users own audit log files
|
Mar 15, 2024 Functional Update- 4.4.3.1.3 Ensure password failed attempts lockout includes root account
|
