STIGhubSTIGhub
STIGsSearchCompare

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
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 7 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper EX Series Switches Network Device Management Security Technical Implementation Guide

V-253913

CAT I (High)

The Juniper EX switch must be configured to end all network connections associated with a device management session at the end of the session, or the session must be terminated after five minutes of inactivity except to fulfill mission requirements.

Rule ID

SV-253913r1082962_rule

STIG

Juniper EX Series Switches Network Device Management Security Technical Implementation Guide

Version

V2R4

CCIs

CCI-001133

Discussion

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.

Check Content

Determine if the network device terminates the connection associated with a device management session at the end of the session or after five minutes of inactivity. This requirement may be verified by demonstration or configuration review. 

Junos permits the administrator to log out at the end of the session, which terminates the session and the network connection. Junos forcibly terminates the session and network connection upon exceeding the inactivity timeout threshold. Inactivity timeouts are assigned to login classes and apply to every administrative access method; there is no provision to set inactivity timeout differently for local (console) and network (remote) device management sessions. Verify the idle-timeout for the root user, and each login class, has an appropriate idle-timeout value.

user@host> show configuration system login
...
idle-timeout 5;
class <name> {
    idle-timeout 5;
...
}

Note: Inactivity timeout (idle-timeout) must be assigned to every login class.

If the network device does not terminate the connection associated with a device management session at the end of the session or after five minutes of inactivity, this is a finding.

Fix Text

Configure the network device to terminate the connection associated with a device management session at the end of the session or after five minutes of inactivity.

There is no configuration required to support explicit logout ("quit"  at the end of the session).
1. Enter configuration mode.
2. Configure inactivity timeout for root.
3. Configure inactivity timeout for all login classes.
4. Commit the configuration.

user@host> configure
user@host# set system login idle-timeout 5
user@host# set system login class <class name> idle-timeout 5
user@host# commit