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 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Riverbed NetIM NDM Security Technical Implementation Guide

V-275457

CAT III (Low)

The Riverbed NetIM must generate an alert of all audit failure events.

Rule ID

SV-275457r1147421_rule

STIG

Riverbed NetIM NDM Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001849

Discussion

To ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. The value for the organization-defined audit record storage requirement will depend on the amount of storage available on the network device, the anticipated volume of logs, the frequency of transfer from the network device to centralized log servers, and other factors.

Check Content

Verify the system administrator (SA) and information system security officer (ISSO) are notified in the event of an audit processing failure by using the following command: 
  
     $ sudo grep -i action_mail_acct /etc/rsyslog.d
     action_mail_acct = <administrator_email_account> 
  
If "action_mail_acct" is not set to the email address of the SA and/or ISSO, is commented out, or is missing, this is a finding.

Fix Text

Configure the "/etc/rsyslog.d" service to notify the SA and ISSO in the event of an audit processing failure.

1. Add or modify the following line in the "/etc/rsyslog.d" file: 
  
action_mail_acct = <administrator_email_account>  
  
Note: Change "administrator_email_account" to the email address of the SA and/or ISSO. 
  
2. Restart rsyslog service.

     $ sudo service rsyslog restart

Note: An email package must be installed on the system for email notifications to be sent.