The Juniper router must be configured to limit the number of concurrent management sessions to an organization-defined number.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-217305 | SRG-APP-000001-NDM-000200 | JUNI-ND-000010 | SV-217305r1050884_rule | 2024-12-05 | 3 |
| 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 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. |
| ℹ️ Check |
|---|
| 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 shown in the example below: system { services { ssh { max-sessions-per-connection 3; connection-limit 3; } } If the router is not configured to limit the number of concurrent sessions, this is a finding. |
| ✔️ Fix |
|---|
| Configure the router to limit the number of concurrent sessions as shown in the example below: [edit system services] set ssh connection-limit 3 set ssh max-sessions-per-connection 3 |