TOSS 5 audit service must be enabled.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-282438 | TOSS-05-000387 | SV-282438r1200294_rule | CCI-000169 | medium |
| Description | ||||
| Without establishing what type of events occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Ensuring the "auditd" service is active ensures audit records generated by the kernel are appropriately recorded. Additionally, a properly configured audit subsystem ensures that actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions. Satisfies: SRG-OS-000062-GPOS-00031, SRG-OS-000352-GPOS-00140, SRG-OS-000353-GPOS-00141, SRG-OS-000354-GPOS-00142, SRG-OS-000358-GPOS-00145, SRG-OS-000365-GPOS-00152, SRG-OS-000392-GPOS-00172, SRG-OS-000475-GPOS-00220 | ||||
| STIG | Date | |||
| Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide | 2026-04-01 | |||
Details
Check Text (C-282438r1200294_chk)
Verify the audit service is configured to produce audit records using the following command:
$ systemctl status auditd.service
auditd.service - Security Auditing Service
Loaded:loaded (/usr/lib/systemd/system/auditd.service; enabled; vendor preset: enabled)
Active: active (running) since Tues 2022-05-24 12:56:56 EST; 4 weeks 0 days ago
If the audit service is not "active" and "running", this is a finding.
Fix Text (F-86904r1200293_fix)
To enable the audit service, run the following command:
$ sudo systemctl enable --now auditd