Juniper EX Series Switches Network Device Management STIG Version Comparison
Juniper EX Series Switches Network Device Management Security Technical Implementation Guide
Comparison
There are 8 differences between versions v1 r5 (Jan. 24, 2024) (the "left" version) and v2 r2 (Oct. 24, 2024) (the "right" version).
Check JUEX-NM-000350 was removed from the benchmark in the "right" version. The text below reflects the old wording.
This check's original form is available here.
Text Differences
Title
The Juniper EX switch must be configured to terminate all sessions and network connections when nonlocal device maintenance is completed.
Check Content
Determine if the network device terminates all sessions and network connections when nonlocal device maintenance is completed. This requirement may be verified by demonstration or validated test results. Junos permits the administrator to log out after completing nonlocal maintenance, which terminates the session and the network connection. Junos forcibly terminates the session and network connection if the idle-timeout value expires or when the permissible number of missed keepalive messages is reached. Verify the number of keepalive messages and the interval between messages is appropriate. For example, to forcibly disconnect a session after 30 seconds of lost connectivity: [edit system services ssh] : client-alive-count-max 3; client-alive-interval 10; Note: Administrator inactivity timeouts not shown because these are a separate check. If the network device does not terminate all sessions and network connections when nonlocal device maintenance is complete, this is a finding.
Discussion
If a device management session or connection remains open after management is completed, it may be hijacked by an attacker and used to compromise or damage the network device. Nonlocal device management and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. In the event the remote node has abnormally terminated or an upstream link from the managed device is down, the management session will be terminated, thereby freeing device resources and eliminating any possibility of an unauthorized user being orphaned to an open idle session of the managed device.
Fix
Configure the network device to terminate all sessions and network connections when nonlocal device maintenance is completed. set system services ssh client-alive-count-max <0..255> set system services ssh client-alive-interval <0..65535 seconds>