V-254143

Discussion

Without generating audit records specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter).

Check Content

Confirm Nutanix AOS generates audit records on all successful/unsuccessful attempts to access privileges occur.

$ sudo grep -iw creat /etc/audit/audit.rules
 -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid=0 -k access.
 -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid=0 -k access.
 -a always,exit -F arch=b64 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access.
 -a always,exit -F arch=b64 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access.
 -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid=0 -k access.
 -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid=0 -k access.
 -a always,exit -F arch=b32 -S creat -F exit=-EACCES -F auid>=1000 -F auid!=4294967295 -k access.
 -a always,exit -F arch=b32 -S creat -F exit=-EPERM -F auid>=1000 -F auid!=4294967295 -k access.

If the output does not contain all of the above rules, this is a finding.
If both the "b32" and "b64" audit rules are not defined for the listed syscall(s), this is a finding.