UCF STIG Viewer Logo

SUSE operating system audit records must contain information to establish what type of events occurred, the source of events, where events occurred, and the outcome of events.


Finding ID Version Rule ID IA Controls Severity
V-234904 SLES-15-030050 SV-234904r854221_rule Medium
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 the SUSE operating system audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured SUSE operating system. Satisfies: SRG-OS-000037-GPOS-00015, SRG-OS-000038-GPOS-00016, SRG-OS-000039-GPOS-00017, SRG-OS-000040-GPOS-00018, SRG-OS-000041-GPOS-00019, SRG-OS-000042-GPOS-00021, SRG-OS-000051-GPOS-00024, SRG-OS-000054-GPOS-00025, SRG-OS-000122-GPOS-00063, SRG-OS-000254-GPOS-00095, SRG-OS-000255-GPOS-00096, SRG-OS-000392-GPOS-00172
SUSE Linux Enterprise Server 15 Security Technical Implementation Guide 2022-12-07


Check Text ( C-38092r618981_chk )
Verify the SUSE operating system produces audit records.

Check that the SUSE operating system produces audit records by running the following command to determine the current status of the auditd service:

> systemctl is-active auditd.service

> systemctl is-enabled auditd.service

If the service is not active or not enabled, this is a finding.
Fix Text (F-38055r618982_fix)
Enable the SUSE operating system auditd service by performing the following commands:

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