Vulnerability Discussion

Without establishing what type of events occurred, along with the source, location, and outcome, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.

Audit record content that may be necessary to satisfy this requirement includes, for example, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.

Enriched logging aids in making sense of who, what, and when events occur on a system. Without this, determining root cause of an event will be much more difficult.

Check

Verify the RHEL 10 audit system is configured to resolve audit information before writing to disk with the following command:

$ sudo grep log_format /etc/audit/auditd.conf
log_format = ENRICHED

If the "log_format" option is not "ENRICHED", or the line is commented out, this is a finding.

Fix

Configure RHEL 10 audit system to resolve audit information before writing to disk.

Edit the "/etc/audit/auditd.conf" file and add or update the "log_format" option:

log_format = ENRICHED

Restart the audit daemon with the following command for the changes to take effect:

$ sudo service auditd restart