CASA-ND-000690 - The Cisco ASA must be configured to terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after 10 minutes of inactivity except to fulfill documented and validated mission requirements - http server

Warning! Audit Deprecated

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

View Next Audit Version

Information

Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element.

Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.

Solution

Set the idle timeout value to 10 minutes or less for console, ssh, and http (if ASDM is used) access.

SW1(config)# ssh timeout 10
SW1(config)# console timeout 10
ASA(config)# http server idle-timeout 10
SW1(config)# end

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Cisco_ASA_Y22M04_STIG.zip

Item Details

References: CAT|I, CCI|CCI-001133, Rule-ID|SV-239920r666196_rule, STIG-ID|CASA-ND-000690, Vuln-ID|V-239920

Plugin: Cisco

Control ID: dd538c65574ab1b11b85cb98f396e39c77ea08e39f7399aeba7b958e36ebe0c4