Title

Ubuntu OS must generate audit records for successful/unsuccessful attempts to use the kmod 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 Ubuntu OS is configured to audit the execution of the module management program "kmod" by using 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" value is arbitrary and can be different from the example output above.

Fix Text

Configure Ubuntu OS to audit the execution of the module management program "kmod". Add or modify the following line in the "/etc/audit/rules.d/stig.rules" file: -w /bin/kmod -p x -k modules 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.

Additional Identifiers

Rule ID: SV-275698r1148144_rule

Vulnerability ID: V-275698

Group Title: SRG-OS-000477-GPOS-00222

Expert Comments

CCIs tied to check.

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