V-254164

Discussion

Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the operating system audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured operating system.

Check Content

Verify Nutanix AOS generates audit records when successful/unsuccessful attempts to use the following commands occur.

Check that the following system call is being audited by performing the following command to check the file system rules in "/etc/audit/audit.rules":

$ sudo auditctl -l | grep -iw /usr/bin/su /etc/audit/audit.rules
If the output is not -a always,exit -F path=/usr/bin/su -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged, this is a finding.

$ sudo auditctl -l | grep -iw /usr/bin/sudo /etc/audit/audit.rules
If the output is not -a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged, this is a finding.

$ sudo grep -i "/etc/sudoers" /etc/audit/audit.rules
If the output is not -w /etc/sudoers -p wa -k actions, this is a finding.

$ sudo grep -i "/etc/sudoers.d/" /etc/audit/audit.rules
If the output is not -w /etc/sudoers.d/ -p wa -k actions, this is a finding.

$ sudo grep -i /usr/bin/newgrp /etc/audit/audit.rules
If the output is not -a always,exit -F path=/usr/bin/newgrp -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged, this is a finding.

$ sudo grep -i /usr/bin/chsh /etc/audit/audit.rules
If the output is not -a always,exit -F path=/usr/bin/chsh -F perm=x -F auid>=1000 -F auid!=4294967295 -k privileged, this is a finding.