|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 18.04 LTS Security Technical Implementation Guide||2022-12-06|
|Check Text ( C-21024r305225_chk )|
| Verify if the Ubuntu operating system is configured to audit the execution of the module management program "kmod". |
Check the currently configured audit rules with the following command:
# sudo auditctl -l | grep kmod
-w /bin/kmod -p x -k module
If the command does not return a line, 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-21023r305226_fix)|
| Configure the Ubuntu operating system to audit the execution of the module management program "kmod". |
Add or update the following rule in the "/etc/audit/rules.d/stig.rules" file.
-w /bin/kmod -p x -k modules
The "root" account must be used to view/edit any files in the /etc/audit/rules.d/ directory.
In order to reload the rules file, issue the following command:
# sudo augenrules --load