The Cisco ACI must limit the number of concurrent sessions to one for each administrator account.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-271975	SRG-APP-000001-NDM-000200	CACI-ND-000060	SV-271975r1168383_rule	2025-12-11	1

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.

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
Review the AAA configuration: 1. In the GUI, on the menu bar, choose Admin >> AAA. 2. In the Navigation pane, click "Authentication". 3. Review the configuration for the configured AAA providers. 4. Review the configuration of the Login Domain(s) used by the site. If the Cisco ACI is not configured to use at a AAA provider for the purpose of authenticating users prior to granting administrative access, this is a finding.

ℹ️ Check

Review the AAA configuration: 1. In the GUI, on the menu bar, choose Admin >> AAA. 2. In the Navigation pane, click "Authentication". 3. Review the configuration for the configured AAA providers. 4. Review the configuration of the Login Domain(s) used by the site. If the Cisco ACI is not configured to use at a AAA provider for the purpose of authenticating users prior to granting administrative access, this is a finding.

✔️ Fix
In the APIC, configure redundant RADIUS providers. 1. On the menu bar, choose Admin >> AAA. 2. In the Navigation pane, choose "Authentication". 3. In the Work pane, choose Providers and click Actions >> Create Provider. 4. In the Create Provider screen, enter the Hostname/IP Address, Description, and choose a RADIUS or TACACS+ as the realm from the drop-down list. Provide the configuration details. Create the login domain for RADIUS: 1. In the Navigation pane, choose AAA Authentication >> Login Domains. 2. In the Work pane, choose Actions >> Create Login Domain. 3. Specify the login domain name, description, realm, and provider group as appropriate. Note: The above configuration is an example using the RADIUS protocol. However, DOD sites may configure the options for RADIUS or TACACS+.

✔️ Fix

In the APIC, configure redundant RADIUS providers. 1. On the menu bar, choose Admin >> AAA. 2. In the Navigation pane, choose "Authentication". 3. In the Work pane, choose Providers and click Actions >> Create Provider. 4. In the Create Provider screen, enter the Hostname/IP Address, Description, and choose a RADIUS or TACACS+ as the realm from the drop-down list. Provide the configuration details. Create the login domain for RADIUS: 1. In the Navigation pane, choose AAA Authentication >> Login Domains. 2. In the Work pane, choose Actions >> Create Login Domain. 3. Specify the login domain name, description, realm, and provider group as appropriate. Note: The above configuration is an example using the RADIUS protocol. However, DOD sites may configure the options for RADIUS or TACACS+.