Detections
Analytics
UBTU-20-010162 - The Ubuntu operating system must generate audit records for successful/unsuccessful uses of the sudoedit command.
Information
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).
Solution
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!=unset -k priv_cmd
To reload the rules file, issue the following command:
$ sudo augenrules --load
Note: The "-k <keyname>" at the end of the line gives the rule a unique meaning to help during an audit investigation. The <keyname> does not need to match the example above.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_CAN_Ubuntu_20-04_LTS_V2R4_STIG.zip
Item Details
Audit Name: DISA Canonical Ubuntu 20.04 LTS STIG v2r4
Category: AUDIT AND ACCOUNTABILITY
References: 800-53|AU-12c., CAT|II, CCI|CCI-000172, Rule-ID|SV-238278r958446_rule, STIG-ID|UBTU-20-010162, Vuln-ID|V-238278
Plugin: Unix
Control ID: 921c9502e48c27b43ba61ed29d8f3955a122274c34615008bcfe23b942bcbe19