AIX7-00-002003 - AIX must produce audit records containing information to establish where the events occurred.

Information

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.

In order 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 AIX provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Reset the audit system with the following command:
# /usr/sbin/audit shutdown

Start the audit system with the following command:
# /usr/sbin/audit start

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_IBM_AIX_7-x_V2R5_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-3, CAT|II, CCI|CCI-000132, Rule-ID|SV-215237r508663_rule, STIG-ID|AIX7-00-002003, STIG-Legacy|SV-101349, STIG-Legacy|V-91249, Vuln-ID|V-215237

Plugin: Unix

Control ID: 19189f8f12d89dccecb8e3a2da9af7dad58b29940191ba49db6978ed5f651939