OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco ASA must be configured to queue log records locally in the event that the central audit server is down or not reachable.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-239857CASA-FW-000090SV-239857r665857_ruleCCI-000140medium
Description
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.
STIGDate
Cisco ASA Firewall Security Technical Implementation Guide2024-06-06

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-05Response To Event Log Processing Failures
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (24) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-14(1)System Start-up
1.00
AU-3Content of Audit Records
1.00
AU-3(1)Additional Audit Information
1.00
AU-3(2)Centralized Management of Planned Audit Record Content
1.00
AU-4Audit Log Storage Capacity
1.00

+14 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.3.4
1.00
CCI1 mapping
CCI-000140
1.00

Details

Check Text (C-239857r665857_chk)

Review the ASA configuration and verify that logging to the buffer is enabled and that the queue size has been increased as shown in the example below. logging enable logging buffered informational logging queue 8192 logging host NDM_INTERFACE 10.1.22.2 6/1514 Note: Configuring a value of 0 for the queue size will set it to maximum size for the specific platform. If the ASA is not configured to queue log records locally In the event that the central audit server is down or not reachable, this is a finding.

Fix Text (F-43049r665856_fix)

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