|Finding ID||Version||Rule ID||IA Controls||Severity|
|Without generating audit records that are 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).|
|Canonical Ubuntu 20.04 LTS Security Technical Implementation Guide||2022-12-06|
|Check Text ( C-41488r654007_chk )|
| Verify the Ubuntu operating system generates an audit record upon successful/unsuccessful attempts to use the "sudoedit" command. |
Check the configured audit rules with the following commands:
$ sudo auditctl -l | grep /usr/bin/sudoedit
-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=-1 -k priv_cmd
If the command does not return a line that matches the example or the line is commented out, this is a finding.
Note: The "-k" allows for specifying an arbitrary identifier, and the string after it does not need to match the example output above.
|Fix Text (F-41447r654008_fix)|
| Configure the audit system to generate an audit event for any successful/unsuccessful use of the "sudoedit" command. |
Add or update the following rules in the "/etc/audit/rules.d/stig.rules":
-a always,exit -F path=/usr/bin/sudoedit -F perm=x -F auid>=1000 -F auid!=4294967295 -k priv_cmd
To reload the rules file, issue the following command:
$ sudo augenrules --load