From SLES 12 Security Technical Implementation Guide
Part of SRG-OS-000037-GPOS-00015
Associated with: CCI-000130 CCI-000169 CCI-000172 CCI-002884
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.
Verify the SUSE operating system generates an audit record for all uses of the "kmod" command. Check that the following command call is being audited by performing the following command on the system rules in "/etc/audit/audit.rules": # sudo grep kmod /etc/audit/audit.rules -w /usr/bin/kmod -p x -k modules If the system is configured to audit the execution of the module management program "kmod", the command will return a line. If the command does not return a line, this is a finding.
Configure the SUSE operating system to audit the execution of the module management program "kmod" by adding the following line to "/etc/audit/audit.rules": -w /usr/bin/kmod -p x -k modules
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer