Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Cisco ACI NDM Security Technical Implementation Guide

V1R1 · · · Released 27 May 2025 · 26 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Supporting documents DISA companion ZIP · 2.1 MB 4 PDFs

Bundled by DISA alongside this STIG release: overview, revision history, and readme files. Download the full archive or open an individual PDF.

Download full ZIP U_Cisco_ACI_Y25M05_STIG.zip
Digest of Updates vs. V1R0.1 · 07 Feb 2025 −2 ✎ 12

Comparison against the immediately-prior release (V1R0.1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Removed rules 2

  • V-271930 Medium The Cisco ACI must off-load audit records to a central syslog server that are separate from the appliance.
  • V-271938 Medium The Cisco ACI must prevent the installation of patches, service packs, or application components without verification the software component has been digitally signed using a certificate that is recognized and approved by the organization.

Content changes 12

  • V-271916 Medium checkfix The Cisco ACI must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).
  • V-271917 Medium checkfix The Cisco ACI must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
  • V-271918 Medium checkfix The Cisco ACI must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the device.
  • V-271919 Medium description The Cisco ACI must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
  • V-271924 High descriptioncheckfix The Cisco Application Policy Infrastructure Controller (APIC) must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access.
  • V-271926 High check The Cisco ACI must be running an operating system release that is currently supported by the vendor.
  • V-271927 High descriptioncheckfix The Cisco ACI must be configured to assign appropriate user roles or access levels to authenticated users.
  • V-271931 High descriptioncheckfix The Cisco ACI must be configured to send log data to a central log server for log retention and forwarding alerts to the administrators and the information system security officer (ISSO).
  • V-271932 Medium fix The Cisco ACI must be configured to alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.
  • V-271966 High description The Cisco ACI must use FIPS 140-2/140-3 approved algorithms for authentication to a cryptographic module.
  • V-271969 High descriptioncheck Cisco ACI SSH sessions must be terminated after five minutes of inactivity.
  • V-271975 Medium checkfix The Cisco ACI must limit the number of concurrent sessions to one for each administrator account.
Sort by
b
The Cisco ACI must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC).
AU-8 - Medium - CCI-001890 - V-271916 - SV-271916r1114201_rule
RMF Control
AU-8
Severity
M
CCI
CCI-001890
Version
CACI-ND-000001
Vuln IDs
  • V-271916
Rule IDs
  • SV-271916r1114201_rule
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in UTC or local time with an offset from UTC.
Checks: C-75966r1114199_chk

1. Navigate to System>> System Setting. 2. In the Navigation pane, click "Date and Time". 3. Verify UTC is selected. If the Cisco ACI is not configured to use the UTC time zone, this is a finding.

Fix: F-75873r1114200_fix

Configure NTP servers to provide UTC time. 1. Navigate to System >> System Setting. 2. In the Navigation pane, click "Date and Time". 3. In the Work pane, choose "Display Format, then click "UTC". 4. Click "Update".

b
The Cisco ACI must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
IA-3 - Medium - CCI-001967 - V-271917 - SV-271917r1114333_rule
RMF Control
IA-3
Severity
M
CCI
CCI-001967
Version
CACI-ND-000002
Vuln IDs
  • V-271917
Rule IDs
  • SV-271917r1114333_rule
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
Checks: C-75967r1114202_chk

To show the current FIPS mode setting, use the show command from the CLI configuration mode. apic1(config) show fips status If FIPS mode is not set to "Enable", this is a finding.

Fix: F-75874r1114332_fix

From the CLI configuration mode, enable FIPS mode on all nodes and then reboot all nodes to activate FIPS compliance. apic1(config)# fips mode enable

b
The Cisco ACI must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the device.
AC-8 - Medium - CCI-000048 - V-271918 - SV-271918r1114335_rule
RMF Control
AC-8
Severity
M
CCI
CCI-000048
Version
CACI-ND-000003
Vuln IDs
  • V-271918
Rule IDs
  • SV-271918r1114335_rule
Display of the DOD-approved use notification before granting access to the Cisco ACI ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users.
Checks: C-75968r1114205_chk

1. On the APIC menu bar, choose System >> System Settings. 2. In the Navigation pane, click "System Alias and Banners". 3. In the "Work" pane, click the verify the Controller CLI Banner, Switch CLI Banner, and GUI Banner (URL) are configured to display the text below. "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details." If the banner is not presented, this is a finding.

Fix: F-75875r1114334_fix

The CLI banner is a simple text string to be printed at the terminal before the password prompt. A banner can be defined for the APIC CLI and a separate banner for the switch CLI. The GUI banner displays at the APIC URL before user login authentication. The GUI banner is defined as a URL of a site hosting the desired HTML. 1. In the GUI menu bar, navigate to System >> System Settings >> APIC Identification Preferences. 2. In the Navigation pane, select "System Alias and Banners". 3. In the "Work" pane, copy and paste the banner below in the exact format for each banner type, then click "Submit". 4. To configure an APIC GUI banner, type the URL of a site hosting the desired HTML into the GUI Banner (URL) textbox. The URL site owner must allow the site to be placed in an iFrame to display the informational banner. If the owner of the site sets the x-frame-optiontodenyorsameorigin, the site the URL points to will not appear. Refer to the vendor guide for more details. 5. Click "Submit". The banner must read exactly as follows: "You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details."

b
The Cisco ACI must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
AC-7 - Medium - CCI-000044 - V-271919 - SV-271919r1114340_rule
RMF Control
AC-7
Severity
M
CCI
CCI-000044
Version
CACI-ND-000004
Vuln IDs
  • V-271919
Rule IDs
  • SV-271919r1114340_rule
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. For Cisco ACI, when a user is in a locked-out state, the lockout is enforced in all nodes that are part of the fabric, including controllers and switches.
Checks: C-75969r1063904_chk

1. On the GUI menu bar, choose Admin >> AAA. 2. In the Navigation pane, choose "Security". 3. In the Work pane, choose the Management Settings >> Policy tab. 4. Under Properties, verify the fields as follows: - For Lockout User after multiple failed login attempts, choose "Enable". - For Number of failed attempts before user is locked out, enter "3". - For Time period in which consecutive attempts were failed (m), enter "15" or an organization-defined value. - For Duration of lockout (m), enter "15". If the Cisco ACI fabric is not configured to enforce the limit of three consecutive invalid logon attempts and lock out users for 15 minutes, this is a finding.

Fix: F-75876r1063905_fix

1. On the GUI menu bar, choose Admin >> AAA. 2. In the Navigation pane, choose "Security". 3. In the Work pane, choose Management Settings >> Policy tab. 4. Under Properties, fill out the fields as follows: - For Lockout User after multiple failed login attempts, choose "Enable". - For Number of failed attempts before user is locked out, enter "3". - For Time period in which consecutive attempts were failed (m), enter "15" (or an organization-defined value). - For Duration of lockout (m), enter "15". 5. Click "Submit".

c
The Cisco ACI must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services.
CM-7 - High - CCI-000382 - V-271920 - SV-271920r1114158_rule
RMF Control
CM-7
Severity
H
CCI
CCI-000382
Version
CACI-ND-000005
Vuln IDs
  • V-271920
Rule IDs
  • SV-271920r1114158_rule
To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable unused or unnecessary physical and logical ports/protocols on information systems. By default, Cisco ACI only exposes two ports from the outside: - HTTPS (TCP 443) for GUI access and REST API access, on both the APIC and switches. - SSH (TCP 22) for CLI access, on both the APIC and switches. Cisco ACI enables Link Layer Discovery Protocol (LLDP) by default to support zero-touch fabric provisioning. DOD sites may keep LLDP enabled on trusted interfaces for loop prevention and VMM integration. Sites must disable LLDP on interfaces facing untrusted networks. Cisco ACI is designed not to run nonrequired services by default, as well as to limit remote management services or protocols that are active by default. Hence, there is no action required from an administrator standpoint to disable them. If any other protocol is required, such as SNMP, administrators must explicitly configure it.
Checks: C-75970r1063155_chk

From APIC GUI: 1. Navigate to Fabric >> Fabric Policies >> Pod >> Management Access. 2. Fabric >> Fabric Policies >> Pod Policies >> Management Access. Verify insecure or unnecessary ports/protocols, services, and ciphers are disabled. This is the default. If the Cisco ACI is configured to listen or run unnecessary and/or nonsecure functions, ports, protocols, and/or services, this is a finding.

Fix: F-75877r1114157_fix

From APIC GUI: 1. Navigate to Fabric >> Fabric Policies >> Pod >> Management Access. 2. Fabric >> Fabric Policies >> Pod Policies >> Management Access. Disable insecure or unnecessary ports/protocols, services, and ciphers that have been enabled, such as HTTP, FTP, unauthorized TLS versions, and TELNET.

b
The Cisco ACI must conduct backups of the configuration weekly or at an organization-defined frequency and store on a separate device.
CP-9 - Medium - CCI-000539 - V-271921 - SV-271921r1113817_rule
RMF Control
CP-9
Severity
M
CCI
CCI-000539
Version
CACI-ND-000006
Vuln IDs
  • V-271921
Rule IDs
  • SV-271921r1113817_rule
Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system configuration and security settings. If this information were not backed up, and a system failure were to occur, the security settings would be difficult to reconfigure quickly and accurately. Maintaining a backup of information system and security-related documentation provides for a quicker recovery time when system outages occur. This control requires the Cisco ACI to support the organizational central backup process for user account information associated with the Cisco ACI. This function may be provided by the Cisco ACI itself; however, the preferred best practice is a centralized backup rather than each Cisco ACI performing discrete backups. With ACI, all components of the ACI Fabric are treated as one entity (leaves, spines, APIC controllers). The ACI Fabric configuration, while made up of different managed objects, is combined into one tar/gz zipfile, which greatly improves the configuration backup process, as well as the configuration restoration process. Finally, the backups can be configured as one-time backup jobs, or they can be scheduled in a daily or weekly scheduler to export the entire Fabric configuration to a remote location (i.e., external server) using SCP, FTP, or SFTP. Cisco ACI allows administrators to perform on-demand and periodic snapshots. Those snapshots can be saved either locally or in a remote location. Cisco ACI configuration contains many sensitive details, including passwords and secrets. Therefore, backup configuration must be properly secured and stored in a secure remote location, ensuring that sensitive information on the configuration files is not disclosed. Set the AES passphrase immediately after fabric bring-up and store the passphrase in a safe location external to the APIC. This passphrase must be provided by the administrator to unencrypt the configuration backup needed to restore the fabric should a disaster happen.
Checks: C-75971r1063952_chk

From the APIC GUI, verify backups are being performed as required: 1. Navigate to Admin >> Import/Export >> Export Policies >> Configuration >> Create Configuration Export Policy. 2. Fill out the rest of the form and click "Submit". If the Cisco ACI is not configured to conduct backups of the configuration weekly or at an organization-defined frequency and stored on a separate device, this is a finding.

Fix: F-75878r1063953_fix

From the APIC GUI, create a remote location where the configuration will be stored: 1. Navigate to Admin >> Import/Export >> Remote Locations >> Create Remote Location. 2. Enable the global AES encryption setting and save the password in a secure location. 3. Fill out the rest of the form and click "Submit". Create a Scheduler policy for weekly backups: 1. Navigate to Admin >> Schedulers >> Fabric >> Create Scheduler >> Create Trigger Scheduler. 2. Fill out the rest of the form and click "Submit". Create a Configuration Export Policy: 1. Navigate to Admin >> Import/Export >> Export Policies >> Configuration >> Create Configuration Export Policy. 2. Fill out the rest of the form and click "Submit".

b
The Cisco ACI must obtain its public key certificates from an appropriate certificate policy through an approved service provider.
SC-17 - Medium - CCI-001159 - V-271922 - SV-271922r1114181_rule
RMF Control
SC-17
Severity
M
CCI
CCI-001159
Version
CACI-ND-000007
Vuln IDs
  • V-271922
Rule IDs
  • SV-271922r1114181_rule
After the Cisco ACI is initialized, it uses the self-signed certificate as the SSL certificate for HTTPS. This self-signed certificate is neither appropriate nor approved for use in DOD.
Checks: C-75972r1063955_chk

From the GUI menu bar: 1. Navigate to Admin >> AAA >> Security >> Public Key Management >> Certificate Authorities. 2. Verify the Issuer is an approved CA. If the Cisco ACI does not obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.

Fix: F-75879r1063162_fix

From the GUI menu bar: 1. Navigate to Admin >> AAA >> Security >> Public Key Management >> Certificate Authorities. 2. Fill in the form, including the trusted CA root certificate and CA intermediate certificate. Click "Submit". 3. Navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. Fill out the form and click "Submit". 4. Navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. Fill out the form and click "Submit". 5. Get the CSR and send it to the CA Organization. 6. On the menu bar, navigate to Admin >> AAA >> Security >> Public Key Management >> Key Rings. 7. Double-click the create Key Ring name and find the Request option. The content in the Request is the CSR. Click "Submit". 8. Update the Signing Certificate on the Web. On the menu bar, navigate to Fabric >> Fabric Policies >> Policies >> Pod >> Management Access >> Default. 9. In the Admin KeyRing drop-down list, choose the desired KeyRing. Click "Submit". After clicking submit, an error occurs due to certificate reasons. Refresh with the new certificate.

b
The Cisco ACI must use DOD-approved Network Time Protocol (NTP) sources that use authentication that is cryptographically based.
IA-3 - Medium - CCI-001967 - V-271923 - SV-271923r1114182_rule
RMF Control
IA-3
Severity
M
CCI
CCI-001967
Version
CACI-ND-000008
Vuln IDs
  • V-271923
Rule IDs
  • SV-271923r1114182_rule
If NTP is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to Cisco ACIs, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source. Time synchronization plays a critical role in the ACI fabric. From validating certificates, to keeping log files across devices consistent, it is strongly encouraged to sync the ACI fabric to redundant time sources. Simply creating an NTP policy does not apply it to the fabric. This policy will need to be updated to a "Pod Policy". Do not enable the NTP server option that allows the leaf switches to serve time requests to downstream endpoints. Using a Bridge Domain SVI (Subnet IP) as an NTP Source for downstream clients is not recommended. When a leaf switch is enabled as NTP server, it will respond on any interface. Issues can arise when attempting to use the SVI address of a leaf, rather than the management IP.
Checks: C-75973r1063957_chk

Review the NTP configuration to verify it is compliant: 1. Navigate to Fabric >> Fabric Policies >> Fabric Security. 2. Expand "Policies". 3. Expand "Pod". 4. Expand "Date and Time". 5. Expand each "Date and Time Policy". 6. Verify at least two DOD-approved time sources are configured. Note: DOD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DOD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source. If Cisco ACI fabric does not use DOD-approved NTP sources that use authentication that is cryptographically based, this is a finding.

Fix: F-75880r1114182_fix

Configure NTP servers. Create an NTP policy: 1. Navigate to Fabric >> Quickstart, and then click "Create an NTP Policy Link". 2. Fill out the form. - Provide a name for the policy. - Set the State to "Enabled". 3. Click "Next" to define the NTP Sources. 4. Define at least two DOD-approved time servers. Leave all the default options and click "OK". Refer to the note below. 5. Navigate to Fabric >> Fabric Policies sub menu >> Pods >> Policy Groups folder to add the NTP Policy to the appropriate Fabric Pod Policy or group to assign to one or more Pods in the fabric. 6. Right-click on the Policy Groups folder. Select an existing Pod Policy Group or create a new group. 7. Select the policy for NTP created in the previous step. 8. Navigate to Fabric >> Fabric Policies sub menu >> Pods >> Profiles >> Pod Profile >> default. If needed, with the default Pod Selector selected in the navigation pane, change the Fabric Policy Group to the one created in the previous step. Note: DOD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DOD network (NIPRNet/SIPRNet); USNO time servers; and/or the GPS. The secondary time source must be located in a different geographic region than the primary time source.

c
The Cisco Application Policy Infrastructure Controller (APIC) must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access.
CM-6 - High - CCI-000370 - V-271924 - SV-271924r1114210_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000370
Version
CACI-ND-000009
Vuln IDs
  • V-271924
Rule IDs
  • SV-271924r1114210_rule
Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important protection against the insider threat. With robust centralized management, audit records for administrator account access to the organization's Cisco ACIs can be more readily analyzed for trends and anomalies. The alternative method of defining administrator accounts on each device exposes the device configuration to remote access authentication attacks and system administrators with multiple authenticators for each Cisco ACI. APIC policies manage the authentication, authorization, and accounting (AAA) functions of the Cisco ACI fabric. The combination of user privileges, roles, and domains with access rights inheritance enables administrators to configure AAA functions at the managed object level in a granular fashion. Creating a user and assigning a role to that user does not enable access rights. It is necessary to also assign the user to one or more security domains. By default, the ACI fabric includes two special precreated domains: - "All" allows access to the entire MIT. - "Infra" allows access to fabric infrastructure objects/subtrees, such as fabric access policies. Satisfies: SRG-APP-000149-NDM-000247, SRG-APP-000001-NDM-000200
Checks: C-75974r1114208_chk

Review the AAA configuration: 1. In the GUI, on the menu bar, choose Admin >> AAA. 2. In the Navigation pane, click "Authentication" and then click the "RADIUS" tab. 3. Review the configuration for the AAA server. 4. Review the configuration of the Login Domain(s) used by the site. Note: The above configuration is an example using the RADIUS protocol. However, DOD sites may configure the options for LDAP, RADIUS, or TACACS+. Roles and user attributes such as limiting concurrent logins to 1 for remote system admins are also needed, but this configuration is done on the remote AAA server. If the Cisco ACI is not configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access, this is a finding.

Fix: F-75881r1114209_fix

In the APIC, configure redundant RADIUS providers. 1. On the menu bar, choose Admin >> AAA. 2. In the Navigation pane, click "Authentication", and then click the "RADIUS" tab. 3. In the Work pane, choose Actions >> Create RADIUS Provider. 4. Specify the RADIUS host name (or IP address), port, protocol, and management endpoint group. 5. In the Navigation pane, choose System >> System Settings >> APIC Connectivity Preferences. 6. In the Work pane, select "ooband". 7. Repeat the above steps for at least one other AAA server. 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 LDAP, RADIUS, or TACACS+.

c
The Cisco ACI must be running an operating system release that is currently supported by the vendor.
CM-6 - High - CCI-000366 - V-271926 - SV-271926r1114339_rule
RMF Control
CM-6
Severity
H
CCI
CCI-000366
Version
CACI-ND-000011
Vuln IDs
  • V-271926
Rule IDs
  • SV-271926r1114339_rule
Cisco ACIs running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities.
Checks: C-75976r1114338_chk

To view the current firmware versions installed on the controllers and switches, type the following command from configuration mode: apic1# configure apic1(config)# firmware apic1(config-firmware)# show version Alternatively, in the GUI navigate to Admin >> Firmware. Refer to the Cisco APIC Upgrade/Downgrade Support Matrix for Cisco APIC upgrade and downgrade paths. If the Cisco ACI fabric, leaf switches, or APIC components have an operating system release that is not currently supported by the vendor, this is a finding.

Fix: F-75883r1114212_fix

Refer to the Cisco APIC Upgrade/Downgrade Support Matrix for Cisco APIC upgrade and downgrade paths. Install a Cisco APIC Software Maintenance Upgrade Patch Using the GUI. Use the following procedure to install a software maintenance upgrade (SMU) patch on a Cisco APIC: 1. Add the firmware image that corresponds to the SMU patch to the Cisco APIC. The patch will be listed along with any other firmware images (SMU patches and otherwise). 2. Set up a controller firmware update. On the Version Selection screen, for the Update Type, choose "Software Maintenance Upgrade (Install)", then choose the SMU patch in the Select Firmware section. Installing a Switch Software Maintenance Upgrade Patch Using the GUI: SMU patch installation or uninstallation uses the same update group as a regular firmware upgrade. Because one node can belong to only one update group, when an SMU patch is applied to a specific node, remove that node from the existing group and create a new group that is dedicated to the node so that other nodes are not impacted. When performing a regular firmware upgrade for the entire fabric, delete the dedicated update group used for the SMU patch installation and add the node back to one of the original groups. If all the nodes in the existing group need the SMU patch, reuse the same update group without creating a new update group. 1. Add the firmware image that corresponds to the SMU patch to the Cisco APIC. The Cisco APIC lists the patch along with any other firmware images (SMU patches and otherwise). 2. Set up a node firmware update. On the Version Selection screen, for the Update Type, choose "Software Maintenance Upgrade (Install)", then choose the SMU patch in the Select Firmware section. Click "Begin Download" in the Confirmation screen to download the patch to the selected switches. The Firmware Updates tab in the Work pane displays. 3. In the Work pane, click the upgrade group created. The Node Firmware Update dialog displays with information for the upgrade group. 4. When the status for the switches is "Ready to Install", click "Actions". Install and Reload: The switches reboot after the SMU patch gets installed. Choose this action to install only one SMU patch, or if installing the final patch of multiple patches. Install and Skip Reload: The switches do not reboot after the SMU patch gets installed. Choose this action to install multiple SMU patches and if this patch is not the final patch. In this case, repeat this entire procedure for each additional patch and continue to choose Install and Skip Reload until the final patch is installed. For the final patch, choose Install and Reload. Optionally, choose "Install and Skip Reload" and manually reboot the switch after the patch gets installed.

c
The Cisco ACI must be configured to assign appropriate user roles or access levels to authenticated users.
AC-3 - High - CCI-000213 - V-271927 - SV-271927r1114337_rule
RMF Control
AC-3
Severity
H
CCI
CCI-000213
Version
CACI-ND-000012
Vuln IDs
  • V-271927
Rule IDs
  • SV-271927r1114337_rule
Successful identification and authentication must not automatically give an entity full access to a Cisco ACI or security domain. The lack of authorization-based access control could result in the immediate compromise of, and unauthorized access to, sensitive information. All DOD systems must be properly configured to incorporate access control methods that do not rely solely on authentication for authorized access. Security domains allow fabric administrators to expose resources selectively to a set of users and provide those users with the required level of permissions to read and modify those resources. By using security domains, multiple sets of users can share the underlying infrastructure while having separated management access to their resources. Although out of scope for this STIG, the authentication server will also need to be configured with the security groups or access levels available on the Cisco ACIs and convey that information to the AAA operator of the Cisco ACI. Once the AAA broker identifies the user persona on the centralized directory service, the user's security group memberships can be retrieved. The AAA operator will then create a mapping that links target security groups from the directory service to the appropriate security groups or access levels on the Cisco ACI. Once these mappings are configured, authorizations can happen dynamically, based on each user's directory service group membership. Satisfies: SRG-APP-000033-NDM-000212, SRG-APP-000329-NDM-000287, SRG-APP-000177-NDM-000263, SRG-APP-000910-NDM-000300
Checks: C-75977r1114336_chk

Verify users are assigned roles based on the SSP. This requirement does not apply to the account of last resort. From the GUI, navigate to Admin >> AAA >> Security Management >> Roles or have the site demonstrate the method used for role and privilege separation. Verify that the roles are associated with the users in compliance with the SSP required roles and privileges. Read and write access rights must match the level of granularity required by the SSP. If any user/group or service account are assigned to roles with privileges that are beyond those required and authorized by the organization, this is a finding.

Fix: F-75884r1114215_fix

View the SSP to determine the required organization-defined roles and the least privilege policies required for each role. For example, audit administrator, crypto administrator, system administrator, etc. Assign remote users to roles based on SSP and least privileges. Carefully assign capabilities to each role based on SSP role assignments. Remote authentication server is required, but roles can be created, deleted, or associated access privileges to nodes and resources update in the APIC. To create a new role with reduced permissions, do the following: To create or modify roles: 1. From the GUI, navigate to Admin >> AAA >> Security Management >> Roles. 2. Create custom roles with appropriate privileges (e.g., read-write access to specific objects). 3. Associate users with these roles, allowing them to perform specific tasks within the ACI fabric. Note: This procedure may use preconfigured rules and privileges. Security Domains, Rules, and Custom Roles may also be used depending on the desired architecture and complexity of the implementation. Refer to the vendor documentation to create custom rules, privileges combinations, Rules, and Security domains. These roles are assigned to the remote users in the external authentication server.

b
The Cisco ACI must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.
AC-2 - Medium - CCI-001358 - V-271929 - SV-271929r1113827_rule
RMF Control
AC-2
Severity
M
CCI
CCI-001358
Version
CACI-ND-000014
Vuln IDs
  • V-271929
Rule IDs
  • SV-271929r1113827_rule
Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. In the initial configuration script for the Cisco ACI, the admin account is configured and the admin is the only user when the system starts. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.
Checks: C-75979r1063972_chk

Verify only the local site designated account of last resort is present: 1. In the GUI menu bar, navigate to Admin >> AAA. 2. In the navigation pane, click "Users". 3. In the Work pane, click "View the Local Users" tab. If local accounts other than the account of last resort are present, this is a finding.

Fix: F-75886r1063973_fix

Remove accounts that are not the account of last resort: 1. In the GUI menu bar, navigate to Admin >> AAA. 2. In the navigation pane, click "Users". 3. In the Work pane, click "View the Local Users" tab. 4. Select any unauthorized user accounts that are not the account of last resort and deactivate the user account by using the Account Status control.

c
The Cisco ACI must be configured to send log data to a central log server for log retention and forwarding alerts to the administrators and the information system security officer (ISSO).
AU-4 - High - CCI-001851 - V-271931 - SV-271931r1114365_rule
RMF Control
AU-4
Severity
H
CCI
CCI-001851
Version
CACI-ND-000016
Vuln IDs
  • V-271931
Rule IDs
  • SV-271931r1114365_rule
The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can be used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, is important in determining whether someone is an internal employee or an outside threat.
Checks: C-75981r1114359_chk

Verify the ACI Fabric is configured to send event messages to syslog servers. Example configuration: logging server-group SYSLOG_SERVER_GROUP apic1(config)# server 10.0.0.10 port 514 severity informational apic1(config)# server 10.0.0.20 port 514 severity informational . . . apic1(config)# syslog monitoring source MyEventSource apic1(config)# syslog monitoring source MyEventSource destination SYSLOG_SERVER_GROUP If the Cisco ACI is not configured to send audit records to at least one central syslog server, this is a finding.

Fix: F-75888r1114364_fix

Configure the Cisco switch to send log records to a syslog servers. 1: Create a logging server group. logging server-group <group_name> server <server_ip> port <port_number> severity <severity_level> 2: Configure monitoring sources. Define which types of events (audit, event, fault, session) to log to the remote servers. Associate the monitoring source with the server group. syslog monitoring source <source_name> syslog monitoring source <source_name> destination <logging_server_group_name> Example configuration: apic1(config)# logging server-group SYSLOG_SERVER_GROUP apic1(config)# server 10.0.0.10 port 514 severity informational apic1(config)# server 10.0.0.20 port 514 severity informational apic1(config)# syslog monitoring source MyEventSource apic1(config)# syslog monitoring source MyEventSource destination SYSLOG_SERVER_GROUP

b
The Cisco ACI must be configured to alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.
Medium - CCI-003831 - V-271932 - SV-271932r1114348_rule
RMF Control
Severity
M
CCI
CCI-003831
Version
CACI-ND-000017
Vuln IDs
  • V-271932
Rule IDs
  • SV-271932r1114348_rule
Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls.
Checks: C-75982r1063191_chk

Verify the remote syslog or SIEM is sending event notifications to personnel based on audit log entries and associating those notifications with specific user roles or groups within the organization through the Authentication, Authorization, and Accounting (AAA) configuration. If the ACI is not configured to send audit records to the central audit server, this is a finding.

Fix: F-75889r1114347_fix

Configure event notifications based on audit log entries and associate those notifications with specific user roles or groups within the organization through the AAA configuration. Preferred method (required): 1. Configure the APIC to forward audit log events to a centralized Syslog such as a SIEM platform. (SRG-APP-000515-NDM-000325) 2. Configure the SIEM's capabilities to aggregate, analyze, and correlate audit events with other system logs for advanced threat detection and incident response. Note: Although the ACI can perform this function, it leverages the Call Home feature, which must be set to disabled by another STIG requirement.

b
The Cisco ACI must audit the enforcement actions used to restrict access associated with changes to the device.
Medium - CCI-003938 - V-271933 - SV-271933r1114169_rule
RMF Control
Severity
M
CCI
CCI-003938
Version
CACI-ND-000018
Vuln IDs
  • V-271933
Rule IDs
  • SV-271933r1114169_rule
Without auditing the enforcement of access restrictions against changes to the device configuration, it will be difficult to identify attempted attacks, and an audit trail will not be available for forensic investigation for after-the-fact actions. Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact. Satisfies: SRG-APP-000381-NDM-000305, SRG-APP-000080-NDM-000220
Checks: C-75983r1114167_chk

Verify the ACI Fabric is configured to send event messages to redundant syslog servers: 1. Navigate to Admin &gt;&gt; External Data Collectors &gt;&gt; Monitoring Destinations &gt;&gt; Syslog. 2. Verify one or more Syslog Monitoring Destinations have been configured. 3. Verify redundant syslog servers are configured. If the ACI is not configured to send audit records to redundant central syslog servers that are separate from the ACI, this is a finding.

Fix: F-75890r1114168_fix

Configure the ACI Fabric to send messages to redundant external syslog servers. Create Syslog Remote Location: 1. Navigate to Admin >> External Data Collectors >> Monitoring Destinations >> Syslog. 2. From the Actions Menu, select "Create Syslog Monitoring Destination Group". 3. Provide a name for the Syslog Group (e.g., syslog servers). 4. Leave all other options as default and click "Next". 5. Under Create Remote Destinations, click the "+" icon. a. Enter hostname or IP address. b. Set the Severity level to "Information". c. Set the Management EPG as default (Out-of-band). d. Click "OK". 6. If necessary, add additional Remove Destinations. 7. Click "Finish". Create Fabric Level Syslog Source: The fabric Syslog policy will export alerts for monitoring details including physical ports, switch components (fans, memory, PSUs, etc.), and linecards. 1. Navigate to Fabric >> Fabric Policies submenu >> Policies >> Monitoring >> Common Policy >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. From the Actions Menu, select "Create Syslog Source". a. Provide a name for the source (e.g., fabric_common_syslog). b. Set the Severity level to "Information". c. Check all Log types. d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". Creating Access Level Syslog Policy: The Access Syslog policy will export alerts for monitoring details including VLAN Pools, Domains, Interface Policy Groups, and Interface & Switch Selectors Policies. 1. Navigate to Fabric >> Access Policies submenu >> Policies >> Monitoring >> default >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. In the Work pane, set the Source Type to "Syslog". 3. Click the "+" icon to add a Syslog Source. a. Provide a name for the source (e.g., access_default_syslog). b. Set severity level to "Information" unless desired to increase logging details. c. Check any additional Log types such as Audit Logs (optional). d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". Creating Tenant Level Syslog Policies: Tenant-level logging includes all tenant-related policies, including Application Profiles, EPGs, Bridge domains, VRFs, external networking, etc. To simplify the syslog configuration across multiple tenants, leverage Common Tenant syslog configuration and share that across other tenants. This would provide a consistent level of logging for all tenants. Alternately, the site may create the respective Syslog policy within each tenant. The following configures a single consistent syslog policy using the Common Tenant: 1. Navigate to Tenants >> common >> Policies >> Mentoring >> default >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. In the Work pane, set the Source Type to "Syslog". 3. Click the "+" icon to add a Syslog Source. a. Provide a name for the source (e.g., tenant_default_syslog). b. Set the severity level as "Information". c. Check all log types. d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". 4. Navigate to Tenants >> Your_Tenant >> Policy tab. 5. Set the Monitoring Policy drop-down box to be the default policy from the common tenant.

b
The Cisco ACI must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
AU-4 - Medium - CCI-001849 - V-271935 - SV-271935r1114172_rule
RMF Control
AU-4
Severity
M
CCI
CCI-001849
Version
CACI-ND-000020
Vuln IDs
  • V-271935
Rule IDs
  • SV-271935r1114172_rule
To ensure Cisco ACIs have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. The value for the organization-defined audit record storage requirement will depend on the amount of storage available on the Cisco ACI, the anticipated volume of logs, the frequency of transfer from the Cisco ACI to centralized log servers, and other factors.
Checks: C-75985r1114170_chk

Verify the ACI Fabric is configured to send event messages to redundant syslog servers: 1. Navigate to Admin &gt;&gt; External Data Collectors &gt;&gt; Monitoring Destinations &gt;&gt; Syslog. 2. Verify one or more Syslog Monitoring Destinations have been configured. 3. Verify redundant syslog servers are configured. If the ACI is not configured to send audit records to redundant central syslog server that are separate from the ACI, this is a finding.

Fix: F-75892r1114171_fix

Configuring the ACI Fabric to send messages to redundant external syslog servers. Create Syslog Remote Location: 1. Navigate to Admin >> External Data Collectors >> Monitoring Destinations >> Syslog. 2. From the Actions Menu, select "Create Syslog Monitoring Destination Group". 3. Provide a name for the Syslog Group (e.g., syslog servers). 4. Leave all other options default and click "Next". 5. Under Create Remote Destinations, click the "+" icon. a. Enter hostname or IP address. b. Set the Severity level to "Information". c. Set the Management EPG as default (Out-of-band). d. Click "OK". 6. If necessary, add additional Remove Destinations. 7. Click "Finish". Create Fabric Level Syslog Source: The fabric Syslog policy will export alerts for monitoring details including physical ports, switch components (fans, memory, PSUs, etc.) and linecards. 1. Navigate to Fabric >> Fabric Policies submenu >> Policies >> Monitoring >> Common Policy >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. From the Actions Menu, select "Create Syslog Source". a. Provide a name for the source (e.g., fabric_common_syslog). b. Set the Severity level to "Information". c. Check all Log types. d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". Creating Access Level Syslog Policy: The Access Syslog policy will export alerts for monitoring details including VLAN Pools, Domains, Interface Policy Groups, and Interface & Switch Selectors Policies. 1. Navigate to Fabric >> Access Policies submenu >> Policies >> Monitoring >> default >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. In the Work pane, set the Source Type to "Syslog". 3. Click the "+" icon to add a Syslog Source. a. Provide a name for the source (e.g., access_default_syslog). b. Set severity level to "Information" unless desired to increase logging details. c. Check any additional Log types such as Audit Logs (optional). d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". Creating Tenant Level Syslog Policies: Tenant-level logging includes all tenant-related policies, including Application Profiles, EPGs, Bridge domains, VRFs, external networking, etc. To simplify the syslog configuration across multiple tenants, leverage Common Tenant syslog configuration and share that across other tenants. This would provide a consistent level of logging for all tenants. Alternately, the site may create the respective Syslog policy within each tenant. The following configures a single consistent syslog policy using the Common Tenant. 1. Navigate to Tenants >> common >> Policies >> Mentoring >> default >> Callhome/Smart Callhome/SNMP/Syslog/TACACs. 2. In the Work pane, set the Source Type to "Syslog". 3. Click the "+" icon to add a Syslog Source. a. Provide a name for the source (e.g., tenant_default_syslog). b. Set the severity level as "Information". c. Check all log types. d. Set the Dest Group to the Syslog Destination Group previously created. e. Click "Submit". 4. Navigate to Tenants >> Your_Tenant >> Policy tab. 5. Set the Monitoring Policy drop-down box to be the default policy from the common tenant.

b
The Cisco ACI must implement replay-resistant authentication mechanisms for network access to privileged accounts.
IA-2 - Medium - CCI-001941 - V-271936 - SV-271936r1113837_rule
RMF Control
IA-2
Severity
M
CCI
CCI-001941
Version
CACI-ND-000021
Vuln IDs
  • V-271936
Rule IDs
  • SV-271936r1113837_rule
A replay attack may enable an unauthorized user to gain access to the application. authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message. Techniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security). Additional techniques include time-synchronous or challenge-response one-time authenticators.
Checks: C-75986r1063988_chk

Verify the default fabric TLS Protocol: 1. On the menu bar, choose Fabric &gt;&gt; Fabric Policies. 2. In the Navigation pane, select Policies &gt;&gt; Pod &gt;&gt; Management Access &gt;&gt; default. 3. In the Work pane, find the HTTPS section. 4. For SSL Protocols, verify the box for TLS 1.2 or higher is checked. Verify other SSL or TLS versions are not checked. If the Cisco ACI fabric does not implement TLS 1.2 or higher for authentication for network access to privileged accounts, this is a finding.

Fix: F-75893r1063989_fix

Configure the default fabric TLS Protocol: 1. On the menu bar, choose Fabric >> Fabric Policies. 2. In the Navigation pane, choose Policies >> Pod >> Management Access >> default. 3. In the Work pane, find the HTTPS section. 4. For SSL Protocols, check the boxes for TLS 1.2 or higher. Uncheck or leave unchecked for any other SSL or TLS version.

b
The Cisco ACI must automatically audit account creation.
AC-2 - Medium - CCI-000018 - V-271939 - SV-271939r1114173_rule
RMF Control
AC-2
Severity
M
CCI
CCI-000018
Version
CACI-ND-000024
Vuln IDs
  • V-271939
Rule IDs
  • SV-271939r1114173_rule
Upon gaining access to a Cisco ACI, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. Notification of account creation helps to mitigate this risk. Auditing account creation provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes. System messages are created by various sources, such as the Application Policy Infrastructure Controller (APIC) or the spine and leaf switches in the ACI fabric. System messages from the switches can be generated by either of the following processes: the underlying NX-OS operating system of the spine and leaf switches or the ACI-related processes in the switch. This requirement sets the default logging level on the ACI to 7. This information severity level captures normal but significant condition messages and is the level required. Satisfies: SRG-APP-000026-NDM-000208, SRG-APP-000027-NDM-000209, SRG-APP-000028-NDM-000210, SRG-APP-000029-NDM-000211, SRG-APP-000343-NDM-00028, SRG-APP-000091-NDM-000223, SRG-APP-000091-NDM-000223, SRG-APP-000495-NDM-000318, SRG-APP-000499-NDM-000319, SRG-APP-000503-NDM-000320, SRG-APP-000503-NDM-000320, SRG-APP-000504-NDM-000321, SRG-APP-000101-NDM-000231, SRG-APP-000095-NDM-000225, SRG-APP-000096-NDM-000226, SRG-APP-000097-NDM-000227, SRG-APP-000098-NDM-000228, SRG-APP-000099-NDM-000229, SRG-APP-000100-NDM-000230
Checks: C-75989r1063993_chk

View the AAA event types in the local log: 1. In the menu bar, click "Admin". 2. In the submenu bar, click "AAA". 3. In the Navigation pane, choose "AAA Authentication". 4. In the Work pane, click the "History" tab. 5. Under the History tab, click the "Events" subtab to view the event log. 6. Under the History tab, click the "Audit Log" subtab to view the audit log. 7. Double-click a log entry to view additional details about the event. If account change actions are not being logged, this is a finding.

Fix: F-75896r1063994_fix

To change the logging level to 6: 1. Select a service from the "Services" field in the "Changing Logging Level" window. 2. Choose the new logging level for the service from the "Logging Level" field. 3. Click "Apply".

b
The Cisco ACI must generate log records for a locally developed list of auditable events.
AU-12 - Medium - CCI-000169 - V-271944 - SV-271944r1113846_rule
RMF Control
AU-12
Severity
M
CCI
CCI-000169
Version
CACI-ND-000029
Vuln IDs
  • V-271944
Rule IDs
  • SV-271944r1113846_rule
Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured Cisco ACI. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis.
Checks: C-75994r1064004_chk

Configure locally required events for auditing in compliance with the SSP: 1. Navigate to the Contracts section within the tenant. 2. Within the filter directives, select "Log" to enable logging for permit or deny actions on that filter. If locally required events that require auditing are not set to log, this is a finding.

Fix: F-75901r1064005_fix

Configure locally required events for auditing in compliance with the SSP: 1. Navigate to the "Contracts" section within the tenant. 2. Within the filter directives, verify the "Log" is enabled for permit or deny actions on that filter.

b
The Cisco ACI must be configured to allow user selection of long passwords and passphrases, including spaces and all printable characters, for password-based authentication.
Medium - CCI-004064 - V-271958 - SV-271958r1114307_rule
RMF Control
Severity
M
CCI
CCI-004064
Version
CACI-ND-000043
Vuln IDs
  • V-271958
Rule IDs
  • SV-271958r1114307_rule
Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords or passphrases are preferable over shorter passwords. Enforced composition rules provide marginal security benefits while decreasing usability. However, organizations may choose to establish certain rules for password generation (e.g., minimum character length for long passwords) under certain circumstances and can enforce this requirement in IA-5(1)(h). Account recovery can occur, for example, in situations when a password is forgotten. Cryptographically protected passwords include salted one-way cryptographic hashes of passwords. The list of commonly used, compromised, or expected passwords includes passwords obtained from previous breach corpuses, dictionary words, and repetitive or sequential characters. The list includes context-specific words, such as the name of the service, username, and derivatives thereof. Satisfies: SRG-APP-000860-NDM-000250, SRG-APP-000865-NDM-000260, SRG-APP-000167-NDM-000255, SRG-APP-000168-NDM-000256, SRG-APP-000169-NDM-000257
Checks: C-76008r1063269_chk

1. Navigate to Admin &gt;&gt; AAA &gt;&gt; Security. 2. Click the "Management Settings" tab. 3. In the Properties Section, ensure "Password Strength Check" is checked. If the Cisco ACI fabric is not configured to allow user selection of long passwords and passphrases, including spaces and all printable characters for password-based authentication, this is a finding.

Fix: F-75915r1063270_fix

1. Navigate to Admin >> AAA >> Security. 2. Click the "Management Settings" tab. 3. In the Properties Section, ensure "Password Strength Check" is checked.

b
The Cisco ACI must enforce a minimum 15-character password length.
Medium - CCI-004066 - V-271960 - SV-271960r1113863_rule
RMF Control
Severity
M
CCI
CCI-004066
Version
CACI-ND-000045
Vuln IDs
  • V-271960
Rule IDs
  • SV-271960r1113863_rule
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password. The shorter the password, the lower the number of possible combinations that must be tested before the password is compromised. Use of more characters in a password helps to increase exponentially the time and/or resources required to compromise the password.
Checks: C-76010r1063275_chk

1. Navigate to Admin &gt;&gt; AAA &gt;&gt; Security. 2. Click the "Management Settings" tab. 3. In the Properties section, ensure "Password Strength Check" is checked. If the Cisco ACI fabric is not configured to enforce a minimum 15-character password length, this is a finding.

Fix: F-75917r1063276_fix

1. Navigate to Admin >> AAA >> Security. 2. Click the "Management Settings" tab. 3. In the Properties section, ensure "Password Strength Check'" is checked. 4. In the dialog box that opens, ensure "Password Minimum Length" is set to "15".

c
The Cisco ACI must use FIPS 140-2/140-3 approved algorithms for authentication to a cryptographic module.
IA-7 - High - CCI-000803 - V-271966 - SV-271966r1114341_rule
RMF Control
IA-7
Severity
H
CCI
CCI-000803
Version
CACI-ND-000051
Vuln IDs
  • V-271966
Rule IDs
  • SV-271966r1114341_rule
Unapproved mechanisms used for authentication to the cryptographic module are not validated and therefore, cannot be relied on to provide confidentiality or integrity, and DOD data may be compromised. Cisco ACIs using encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2/140-3 is the current standard for validating that mechanisms used to access cryptographic modules use authentication that meets DOD requirements. However, authentication algorithms must configure security processes to use only FIPS-approved and NIST-recommended authentication algorithms. Satisfies: SRG-APP-000179-NDM-000265, SRG-APP-000411-NDM-000330, SRG-APP-000412-NDM-000331
Checks: C-76016r1063293_chk

1. Navigate to System &gt;&gt; System Settings. 2. Click "Fabric Security". 3. Click the "Policy" tab. 4. Verify FIPS Mode is set to "Enable". If FIPS mode is not set to "Enable", this is a finding.

Fix: F-75923r1064044_fix

When FIPS is enabled, it is applied across the Cisco Application Policy Infrastructure Controller (APIC). 1. On the menu bar, select System >> System Settings. 2. In the Navigation pane, select "Fabric Security". 3. In the Work pane, in the Properties area, select the desired FIPS mode. 4. Reboot to complete the configuration.

c
Cisco ACI SSH sessions must be terminated after five minutes of inactivity.
SC-10 - High - CCI-001133 - V-271969 - SV-271969r1114305_rule
RMF Control
SC-10
Severity
H
CCI
CCI-001133
Version
CACI-ND-000054
Vuln IDs
  • V-271969
Rule IDs
  • SV-271969r1114305_rule
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. Quickly terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level or deallocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Checks: C-76019r1114220_chk

Verify the maximum GUI idle duration before requiring login refresh is set to 300 seconds or less: show runing-config crypto webtoken Note: If the output is empty, then the default values are used, this is a finding. If ui-idle-timeout-seconds and webtoken-timeout-seconds are not set to 300 seconds or less, this is a finding.

Fix: F-75926r1064051_fix

Set the GUI idle timeout which affects SSH on both APIC and Switches: 1. Navigate to Admin >> AAA >> Security >> Management Settings. 2. In the Properties section, ensure "Web Token Timeout (s)" is set to 300 or less.

b
The Cisco ACI must be configured to synchronize system clocks within and between systems or system components.
Medium - CCI-004922 - V-271971 - SV-271971r1114177_rule
RMF Control
Severity
M
CCI
CCI-004922
Version
CACI-ND-000056
Vuln IDs
  • V-271971
Rule IDs
  • SV-271971r1114177_rule
Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication processes that involve certificates and time-of-day restrictions as part of access control. Denial of service or failure to deny expired credentials may result without properly synchronized clocks within and between systems and system components. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, such as clocks synchronizing within hundreds of milliseconds or tens of milliseconds. Organizations may define different time granularities for system components. Time service can be critical to other security capabilities such as access control and identification and authentication depending on the nature of the mechanisms used to support the capabilities.
Checks: C-76021r1063308_chk

1. Navigate to Fabric &gt;&gt; Fabric Policies &gt;&gt; Fabric Security. 2. Expand "Policies". 3. Expand "Pod". 4. Expand "Date and Time". 5. Expand each "Date and Time Policy". 6. Verify at least two DOD-approved time sources are configured. Note: DOD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DOD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source. If Cisco ACI fabric does not use DOD-approved redundant NTP sources that use authentication that is cryptographically based, this is a finding.

Fix: F-75928r1114176_fix

Create an NTP policy: 1. Navigate to Fabric >> Quickstart and click "Create an NTP Policy Link". 2. Fill out the form. - Provide a name for the policy. - Set the State to "Enabled". 3. Click "Next" to define the NTP Sources. 4. Define at least two DOD-approved time servers. Leave all the default options and click "OK". Refer to note below. 5. Navigate to Fabric >> Fabric Policies submenu >> Pods >> Policy Groups folder to add the NTP Policy to the appropriate Fabric Pod Policy or group to assign to one or more Pods in the fabric. 6. Right-click on the Policy Groups folder. Select an existing Pod Policy Group or create a new group. 7. Select the policy for NTP created in the previous step. 8. Navigate to Fabric >> Fabric Policies submenu >> Pods >> Profiles >> Pod Profile >> default. If needed, with the default Pod Selector selected in the navigation pane, change the Fabric Policy Group to the one created in the previous step. Note: DOD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), USNO time servers, and/or GPS. The secondary time source must be located in a different geographic region than the primary time source.

b
The Cisco ACI must be configured to disable the auxiliary USB port.
CM-7 - Medium - CCI-000382 - V-271972 - SV-271972r1114185_rule
RMF Control
CM-7
Severity
M
CCI
CCI-000382
Version
CACI-ND-000057
Vuln IDs
  • V-271972
Rule IDs
  • SV-271972r1114185_rule
Disable the USB port in those environments where physical access to the devices is not strictly controlled, or in environments where this extra layer of protection is required. Cisco Nexus 9000 switches running Cisco ACI code have the USB port enabled by default. When the USB port is enabled, switches will try to boot from the USB drive first. This may be a security risk in case a malicious actor has physical access to the switch, given they could power-cycle the device to try to boot the switch from a USB image that contains malicious code. Even if this is not a common scenario considering that most organizations have physical access security guidelines in place, Cisco ACI release 5.2(3) introduced the option to disable the USB port using a specific switch policy.
Checks: C-76022r1064057_chk

Verify the USB port is disabled: 1. Navigate to Fabric &gt;&gt; Access Policies &gt;&gt; Policies &gt;&gt; Switch &gt;&gt; USB Configuration &gt;&gt; default. 2. Verify the "Disable USB Port" box is checked. If the USB port is not disabled, this is a finding.

Fix: F-75929r1114185_fix

Disable the USB port on all switches within the Cisco ACI fabric: 1. Navigate to Fabric >> Access Policies >> Policies >> Switch >> USB Configuration >> default. 2. Check the "Disable USB Port" box; this will disable the USB port on all switches within the Cisco ACI fabric.

b
The Cisco ACI must limit the number of concurrent sessions to one for each administrator account.
AC-10 - Medium - CCI-000054 - V-271975 - SV-271975r1114224_rule
RMF Control
AC-10
Severity
M
CCI
CCI-000054
Version
CACI-ND-000060
Vuln IDs
  • V-271975
Rule IDs
  • SV-271975r1114224_rule
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.
Checks: C-76025r1114222_chk

Review the AAA configuration: 1. In the GUI, on the menu bar, choose Admin &gt;&gt; AAA. 2. In the Navigation pane, click "Authentication" and then click the "RADIUS" tab. 3. Review the configuration for the AAA server. 4. Review the configuration of the Login Domain(s) used by the site. Note: The above configuration is an example using the RADIUS protocol. However, DOD sites may configure the options for LDAP, RADIUS, or TACACS+. Roles and user attributes such as limiting concurrent logins to 1 for remote system admins are also needed, but this configuration is done on the remote AAA server. If the Cisco ACI is not configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access, this is a finding.

Fix: F-75932r1114223_fix

In the APIC, configure redundant RADIUS providers: 1. On the menu bar, choose Admin >> AAA. 2. In the Navigation pane, click "Authentication" and then click the "RADIUS" tab. 3. In the Work pane, choose Actions >> Create RADIUS Provider. 4. Specify the RADIUS host name (or IP address), port, protocol, and management endpoint group. 5. In the Navigation pane, choose System >> System Settings >> APIC Connectivity Preferences. In the Work pane, select "ooband". 6. Repeat the above steps for at least one other AAA server. 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 LDAP, RADIUS, or TACACS+.