Details

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 on all configured login classes as shown in the example below.

[edit system login]
set class ADMIN idle-timeout 10

Supportive Information

The following resource is also helpful.

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

This security hardening control applies to the following category of controls within NIST 800-53: System and Communications Protection.This control applies to the following type of system Juniper.

References

• 800-53|SC-10
• CAT|I
• CCI|CCI-001133
• CSCv6|16.4
• Rule-ID|SV-101241r1_rule
• STIG-ID|JUNI-ND-000710
• Vuln-ID|V-91141

Source

• Tenable.com/audits