TOSS 5 must produce audit records containing information to establish the identity of any individual or process associated with the event.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-282530	TOSS-05-000404	SV-282530r1200570_rule	CCI-001487	medium
Description
Without establishing what type of events occurred, the source of events, where events occurred, and the outcome of events, 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.
STIG			Date
Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide			2026-04-01

Details

Check Text (C-282530r1200570_chk)

Verify TOSS 5 audit system is configured to resolve audit information before writing to disk using 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 (F-86996r1200569_fix)

Edit the /etc/audit/auditd.conf file and add or update the "log_format" option: log_format = ENRICHED Restart the audit daemon for the changes to take effect.