The TOSS 5 audit system must take appropriate action when an error writing to the audit storage volume occurs.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-282749 | TOSS-05-000388 | SV-282749r1201227_rule | CCI-000366 | medium |
| Description | ||||
| It is critical that when the operating system is at risk of failing to process audit logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware errors; failures in the audit capturing mechanisms; and audit storage capacity being reached or exceeded. Responses to audit failure depend upon the nature of the failure mode. | ||||
| STIG | Date | |||
| Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide | 2026-04-01 | |||
Details
Check Text (C-282749r1201227_chk)
Verify TOSS 5 takes the appropriate action when an audit processing failure occurs using the following command:
$ sudo grep disk_error_action /etc/audit/auditd.conf
disk_error_action = HALT
If the value of the "disk_error_action" option is not "SYSLOG", "SINGLE", or "HALT", or the line is commented out, ask the system administrator (SA) to indicate how the system takes appropriate action when an audit process failure occurs. If there is no evidence of appropriate action, this is a finding.
Fix Text (F-87215r1201226_fix)
Configure TOSS 5 to shut down by default upon audit failure (unless availability is an overriding concern).
Add or update the following line (depending on the configuration, "disk_error_action" can be set to "SYSLOG" or "SINGLE") in "/etc/audit/auditd.conf" file:
disk_error_action = HALT
If availability has been determined to be more important, and this decision is documented with the information system security officer (ISSO), configure the operating system to notify the SA and ISSO in the event of an audit processing failure by setting the "disk_error_action" to "SYSLOG".