Detections
Analytics

CISC-ND-000010 - The Cisco router must be configured to limit the number of concurrent management sessions to an organization-defined number.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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

Solution

Configure the router to limit the number of concurrent management sessions to an organization-defined number as shown in the example below.

R4(config)#ip http max-connections 2
R4(config)#line vty 0 1
R4(config-line)#transport input ssh
R4(config-line)#exit
R4(config)#line vty 2 4
R4(config-line)# transport input none
R4(config-line)#end

To configure session limiting, use the example below.

R4(config)#line vty 0 4
R4(config-line)#session-limit 2
R4(config-line)#transport input ssh

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Cisco_IOS_Router_Y26M04_STIG.zip

Item Details

Category: ACCESS CONTROL

References: 800-53|AC-10, CAT|II, CCI|CCI-000054, Rule-ID|SV-215662r1192908_rule, STIG-ID|CISC-ND-000010, STIG-Legacy|SV-105145, STIG-Legacy|V-96007, Vuln-ID|V-215662

Plugin: Cisco

Control ID: dddf801cb95ff759747f52c732a59a86c817c58289bb130c750381f4710106a8