|Finding ID||Version||Rule ID||IA Controls||Severity|
|Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. At a minimum, the organization must audit the full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000062-GPOS-00031, SRG-OS-000392-GPOS-00172, SRG-OS-000462-GPOS-00206, SRG-OS-000471-GPOS-00215|
|SUSE Linux Enterprise Server 15 Security Technical Implementation Guide||2022-12-07|
|Check Text ( C-38122r619071_chk )|
| Verify the SUSE operating system generates an audit record for all uses of the "mount" system call. |
Check that the system call is being audited by performing the following command:
> sudo auditctl -l | grep -w 'mount'
-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=-1 -k privileged-mount
-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=-1 -k privileged-mount
If both the "b32" and "b64" audit rules are not defined for the "mount" syscall, this is a finding.
The "-k" allows for specifying an arbitrary identifier. The string following "-k" does not need to match the example output above.
|Fix Text (F-38085r619072_fix)|
| Configure the SUSE operating system to generate an audit record for all uses of the "mount" system call. |
Add or update the following rules to "/etc/audit/rules.d/audit.rules":
-a always,exit -F arch=b32 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
-a always,exit -F arch=b64 -S mount -F auid>=1000 -F auid!=4294967295 -k privileged-mount
To reload the rules file, restart the audit daemon
> sudo systemctl restart auditd.service
or issue the following command:
> sudo augenrules --load