The BGP Cisco ACI must be configured to use a unique key for each autonomous system (AS) it peers with.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-272083 | CACI-RT-000023 | SV-272083r1114278_rule | CCI-001184 | medium |
| Description | ||||
| If the same keys are used between eBGP neighbors, the chance of a hacker compromising any of the BGP sessions increases. It is possible that a malicious user exists in one autonomous system who would know the key used for the eBGP session. This user would then be able to hijack BGP sessions with other trusted neighbors. | ||||
| STIG | Date | |||
| Cisco ACI Router Security Technical Implementation Guide | 2025-06-18 | |||
Related Frameworks
1 mapping across 4 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)1intersects(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 (30) 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)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V2R6our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)2intersects(normalised)DISA STIG Benchmark (XCCDF)V2R6intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(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)1intersects(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)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA STIG Benchmark (XCCDF)1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
+20 more (top 10 by confidence shown)
NIST 800-1710 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.
3.13.15
1.00
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- NIST SP 800-171 Rev 2, Appendix DRev 2 (Feb 2020, errata Jan 2021)equal to(normalised)
CCI1 mapping
CCI-001184
1.00
- DISA STIG Benchmark (XCCDF)1intersects(normalised)
Details
Check Text (C-272083r1114278_chk)
Review the configuration. Verify the neighbor authentication keys on ACI border leaf switches use a different authentication key for each AS peer. Route maps can also show this view.
ip tcp authentication key chain AS100
key 1 send-id 10 recv-id 10
key 2 send-id 20 recv-id 20
ip tcp authentication key chain AS200
key 1 send-id 30 recv-id 30
key 2 send-id 40 recv-id 40
router bgp 100
neighbor 10.0.0.1 ao AS100
router bgp 200
neighbor 10.0.1.1 ao AS200
If unique keys are not being used, this is a finding.
Fix Text (F-76040r1114277_fix)
Configure unique keys for each AS peered by a Cisco ACI device using TCP-AO by creating separate key chains for each AS, ensuring each key chain contains unique "send-id" and "recv-id" values for the keys within it, and then associating the appropriate key chain with the BGP neighbor configuration for that specific AS. The following is an example:
1. Create key chain for AS100.
apic1(config)# ip tcp authentication key chain AS100
apic1(config)# key 1 send-id 10 recv-id 10
apic1(config)# key 2 send-id 20 recv-id 20
2. Create key chain for AS 200.
apic1(config)#ip tcp authentication key chain AS200
apic1(config)# key 1 send-id 30 recv-id 30
apic1(config)# key 2 send-id 40 recv-id 40
3. Configure BGP neighbor with AS100 using key chain AS100.
apic1(config)# router bgp 100
apic1(config-router)# neighbor 10.0.0.1 ao AS100
4. Configure BGP neighbor with AS 200 using key chain AS200.
apic1(config)# router bgp 200
apic1(config-router)# neighbor 10.0.1.1 ao AS200