TOSS must generate audit records containing the full-text recording of privileged commands.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-252974 | TOSS-04-030060 | SV-252974r958422_rule | CCI-000135 | medium |
| Description | ||||
| 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 commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. | ||||
| STIG | Date | |||
| Tri-Lab Operating System Stack (TOSS) 4 Security Technical Implementation Guide | 2025-05-08 | |||
Details
Check Text (C-252974r958422_chk)
Verify that an audit event is generated for any successful/unsuccessful use of the "sudo" command by performing the following command to check the file system rules in "/etc/audit/audit.rules":
$ sudo grep -w sudo /etc/audit/audit.rules
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd
If the command does not return a line, or the line is commented out, this is a finding.
Fix Text (F-56377r824245_fix)
Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudo" command by adding or updating the following rule in the "/etc/audit/rules.d/audit.rules" file:
-a always,exit -F path=/usr/bin/sudo -F perm=x -F auid>=1000 -F auid!=unset -k priv_cmd
The audit daemon must be restarted for the changes to take effect.