The Juniper EX switch must be configured to limit the number of concurrent management sessions to 10 or an organization-defined value.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-253878	SRG-APP-000001-NDM-000200	JUEX-NM-000010	SV-253878r1028864_rule	2025-03-07	2

Description
Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to denial-of-service (DoS) attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions must be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions. Juniper switches apply session limits per access method (e.g., web management, SSH), which means the limit is applicable to local, remote, and root account sessions. Unconfigured management access methods are disabled. For instance, if there is no [edit system services ssh] stanza, that service is unavailable and a connection-limit should not be configured because that will enable the service.

Description

Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to denial-of-service (DoS) attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions must be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions. Juniper switches apply session limits per access method (e.g., web management, SSH), which means the limit is applicable to local, remote, and root account sessions. Unconfigured management access methods are disabled. For instance, if there is no [edit system services ssh] stanza, that service is unavailable and a connection-limit should not be configured because that will enable the service.

ℹ️ Check
If, based on operational needs, an organization defined number other than 1 is used, document the value in the SSP. View the SSH service configuration using the "show configuration system services ssh" command. SSH example. user@host> show configuration system services ssh connection-limit 1; rate-limit 1 If the device does not limit the number of concurrent management sessions to 1 or an organization-defined number, this is a finding.

ℹ️ Check

If, based on operational needs, an organization defined number other than 1 is used, document the value in the SSP. View the SSH service configuration using the "show configuration system services ssh" command. SSH example. user@host> show configuration system services ssh connection-limit 1; rate-limit 1 If the device does not limit the number of concurrent management sessions to 1 or an organization-defined number, this is a finding.

✔️ Fix
Enter the CLI configuration mode and enter the following commands to set the connection-limit to 1 or an organization defined number. If, based on operational needs, an organization defined number other than 1 is used, document the value in the SSP. SSH example limiting connections to 1: user@host> configure user@host# set system services ssh connection-limit 1 user@host# commit