Information
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
At a minimum, the organization must audit the full-text recording of privileged access commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
When a user logs on, the auid is set to the uid of the account that is being authenticated. Daemons are not user sessions and have the loginuid set to -1. The auid representation is an unsigned 32-bit integer, which equals 4294967295. The audit system interprets -1, 4294967295, and 'unset' in the same way.
Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000042-GPOS-00020, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215
Solution
Configure the operating system to generate audit records when successful/unsuccessful attempts to use the 'sudo' command occur.
Add or update the following rule in '/etc/audit/rules.d/audit.rules':
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k privileged-priv_change
The audit daemon must be restarted for the changes to take effect.
Item Details
Category: AUDIT AND ACCOUNTABILITY, MAINTENANCE
References: 800-53|AU-3, 800-53|AU-3(1), 800-53|AU-12c., 800-53|MA-4(1)(a), CAT|II, CCI|CCI-000130, CCI|CCI-000135, CCI|CCI-000172, CCI|CCI-002884, Rule-ID|SV-204548r958412_rule, STIG-ID|RHEL-07-030690, STIG-Legacy|SV-86785, STIG-Legacy|V-72161, Vuln-ID|V-204548
Control ID: ffb9adc0cd12bfc47e1a9f50f92ef84894219417f6860954d778e25b363e11db