Title

The Cisco ACI must limit the number of concurrent sessions to one for each administrator account. (Cat II impact)

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) 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 Content

Verify the ACI is set to limit the number of concurrent management sessions to "1" as shown in the example below: 1. Navigate to the configuration through the APIC GUI by navigating to Admin >> AAA >> Security. 2. Verify the limit for the number of concurrent sessions per user is set to "1". If the ACI is not configured to limit the number of concurrent management sessions to "1" for all management session types (i.e., vty, con, and SSH), this is a finding.

Fix Text

Configure the switch to limit the number of concurrent management sessions to an organization-defined number as shown in the example below: 1. Navigate to the configuration through the APIC GUI by navigating to Admin >> AAA >> Security. 2. Set the limit for the number of concurrent sessions per user to "1".

Additional Identifiers

Rule ID: SV-271975r1067450_rule

Vulnerability ID: V-271975

Group Title: SRG-APP-000001-NDM-000200

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.