SV-258155r1045300: RHEL 9 must allocate audit record storage capacity to store at least one week's worth of audit records. | Red Hat Enterprise Linux 9 STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

RHEL 9 must allocate audit record storage capacity to store at least one week's worth of audit records.

Description

Discussion Text

To ensure RHEL 9 systems have a sufficient storage capacity in which to write the audit logs, RHEL 9 needs to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial installation of RHEL 9. Satisfies: SRG-OS-000341-GPOS-00132, SRG-OS-000342-GPOS-00133

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

IA Controls

NIST SP 800-53

Not mappedCCI-001849Not mappedCCI-001851

References

DPMS Target Red Hat Enterprise Linux 9 DISA DPMS Target Red Hat Enterprise Linux 9 5551

Checks

DISA STIG (Manual Reference)

Verify RHEL 9 allocates audit record storage capacity to store at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.

Note: The partition size needed to capture a week of audit records is based on the activity level of the system and the total storage capacity available. Typically 10.0GB of storage space for audit records should be sufficient.

Determine which partition the audit records are being written to with the following command:

$ sudo grep -w log_file /etc/audit/auditd.conf

log_file = /var/log/audit/audit.log 

Check the size of the partition that audit records are written to with the following command and verify whether it is sufficiently large:

 # df -h /var/log/audit/

/dev/sda2 24G 10.4G 13.6G 43% /var/log/audit 

If the audit record partition is not allocated for sufficient storage capacity, this is a finding.

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.rhel9os:def:258155
# RHEL 9 must allocate audit record storage capacity to store at least one week's worth of audit records.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.
#
# MANUAL REVIEW REQUIRED -- the module(s) below could not be reconstructed
# into working code from curated SCC reference data, and are excluded from
# the automated result:
#   - variable_object (variable_test) -- Audit file system total space >= 10GiB: no extractor for field "value"

# Audit file system exists
# partition_object (partition_test)
test_1() {
  findmnt -n -o FSTYPE,OPTIONS  &>/dev/null
}

if test_1; then
  echo "PASS (automated portion only -- MANUAL REVIEW still required, see notes above)"
else
  echo "FAIL (or see MANUAL REVIEW note above)"
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
# OVAL Definition: oval:mil.disa.stig.rhel9os:def:258155

if [ ! -s /etc/audit/auditd.conf ]; then echo "PASS"; exit 0; fi
if [ $(grep -c "^\\s*log_file\\s*=\\s*(\\S+)" /etc/audit/auditd.conf) -ge 1 ]; then mount_point=$(grep "^\\s*log_file\\s*=\\s*" /etc/audit/auditd.conf | sed 's/^.*=\s//'); fi
if [ -z "$mount_point" ]; then echo "PASS"; exit 0; fi
if [ ! -d "$mount_point" ]; then echo "FAIL"; exit 1; fi
size_kb=$(stat -c %s "$mount_point"/. 2>/dev/null)
if [ -z "$size_kb" ]; then echo "PASS"; exit 0; fi
size_gb=$(($size_kb / 1024 / 1024))
if [ $size_gb -ge 10 ]; then echo "PASS"; exit 0; else echo "FAIL"; exit 1; fi

Remediation

Allocate enough storage capacity for at least one week of audit records when audit records are not immediately sent to a central audit record storage facility.

If audit records are stored on a partition made specifically for audit records, resize the partition with sufficient space to contain one week of audit records.

If audit records are not stored on a partition made specifically for audit records, a new partition with sufficient space will need be to be created.