Title

SLEM 5 must generate audit records for all uses of the "sudoedit" command. (Cat II impact)

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

Verify an audit record is generated for all uses of the "sudoedit" command with the following command: > sudo auditctl -l | grep -w '/usr/bin/sudoedit' -a always,exit -S all -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -F key=privileged-sudoedit If the command does not return any output or the returned line is commented out, this is a finding. Note: The "key=" value is arbitrary and can be different from the example output above.

Fix Text

Configure SLEM 5 to generate an audit record for all uses of the "sudoedit" command. Add or modify the following line in the "/etc/audit/rules.d/audit.rules" file: -a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=unset -k privileged-sudoedit To reload the rules file, restart the audit daemon: > sudo systemctl restart auditd.service or issue the following command: > sudo augenrules --load

Additional Identifiers

Rule ID: SV-261446r996745_rule

Vulnerability ID: V-261446

Group Title: SRG-OS-000037-GPOS-00015

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.