The Cisco ACI must establish organization-defined alternate communication paths for system operations organizational command and control.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-272103 | CACI-RT-000043 | SV-272103r1168419_rule | CCI-004931 | medium |
| Description | ||||
| An incident, whether adversarial- or nonadversarial-based, can disrupt established communication paths used for system operations and organizational command and control. Alternate communication paths reduce the risk of all communications paths being affected by the same incident. To compound the problem, the inability of organizational officials to obtain timely information about disruptions or to provide timely direction to operational elements after a communication path incident, can impact the ability of the organization to respond to such incidents in a timely manner. Establishing alternate communication paths for command and control purposes, including designating alternative decision makers if primary decision makers are unavailable and establishing the extent and limitations of their actions, can greatly facilitate the organization's ability to continue to operate and take appropriate actions during an incident. | ||||
| STIG | Date | |||
| Cisco ACI Router Security Technical Implementation Guide | 2025-12-11 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (5) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-004931
1.00
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
Details
Check Text (C-272103r1168419_chk)
Review the SSP and the ACI configuration to verify logical separation using EPGs, bridge domains, and/or tenants is configured.
There are a large number of places to validate that each EPG is using an organizational defined VLAN. That would be dependent on the VLAN pool associated with the Physical/ VMM Domains that the EPG is using.
To check the Physical domain in the GUI, use the following path:
Tenants >> {{your_Tenant}} >> Application Profiles >> {{your_application_profile}} >> Application EPGs >> {{your_EPG}} > Domains
After checking the domain, check the VLAN pool on the physical domains in the GUI:
Fabric >> Access Policies >> Physical and External Domains >> Physical Domains >> {{your_domain}}
For VMM Domain vlan pools, check the following GUI location:
Virtual Networking >> VMware >> {{your_VMM_Domain}} >> Policy >> General
If organization-defined alternate communication paths for system operations organizational command and control have not been established, this is a finding.
Fix Text (F-76060r1168418_fix)
Configure logical separation using EPGs, bridge domains, and/or tenants in accordance with the SSP. There are a large number of spots to validate that each EPG is using an organizational defined VLAN. That would be dependent on the VLAN pool associated with the Physical/ VMM Domains that the EPG is using.
1. Edit or create a physical domain in the GUI using the following path:
Tenants >> {{your_Tenant}} >> Application Profiles >> {{your_application_profile}} >> Application EPGs >> {{your_EPG}} > Domains
2. Create a VLAN pool on physical domains in the GUI:
Fabric >> Access Policies >> Physical and External Domains >> Physical Domains >> {{your_domain}}
3. For VMM Domain vlan pools, create a policy at the following GUI location:
Virtual Networking >> VMware >> {{your_VMM_Domain}} >> Policy >> General