Nov 3, 2025 Functional Update- 2.1.1 Ensure autofs services are not in use
- 2.1.11 Ensure print server services are not in use
- 3.1.3 Ensure bluetooth services are not in use
- 6.2.1.3 Ensure auditing for processes that start prior to auditd is enabled
- 6.2.4.5 Ensure audit configuration files mode is configured
- 6.2.4.6 Ensure audit configuration files owner is configured
- 6.2.4.7 Ensure audit configuration files group owner is configured
- 6.3.3 Ensure cryptographic mechanisms are used to protect the integrity of audit tools
Informational Update- 1.1.1.10 Ensure unused filesystems kernel modules are not available
- 1.1.1.6 Ensure overlayfs kernel module is not available
- 1.1.1.7 Ensure squashfs kernel module is not available
- 1.1.1.8 Ensure udf kernel module is not available
- 1.1.1.9 Ensure usb-storage 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.7.6 Ensure GDM automatic mounting of removable media is disabled
- 1.7.7 Ensure GDM disabling automatic mounting of removable media is not overridden
- 2.1.11 Ensure print server services are not in use
- 2.1.2 Ensure avahi daemon services are not in use
- 3.1.3 Ensure bluetooth services are not in use
- 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
- 5.3.3.1.3 Ensure password failed attempts lockout includes root account
- 5.4.1.2 Ensure minimum password days is configured
- 5.4.3.1 Ensure nologin is not listed in /etc/shells
- 6.2.1.3 Ensure auditing for processes that start prior to auditd is enabled
- 6.2.1.4 Ensure audit_backlog_limit is sufficient
- 6.2.2.3 Ensure system is disabled when audit logs are full
- 6.2.2.4 Ensure system warns when audit logs are low on space
- 6.2.3.1 Ensure changes to system administration scope (sudoers) is collected
- 6.2.3.10 Ensure successful file system mounts are collected
- 6.2.3.11 Ensure session initiation information is collected
- 6.2.3.12 Ensure login and logout events are collected
- 6.2.3.13 Ensure file deletion events by users are collected
- 6.2.3.14 Ensure events that modify the system's Mandatory Access Controls are collected
- 6.2.3.15 Ensure successful and unsuccessful attempts to use the chcon command are collected
- 6.2.3.16 Ensure successful and unsuccessful attempts to use the setfacl command are collected
- 6.2.3.17 Ensure successful and unsuccessful attempts to use the chacl command are collected
- 6.2.3.18 Ensure successful and unsuccessful attempts to use the usermod command are collected
- 6.2.3.19 Ensure kernel module loading unloading and modification is collected
- 6.2.3.2 Ensure actions as another user are always logged
- 6.2.3.20 Ensure the audit configuration is immutable
- 6.2.3.21 Ensure the running and on disk configuration is the same
- 6.2.3.3 Ensure events that modify the sudo log file are collected
- 6.2.3.4 Ensure events that modify date and time information are collected
- 6.2.3.5 Ensure events that modify the system's network environment are collected
- 6.2.3.6 Ensure use of privileged commands are collected
- 6.2.3.7 Ensure unsuccessful file access attempts are collected
- 6.2.3.8 Ensure events that modify user/group information are collected
- 6.2.3.9 Ensure discretionary access control permission modification events are collected
- 6.2.4.1 Ensure audit log files mode is configured
- 6.2.4.2 Ensure audit log files owner is configured
- 6.2.4.3 Ensure audit log files group owner is configured
- 6.2.4.4 Ensure the audit log file directory mode is configured
- 6.2.4.5 Ensure audit configuration files mode is configured
- 6.2.4.6 Ensure audit configuration files owner is configured
- 6.2.4.7 Ensure audit configuration files group owner is configured
- 6.3.3 Ensure cryptographic mechanisms are used to protect the integrity of audit tools
Miscellaneous- Metadata updated.
- References updated.
- Variables updated.
|
Jan 6, 2025 Informational Update- 1.1.1.10 Ensure unused filesystems kernel modules are not available
- 1.1.1.6 Ensure overlayfs kernel module is not available
- 1.1.1.7 Ensure squashfs kernel module is not available
- 1.1.1.8 Ensure udf kernel module is not available
- 1.1.1.9 Ensure usb-storage kernel module is not available
- 1.7.6 Ensure GDM automatic mounting of removable media is disabled
- 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
- 6.2.3.10 Ensure successful file system mounts are collected
- 6.2.3.13 Ensure file deletion events by users are collected
- 6.2.3.15 Ensure successful and unsuccessful attempts to use the chcon command are collected
- 6.2.3.16 Ensure successful and unsuccessful attempts to use the setfacl command are collected
- 6.2.3.17 Ensure successful and unsuccessful attempts to use the chacl command are collected
- 6.2.3.18 Ensure successful and unsuccessful attempts to use the usermod command are collected
- 6.2.3.19 Ensure kernel module loading unloading and modification is collected
- 6.2.3.3 Ensure events that modify the sudo log file are collected
- 6.2.3.6 Ensure use of privileged commands are collected
- 6.2.3.7 Ensure unsuccessful file access attempts are collected
- 6.2.3.9 Ensure discretionary access control permission modification events are collected
- 6.2.4.1 Ensure audit log files mode is configured
- 6.2.4.2 Ensure audit log files owner is configured
|
