STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Oracle Linux 8 Security Technical Implementation Guide

V-248731

CAT II (Medium)

OL 8 must resolve audit information before writing to disk.

Rule ID

SV-248731r991589_rule

STIG

Oracle Linux 8 Security Technical Implementation Guide

Version

V2R8

CCIs

CCI-000366

Discussion

Without establishing what type of events occurred and their 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 Content

Verify the OL 8 audit daemon 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 Text

Configure OL 8 to resolve audit information before writing to disk by adding the following line to the "/etc/audit/auditd.conf" file and add or update the "log_format" option: 
 
log_format = ENRICHED 
 
The audit daemon must be restarted for changes to take effect.