STIGQter STIGQter: STIG Summary: Red Hat Enterprise Linux 9 Security Technical Implementation Guide Version: 2 Release: 9 Benchmark Date: 01 Jul 2026:

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

DISA Rule

SV-258155r1045300_rule

Vulnerability Number

V-258155

Group Title

SRG-OS-000341-GPOS-00132

Rule Version

RHEL-09-653030

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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.

Check Contents

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.

Vulnerability Number

V-258155

Documentable

False

Rule Version

RHEL-09-653030

Severity Override Guidance

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.

Check Content Reference

M

Target Key

5551