Title

Successful/unsuccessful uses of the umount system call in RHEL 9 must generate an audit record. (Cat II impact)

Discussion

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing DAC modifications can facilitate the identification of patterns of abuse among both authorized and unauthorized users. 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

Check Content

Verify that RHEL 9 generates an audit record for all uses of the "umount" and system call with the following command: $ sudo auditctl -l | grep b32 | grep 'umount\b' -a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=-1 -F key=privileged-umount If the command does not return a line, or the line is commented out, this is a finding.

Fix Text

Configure the audit system to generate an audit event for any successful/unsuccessful use of the "umount" system call by adding or updating the following rules in "/etc/audit/audit.rules" and adding the following rules to "/etc/audit/rules.d/perm_mod.rules" or updating the existing rules in files in the "/etc/audit/rules.d/" directory: -a always,exit -F arch=b32 -S umount -F auid>=1000 -F auid!=unset -k privileged-umount To load the rules to the kernel immediately, use the following command: $ sudo augenrules --load

Additional Identifiers

Rule ID: SV-258215r1045430_rule

Vulnerability ID: V-258215

Group Title: SRG-OS-000037-GPOS-00015

Expert Comments

CCIs tied to check.

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