CASA-FW-000090 - The Cisco ASA must be configured to queue log records locally in the event that the central audit server is down or not reachable - Queue

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


It is critical that when the network element is at risk of failing to process traffic 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 on the nature of the failure mode.

In accordance with DoD policy, the traffic log must be sent to a central audit server. When logging functions are lost, system processing cannot be shut down because firewall availability is an overriding concern given the role of the firewall in the enterprise. The system should either be configured to log events to an alternative server or queue log records locally. Upon restoration of the connection to the central audit server, action should be taken to synchronize the local log data with the central audit server.

If the central audit server uses User Datagram Protocol (UDP) communications instead of a connection oriented protocol such as TCP, a method for detecting a lost connection must be implemented.


To continue to allow new connections and queue log records in the event the syslog server is not reachable, configure logging buffered and increase the queue size as shown in the example below.

ASA(config)# logging buffered informational
ASA(config)# logging queue 8192

See Also

Item Details

References: CAT|II, CCI|CCI-000140, Rule-ID|SV-239857r665857_rule, STIG-ID|CASA-FW-000090, Vuln-ID|V-239857

Plugin: Cisco

Control ID: 7d278dff8694d4ef7739f62b8c279b4b4edd9b72034ed3ca97435536ebe5a14a