Juniper Router NDM STIG Version Comparison

There are 5 differences between versions v2 r3 (June 7, 2023) (the "left" version) and v3 r2 (Jan. 30, 2025) (the "right" version).

Check JUNI-ND-000010 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

The Juniper router must be configured to limit the number of concurrent management sessions to an organization-defined number.

Check Content

Note: This requirement is not applicable to file transfer actions such as SCP and SFTP. Review the router configuration to determine if concurrent SSH sessions are limited as show shown in the example below: system { services { ssh { max-sessions-per-connection 1; 3; connection-limit 2; 3; } } If } Note: the max-sessions-per-connection must be set to 1 to limit the number of sessions per connection which is limited by the connection-limit. If the router is not configured to limit the number of concurrent sessions, this is a finding.

Discussion

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 (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 should 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.

Fix

Configure the router to limit the number of concurrent sessions as shown in the example below: [edit system services] set ssh connection-limit 2 set 3 set ssh max-sessions-per-connection 1 3