STIGUI
V-261411CAT II — Medium severitySV-261411r996646_rule

SLEM 5 audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.

Rule version SLEM-05-653015 · STIG v1 · 2026-08-20

Discussion

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.

Associating event types with detected events in SLEM 5 audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured SLEM 5.

Check

Verify SLEM 5 produces audit records with the following commands:

     > systemctl is-active auditd.service
     active
     > systemctl is-enabled auditd.service
     enabled

If the service is not active or not enabled, this is a finding.

Fix

Enable SLEM 5 auditd service by using the following commands:

     > sudo systemctl enable auditd.service
     > sudo systemctl start auditd.service

Identifiers

Group ID
V-261411
Group title
SRG-OS-000037-GPOS-00015
Rule ID
SV-261411r996646_rule
Check ID
C-65140r996098_chk
Fix ID
F-65048r996099_fix