Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-254166 | NUTX-OS-000640 | SV-254166r846586_rule | Medium |
Description |
---|
Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as operating system components, modules, device identifiers, node names, file names, and functionality. Associating information about where the event occurred within the operating system provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system. |
STIG | Date |
---|---|
Nutanix AOS 5.20.x OS Security Technical Implementation Guide | 2022-08-24 |
Check Text ( C-57651r846584_chk ) |
---|
Verify the operating system produces audit records containing information to establish when (date and time) the events occurred. Determine if auditing is active by issuing the following command: $ sudo systemctl is-active auditd.service active If the "auditd" status is not active, this is a finding. |
Fix Text (F-57602r846585_fix) |
---|
Enable the auditd service to run automatically. $ sudo systemctl enable auditd |