SV-271595r1155316: OL 9 must be configured so that successful/unsuccessful uses of the umount2 system call generate an audit record. | Oracle Linux 9 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

OL 9 must be configured so that successful/unsuccessful uses of the umount2 system call generate an audit record.

Description

Discussion Text

The changing of file permissions could indicate that a user is attempting to gain access to information that would otherwise be disallowed. Auditing discretionary access control (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

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000130Not mappedCCI-000169Not mappedCCI-002884Not mappedCCI-000172

References

DPMS Target Oracle Linux 9 DISA DPMS Target Oracle Linux 9 5680

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.ol9os:def:271595
# OL 9 must be configured so that successful/unsuccessful uses of the umount2 system call generate an audit record.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Audit 32-bit invocations of umount2 syscall
# textfilecontent54_object (textfilecontent54_test)
test_1() {
  grep -Pq '^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b32\s+(?:.*(-S\s+umount2\s+|(\s+|,)umount2(\s+|,))).*-F\s+auid>=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$' '/etc/audit/audit.rules' &>/dev/null
}
# Audit 64-bit invocations of umount2 syscall
# textfilecontent54_object (textfilecontent54_test)
test_2() {
  grep -Pq '^\s*-a\s+(always,exit|exit,always)\s+-F\s+arch=b64\s+(?:.*(-S\s+umount2\s+|(\s+|,)umount2(\s+|,))).*-F\s+auid>=1000\s+-F\s+auid!=(4294967295|-1|unset)(\s+(-k\s+|-F\s+key=)[-\w]+)*\s*$' '/etc/audit/audit.rules' &>/dev/null
}

if ( test_1 && test_2 ); then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# Implementing DISA STIG OL 9 rule oval:mil.disa.stig.ol9os:def:271595

if [ ! -f "/etc/audit/audit.rules" ]; then
    echo "FAIL"
    exit 1
fi

if [ $(grep -c "^\\s*-a\\s+(always,exit|exit,always)\\s+-F\\s+arch=b32\\s+(?:.*(-S\\s+umount2\\s+|(\\s+|,)umount2(\\s+|,))).*-F\\s+auid>=1000\\s+-F\\s+auid != (4294967295|-1|unset)(\\s+(-k\\s+|-F\\s+key=)[-\\w]+)*\\s*$" /etc/audit/audit.rules) -ge 1 ] && \
[ $(grep -c "^\\s*-a\\s+(always,exit|exit,always)\\s+-F\\s+arch=b64\\s+(?:.*(-S\\s+umount2\\s+|(\\s+|,)umount2(\\s+|,))).*-F\\s+auid>=1000\\s+-F\\s+auid != (4294967295|-1|unset)(\\s+(-k\\s+|-F\\s+key=)[-\\w]+)*\\s*$" /etc/audit/audit.rules) -ge 1 ]; then
    echo "PASS"
    exit 0
else
    echo "FAIL"
    exit 1
fi

Remediation

Configure the audit system to generate an audit event for any successful/unsuccessful use of the umount2 system call by adding the following rules to a rules file in /etc/audit/rules.d/ directory: (Example /etc/audit/rules.d/audit.rules)

-a always,exit -F arch=b32 -S umount2 -F auid>=1000 -F auid!=unset -k perm_mod
-a always,exit -F arch=b64 -S umount2 -F auid>=1000 -F auid!=unset -k perm_mod

The audit daemon must be restarted for the changes to take effect.

Restart auditd:
$ sudo service auditd restart