STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide

V-282429

CAT II (Medium)

TOSS 5 must take appropriate action when a critical audit processing failure occurs.

Rule ID

SV-282429r1200267_rule

STIG

Tri-Lab Operating System Stack (TOSS) 5 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000139

Discussion

It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded.

Check Content

Verify the audit service is configured to panic on a critical error using the following command:

$ sudo grep "\-f" /etc/audit/audit.rules 

-f 2

If the value for "-f" is not "2", and availability is not documented as an overriding concern, this is a finding.

Fix Text

Configure TOSS 5 to shut down when auditing failures occur.

Add the following line to the bottom of the "/etc/audit/audit.rules" file:

-f 2