Capacity
CCI-000130
Ensure that audit records containing information that establishes what type of event occurred.
1
Rule
Severity: High
Enable audit Service
29
Rule
Severity: Medium
Ensure the audit Subsystem is Installed
30
Rule
Severity: Medium
Enable auditd Service
29
Rule
Severity: Medium
Ensure auditd Collects Information on Exporting to Media (successful)
29
Rule
Severity: Medium
Ensure auditd Collects System Administrator Actions
29
Rule
Severity: Medium
Record Events that Modify User/Group Information
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - chmod
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - chown
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fchmod
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fchmodat
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fchown
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fchownat
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fremovexattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - fsetxattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - lchown
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - lremovexattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - lsetxattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - removexattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - setxattr
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - umount
29
Rule
Severity: Medium
Record Events that Modify the System's Discretionary Access Controls - umount2
29
Rule
Severity: Medium
Ensure auditd Collects File Deletion Events by User - rename
29
Rule
Severity: Medium
Ensure auditd Collects File Deletion Events by User - renameat
29
Rule
Severity: Medium
Ensure auditd Collects File Deletion Events by User - rmdir
29
Rule
Severity: Medium
Ensure auditd Collects File Deletion Events by User - unlink
29
Rule
Severity: Medium
Ensure auditd Collects File Deletion Events by User - unlinkat
23
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - creat
23
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - ftruncate
23
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - open
24
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - open_by_handle_at
23
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - openat
23
Rule
Severity: Medium
Record Unsuccessful Access Attempts to Files - truncate
22
Rule
Severity: Medium
Ensure auditd Collects Information on Kernel Module Unloading - delete_module
23
Rule
Severity: Medium
Ensure auditd Collects Information on Kernel Module Loading and Unloading - finit_module
22
Rule
Severity: Medium
Ensure auditd Collects Information on Kernel Module Loading - init_module
3
Rule
Severity: Medium
Ensure the audit-libs package as a part of audit Subsystem is Installed
19
Rule
Severity: Low
Enable Auditing for Processes Which Start Prior to the Audit Daemon
17
Rule
Severity: Low
Extend Audit Backlog Limit for the Audit Daemon
20
Rule
Severity: Medium
Record Events that Modify User/Group Information - /etc/group
20
Rule
Severity: Medium
Record Events that Modify User/Group Information - /etc/gshadow
20
Rule
Severity: Medium
Record Events that Modify User/Group Information - /etc/security/opasswd
20
Rule
Severity: Medium
Record Events that Modify User/Group Information - /etc/passwd
20
Rule
Severity: Medium
Record Events that Modify User/Group Information - /etc/shadow
17
Rule
Severity: Medium
Record Any Attempts to Run chcon
14
Rule
Severity: Medium
Record Any Attempts to Run setsebool
23
Rule
Severity: Medium
Record Attempts to Alter Logon and Logout Events - lastlog
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - chage
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - chsh
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - crontab
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - gpasswd
9
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - insmod
14
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - kmod
9
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - modprobe
16
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - mount
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - newgrp
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - pam_timestamp_check
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - passwd
16
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - postdrop
16
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - postqueue
9
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - rmmod
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - ssh-keysign
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - su
18
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - sudo
16
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - sudoedit
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - umount
17
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - unix_chkpwd
8
Rule
Severity: Medium
Ensure auditd Collects System Administrator Actions - /etc/sudoers
7
Rule
Severity: Medium
Ensure auditd Collects System Administrator Actions - /etc/sudoers.d/
14
Rule
Severity: Medium
Record Any Attempts to Run chacl
11
Rule
Severity: Medium
Record Any Attempts to Run setfacl
11
Rule
Severity: Medium
Record Any Attempts to Run ssh-agent
8
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - unix_update
14
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - usermod
1
Rule
Severity: Medium
Enable Auditing for Processes Which Start Prior to the Audit Daemon
2
Rule
Severity: Medium
Ensure the libaudit1 package as a part of audit Subsystem is Installed
2
Rule
Severity: Medium
Record Any Attempts to Run chmod
2
Rule
Severity: Medium
Record Any Attempts to Run rm
4
Rule
Severity: Medium
Record Attempts to Alter Logon and Logout Events - faillog
4
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - chfn
2
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - passmass
1
Rule
Severity: Medium
Ensure auditd Collects Information on the Use of Privileged Commands - unix2_chkpwd
2
Rule
Severity: Medium
AAA Services configuration audit records must identify what type of events occurred.
6
Rule
Severity: Medium
The Apache web server must produce log records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
The ALG must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Low
The Arista Multilayer Switch must produce audit log records containing sufficient information to establish what type of event occurred.
2
Rule
Severity: Medium
The application server must produce log records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
The Arista network device must be configured to capture all DOD auditable events.
2
Rule
Severity: Medium
The application must log application shutdown events.
2
Rule
Severity: Medium
The application must log destination IP addresses.
2
Rule
Severity: Medium
The application must log user actions involving access to data.
2
Rule
Severity: Medium
The application must log user actions involving changes to data.
2
Rule
Severity: Low
The print-severity variable for the configuration of BIND 9.x server logs must be configured to produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Low
The Central Log Server must produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Low
The System Administrator (SA) and Information System Security Manager (ISSM) must configure the retention of the log records based on criticality level, event type, and/or retention period, at a minimum.
1
Rule
Severity: Low
The DBN-6300 must produce audit log records containing sufficient information to establish what type of event occurred.
1
Rule
Severity: Medium
The audit log configuration level must be set to request in the Universal Control Plane (UCP) component of Docker Enterprise.
1
Rule
Severity: Medium
The host operating systems auditing policies for the Docker Engine - Enterprise component of Docker Enterprise must be set.
2
Rule
Severity: Medium
The DNS server implementation must produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
The firewall must generate traffic log entries containing information to establish what type of events occurred.
1
Rule
Severity: Medium
The FortiGate firewall must generate traffic log entries containing information to establish what type of events occurred.
1
Rule
Severity: Low
The HP FlexFabric Switch must produce audit log records containing sufficient information to establish what type of event occurred.
1
Rule
Severity: Medium
The HYCU server must initiate session auditing upon startup and produce audit log records containing sufficient information to establish what type of event occurred.
1
Rule
Severity: Medium
The MQ Appliance messaging server must produce log records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
The WebSphere Liberty Server must log remote session and security activity.
1
Rule
Severity: Medium
The MQ Appliance network device must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation.
1
Rule
Severity: Medium
The WebSphere Application Server audit event type filters must be configured.
1
Rule
Severity: Medium
CA VM:Secure product must be installed and operating.
2
Rule
Severity: Medium
The IDPS must produce audit records containing sufficient information to establish what type of event occurred, including, at a minimum, event descriptions, policy filter, rule or signature invoked, port, protocol, and criticality level/alert code or description.
2
Rule
Severity: Medium
JBoss must be configured to log the IP address of the remote system connecting to the JBoss system/cluster.
2
Rule
Severity: Medium
JBoss must be configured to produce log records containing information to establish what type of events occurred.
2
Rule
Severity: Low
The Sentry must produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
The Mainframe Product must produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
The network device must produce audit log records containing sufficient information to establish what type of event occurred.
1
Rule
Severity: Medium
Nutanix AOS must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
OHS must have a log level severity defined to produce sufficient log records to establish what type of events occurred.
1
Rule
Severity: Medium
OHS must have a log format defined for log records generated to capture sufficient information to establish what type of events occurred.
1
Rule
Severity: Medium
OHS must have a SSL log format defined for log records generated to capture sufficient information to establish what type of events occurred.
1
Rule
Severity: Medium
OHS must have a log file defined for each site/virtual host to capture sufficient information to establish what type of events occurred.
1
Rule
Severity: Low
Oracle WebLogic must produce process events and severity levels to establish what type of HTTPD-related events and severity levels occurred.
1
Rule
Severity: Low
Oracle WebLogic must produce audit records containing sufficient information to establish what type of JVM-related events and severity levels occurred.
1
Rule
Severity: Low
Oracle WebLogic must produce process events and security levels to establish what type of Oracle WebLogic process events and severity levels occurred.
2
Rule
Severity: High
The Riverbed NetProfiler must be configured to automatically generate DOD-required audit records with sufficient information to support incident reporting to a central log server.
2
Rule
Severity: Medium
Rancher MCM must generate audit records for all DoD-defined auditable events within all components in the platform.
2
Rule
Severity: Medium
The SDN controller must be configured to produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
Innoslate must generate comprehensive audit records.
1
Rule
Severity: Medium
Symantec ProxySG must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
The SMS must produce audit records containing sufficient information to establish what type of event occurred, including, at a minimum, event descriptions, policy filter, rule or signature invoked, port, protocol, and criticality level/alert code or description by sending all audit and system logs to a centralized syslog server.
2
Rule
Severity: Medium
The UEM server must be configured to produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: High
The TippingPoint SMS must automatically generate audit records for account changes and actions with containing information needed for analysis of the event that occurred on the SMS and TPS.
2
Rule
Severity: Low
The VPN Gateway must generate log records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
Audit records content must contain valid information to allow for proper incident reporting.
2
Rule
Severity: Medium
The Apache web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events.
2
Rule
Severity: Medium
AccessLogValve must be configured for each application context.
2
Rule
Severity: Medium
AccessLogValve must be configured per each virtual host.
1
Rule
Severity: Medium
The macOS system must initiate session audits at system startup, using internal clocks with time stamps for audit records that meet a minimum granularity of one second and can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT), in order to generate audit records containing information to establish what type of events occurred, the identity of any individual or process associated with the event, including individual identities of group account users, establish where the events occurred, source of the event, and outcome of the events including all account enabling actions, full-text recording of privileged commands, and information about the use of encryption for access wireless access to and from the system.
3
Rule
Severity: Medium
The macOS system must produce audit records containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions.
3
Rule
Severity: Medium
The macOS system must enable security auditing.
2
Rule
Severity: Medium
The Ubuntu operating system must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DoD-defined auditable events and actions in near real time.
2
Rule
Severity: Medium
The Cisco ASA must be configured to generate traffic log entries containing information to establish what type of events occurred.
4
Rule
Severity: Medium
PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
The Cisco ASA must be configured to produce audit log records containing sufficient information to establish what type of event occurred.
5
Rule
Severity: Medium
The DBMS must produce audit records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
All audit records must identify what type of event has occurred within the container platform.
2
Rule
Severity: Medium
The EDB Postgres Advanced Server must produce audit records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
The operating system must produce audit records containing information to establish what type of events occurred.
2
Rule
Severity: Medium
SSMC web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events.
2
Rule
Severity: Medium
AIX must produce audit records containing information to establish what the date, time, and type of events that occurred.
4
Rule
Severity: Medium
IBM z/OS required SMF data record types must be collected.
2
Rule
Severity: Low
The ICS must be configured to generate log records containing sufficient information about where, when, identity, source, or outcome of the events.
2
Rule
Severity: Medium
The Juniper device must be configured to produce audit log records containing sufficient information to establish what type of event occurred.
2
Rule
Severity: Medium
The ICS must be configured to audit the execution of privileged functions such as accounts additions and changes.
2
Rule
Severity: Medium
Kubernetes API Server must generate audit records that identify what type of event has occurred, identify the source of the event, contain the event results, identify any users, and identify any containers associated with the event.
2
Rule
Severity: Medium
MariaDB must produce audit records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
MongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.
2
Rule
Severity: Medium
Event tracing for Windows (ETW) for Common Language Runtime events must be enabled.
2
Rule
Severity: Medium
Windows 10 must be configured to audit Other Policy Change Events Failures.
2
Rule
Severity: Medium
Windows 10 must be configured to audit other Logon/Logoff Events Successes.
2
Rule
Severity: Medium
Windows 10 must be configured to audit other Logon/Logoff Events Failures.
2
Rule
Severity: Medium
Windows 10 must be configured to audit Detailed File Share Failures.
2
Rule
Severity: Medium
Windows 10 must be configured to audit MPSSVC Rule-Level Policy Change Successes.
2
Rule
Severity: Medium
Windows 10 must be configured to audit MPSSVC Rule-Level Policy Change Failures.
2
Rule
Severity: Medium
Windows 11 must be configured to audit Other Policy Change Events Successes.
2
Rule
Severity: Medium
Windows 11 must be configured to audit Other Policy Change Events Failures.
2
Rule
Severity: Medium
Windows 11 must be configured to audit other Logon/Logoff Events Successes.
2
Rule
Severity: Medium
Windows 11 must be configured to audit other Logon/Logoff Events Failures.
2
Rule
Severity: Medium
Windows 11 must be configured to audit Detailed File Share Failures.
2
Rule
Severity: Medium
Windows 11 must be configured to audit MPSSVC Rule-Level Policy Change Successes.
2
Rule
Severity: Medium
Windows 11 must be configured to audit MPSSVC Rule-Level Policy Change Failures.
2
Rule
Severity: Medium
OL 8 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.
2
Rule
Severity: Medium
The Oracle Linux operating system must audit all uses of the su command.
2
Rule
Severity: Medium
The Oracle Linux operating system must audit all uses of the sudo command.
2
Rule
Severity: Medium
The Oracle Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory.
2
Rule
Severity: Medium
The Oracle Linux operating system must audit all uses of the newgrp command.
2
Rule
Severity: Medium
The Oracle Linux operating system must audit all uses of the chsh command.
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creation events that affect "/etc/shadow".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creation events that affect "/etc/security/opasswd".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creation events that affect "/etc/passwd".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creation events that affect "/etc/gshadow".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creation events that affect "/etc/group".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers".
2
Rule
Severity: Medium
OL 8 must generate audit records for all account creations, modifications, disabling, and termination events that affect "/etc/sudoers.d/".
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "su" command.
2
Rule
Severity: Medium
The OL 8 audit system must be configured to audit any use of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "chage" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any uses of the "chcon" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "ssh-agent" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "passwd" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "mount" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "umount" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "mount" syscall.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "unix_update" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "postdrop" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "postqueue" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "setsebool" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "unix_chkpwd" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "ssh-keysign" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "setfacl" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "pam_timestamp_check" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "newgrp" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "init_module" and "finit_module" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "rename", "unlink", "rmdir", "renameat", and "unlinkat" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "gpasswd" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the delete_module syscall.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "crontab" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "chsh" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "truncate", "ftruncate", "creat", "open", "openat", and "open_by_handle_at" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "chown", "fchown", "fchownat", and "lchown" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "chmod", "fchmod", and "fchmodat" system calls.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "sudo" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "usermod" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "chacl" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any use of the "kmod" command.
2
Rule
Severity: Medium
OL 8 must generate audit records for any attempted modifications to the "faillock" log file.
2
Rule
Severity: Medium
OL 8 must generate audit records for any attempted modifications to the "lastlog" file.
2
Rule
Severity: Medium
OL 8 must enable auditing of processes that start prior to the audit daemon.
2
Rule
Severity: Low
OL 8 must allocate an "audit_backlog_limit" of sufficient size to capture processes that start prior to the audit daemon.
2
Rule
Severity: Medium
MySQL Database Server 8.0 must produce audit records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
The Automation Controller must generate the appropriate log records.
2
Rule
Severity: Medium
Rancher RKE2 components must be configured in accordance with the security configuration settings based on DOD security configuration or implementation guidance, including SRGs, STIGs, NSA configuration guides, CTOs, and DTMs.
2
Rule
Severity: Medium
All audit records must identify what type of event has occurred within OpenShift.
1
Rule
Severity: Medium
The Red Hat Enterprise Linux operating system must audit all uses of the su command.
1
Rule
Severity: Medium
The Red Hat Enterprise Linux operating system must audit all uses of the sudo command.
1
Rule
Severity: Medium
The Red Hat Enterprise Linux operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory.
1
Rule
Severity: Medium
The Red Hat Enterprise Linux operating system must audit all uses of the newgrp command.
1
Rule
Severity: Medium
The Red Hat Enterprise Linux operating system must audit all uses of the chsh command.
2
Rule
Severity: Low
RHEL 9 must enable auditing of processes that start prior to the audit daemon.
4
Rule
Severity: Medium
SUSE operating system audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the su command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the sudo command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the chfn command.
2
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the mount command.
2
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the umount command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the ssh-agent command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the ssh-keysign command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the kmod command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr syscalls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chown, fchown, fchownat, and lchown syscalls.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chmod, fchmod, and fchmodat system calls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate syscalls.
2
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the passwd command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the gpasswd command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the newgrp command.
4
Rule
Severity: Low
The SUSE operating system must generate audit records for a uses of the chsh command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chmod command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the setfacl command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chacl command.
2
Rule
Severity: Medium
Successful/unsuccessful attempts to modify categories of information (e.g., classification levels) must generate audit records.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the rm command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all modifications to the tallylog file must generate an audit record.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all modifications to the lastlog file.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the passmass command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the unix_chkpwd command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chage command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the usermod command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the crontab command.
4
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the pam_timestamp_check command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the delete_module command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the init_module and finit_module syscalls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all modifications to the faillog file.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the unlink, unlinkat, rename, renameat and rmdir syscalls.
2
Rule
Severity: Medium
RHEL 9 audit package must be installed.
2
Rule
Severity: Medium
RHEL 9 audit service must be enabled.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chmod, fchmod, and fchmodat system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chown, fchown, fchownat, and lchown system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of umount system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chacl command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the setfacl command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chcon command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the semanage command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the setfiles command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the setsebool command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the rename, unlink, rmdir, renameat, and unlinkat system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the truncate, ftruncate, creat, open, openat, and open_by_handle_at system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the delete_module system call.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the init_module and finit_module system calls.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chage command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the chsh command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the crontab command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the gpasswd command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the kmod command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the newgrp command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the pam_timestamp_check command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the passwd command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the postdrop command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the postqueue command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the ssh-agent command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the ssh-keysign command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the su command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the sudo command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the sudoedit command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the unix_chkpwd command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the unix_update command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the userhelper command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the usermod command.
2
Rule
Severity: Medium
RHEL 9 must audit all uses of the mount command.
2
Rule
Severity: Medium
Successful/unsuccessful uses of the umount system call in RHEL 9 must generate an audit record.
2
Rule
Severity: Medium
Successful/unsuccessful uses of the umount2 system call in RHEL 9 must generate an audit record.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/sudoers.d/ directory.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/group.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/gshadow.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/opasswd.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/passwd.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /etc/shadow.
2
Rule
Severity: Medium
RHEL 9 must generate audit records for all account creations, modifications, disabling, and termination events that affect /var/log/lastlog.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the passwd command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the unix_chkpwd or unix2_chkpwd commands.
2
Rule
Severity: Medium
The SUSE operating system must audit all uses of the sudoers file and all files in the /etc/sudoers.d/ directory.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the creat, open, openat, open_by_handle_at, truncate, and ftruncate system calls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the setxattr, fsetxattr, lsetxattr, removexattr, fremovexattr, and lremovexattr system calls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chown, fchown, fchownat, and lchown system calls.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the sudoedit command.
2
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the mount system call.
2
Rule
Severity: Low
The SUSE operating system must generate audit records for all uses of the umount system call.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the insmod command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the rmmod command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the modprobe command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the chcon command.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the delete_module system call.
2
Rule
Severity: Medium
The SUSE operating system must generate audit records for all uses of the init_module and finit_module system calls.
4
Rule
Severity: Medium
Audit records must include what type of events occurred.
2
Rule
Severity: Medium
The VMM must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
The ESXi host must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
VAMI must produce log records containing sufficient information to establish what type of events occurred.
1
Rule
Severity: Medium
Performance Charts must record user access in a format that enables monitoring of remote access.
4
Rule
Severity: Medium
The vCenter Server must produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
ESX Agent Manager must record user access in a format that enables monitoring of remote access.
1
Rule
Severity: Medium
Lookup Service must record user access in a format that enables monitoring of remote access.
3
Rule
Severity: Medium
The ESXi must produce audit records containing information to establish what type of events occurred.
3
Rule
Severity: Medium
The ESXi host must forward audit records containing information to establish what type of events occurred.
4
Rule
Severity: Medium
The Photon operating system must configure auditd to log to disk.
3
Rule
Severity: Medium
The vCenter ESX Agent Manager service must produce log records containing sufficient information regarding event details.
1
Rule
Severity: Medium
VMware Postgres log files must contain required fields.
1
Rule
Severity: Medium
The Security Token Service must record user access in a format that enables monitoring of remote access.
3
Rule
Severity: Medium
The vCenter Lookup service must produce log records containing sufficient information regarding event details.
1
Rule
Severity: Medium
vSphere UI must record user access in a format that enables monitoring of remote access.
3
Rule
Severity: Medium
The vCenter Perfcharts service must produce log records containing sufficient information regarding event details.
3
Rule
Severity: Medium
The vCenter PostgreSQL service must produce logs containing sufficient information to establish what type of events occurred.
3
Rule
Severity: Medium
The vCenter STS service must produce log records containing sufficient information regarding event details.
3
Rule
Severity: Medium
The vCenter UI service must produce log records containing sufficient information regarding event details.
3
Rule
Severity: Medium
The vCenter VAMI service must produce log records containing sufficient information to establish what type of events occurred.
2
Rule
Severity: Medium
The web server must produce log records containing sufficient information to establish what type of events occurred.
1
Rule
Severity: Medium
The BIG-IP AFM module must be configured to produce audit records containing information to establish what type of events occurred.
1
Rule
Severity: Medium
The BIG-IP ASM module must be configured to produce ASM Event Logs containing information to establish what type of unauthorized events occurred.
1
Rule
Severity: Medium
Ubuntu 22.04 LTS must have the "auditd" package installed.
1
Rule
Severity: Medium
Ubuntu 22.04 LTS must produce audit records and reports containing information to establish when, where, what type, the source, and the outcome for all DOD-defined auditable events and actions in near real time.
1
Rule
Severity: Medium
The Enterprise Voice, Video, and Messaging Endpoint must be configured to produce session (call detail) records containing what type of connection occurred.
1
Rule
Severity: Medium
The F5 BIG-IP appliance must generate event log records that can be forwarded to the centralized events log.
1
Rule
Severity: Medium
The Enterprise Voice, Video, and Messaging Session Manager must produce session (call) records containing the type of session connection.
1
Rule
Severity: Medium
The F5 BIG-IP appliance must generate traffic log entries containing information to establish the details of the event, including success or failure of the application of the firewall rule.
1
Rule
Severity: Medium
The F5 BIG-IP appliance must be configured to audit the execution of privileged functions such as accounts additions and changes.
1
Rule
Severity: Medium
MongoDB must provide audit record generation for DOD-defined auditable events within all DBMS/database components.
1
Rule
Severity: Medium
The OL 8 audit package must be installed.
1
Rule
Severity: Medium
SLEM 5 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chacl" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chage" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chcon" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chfn" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chmod" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for a uses of the "chsh" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "crontab" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "gpasswd" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "insmod" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "kmod" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "modprobe" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "newgrp" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "pam_timestamp_check" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "passwd" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "rm" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "rmmod" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "setfacl" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "ssh-agent" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "ssh-keysign" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "su" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "sudo" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "sudoedit" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "unix_chkpwd" or "unix2_chkpwd" commands.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "usermod" command.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chmod", "fchmod" and "fchmodat" system calls.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "chown", "fchown", "fchownat", and "lchown" system calls.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "creat", "open", "openat", "open_by_handle_at", "truncate", and "ftruncate" system calls.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "delete_module" system call.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "init_module" and "finit_module" system calls.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "mount" system call.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "setxattr", "fsetxattr", "lsetxattr", "removexattr", "fremovexattr", and "lremovexattr" system calls.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all uses of the "umount" system call.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all modifications to the "lastlog" file.
1
Rule
Severity: Medium
SLEM 5 must generate audit records for all modifications to the "tallylog" file must generate an audit record.
1
Rule
Severity: Medium
SLEM 5 must audit all uses of the sudoers file and all files in the "/etc/sudoers.d/" directory.
1
Rule
Severity: Medium
The TPS must provide audit record generation capability for detection events based on implementation of policy filters, rules, signatures, and anomaly analysis.
1
Rule
Severity: High
The TippingPoint SMS must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).
1
Rule
Severity: Medium
TOSS audit records must contain information to establish what type of events occurred, when the events occurred, the source of events, where events occurred, and the outcome of events.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "chage" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "chcon" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the ssh-agent in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "passwd" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of postdrop in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of postqueue in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of setsebool in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the ssh-keysign in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "setfacl" command in RTOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "pam_timestamp_check" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "newgrp" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "init_module" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "rename" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "renameat" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "rmdir" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "unlink" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "unlinkat" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "finit_module" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "delete_module" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "crontab" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "chsh" command in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of setfiles in TOSS must generate an audit record.
1
Rule
Severity: Medium
Successful/unsuccessful uses of the "chacl" command in TOSS must generate an audit record.
1
Rule
Severity: Info
The NSX Distributed Firewall must generate traffic log entries.
1
Rule
Severity: Medium
The NSX Tier-0 Gateway Firewall must generate traffic log entries.
Patternfly
PatternFly elements
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.
Modules