InformationThe auditing daemon, auditd , stores log data in the /var/log/audit directory.
There are two important reasons to ensure that data gathered by auditd is stored on a separate partition: protection against resource exhaustion (since the audit.log file can grow quite large) and protection of audit data. The audit daemon calculates how much free space is left and performs actions based on the results. If other processes (such as syslog ) consume space in the same partition as auditd , it may not perform as desired.
SolutionFor new installations, during installation create a custom partition setup and specify a separate partition for /var/log/audit .
For systems that were previously installed, create a new partition and configure /etc/fstab as appropriate.
Resizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations.
AJ Lewis, 'LVM HOWTO', http://tldp.org/HOWTO/LVM-HOWTO/
When modifying /var/log/audit it is advisable to bring the system to emergency mode (so auditd is not running), rename the existing directory, mount the new file system, and migrate the data over before returning to multiuser mode.
This Benchmark recommendation maps to:
Red Hat Enterprise Linux 7 Security Technical Implementation Guide:
Version 2, Release: 3 Benchmark Date: 26 Apr 2019
Vul ID: V-72063
Rule ID: SV-86687r6_rule
STIG ID: RHEL-07-021330
Severity: CAT III