DISA STIGS Viewer

The Cisco ACI must be configured to only permit management traffic that ingresses and egresses the OOBM interface.

Overview

Finding ID Version Rule ID IA Controls Severity
V-272081 CACI-RT-000021 SV-272081r1114276_rule   Medium
Description
To configure OOB management on an ACI fabric, use the Application Policy Infrastructure Controller (APIC), which is the central management point for the network. When setting up OOB access, a specific "contract" that controls which traffic is allowed on the OOB management network is typically defined. All management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network.
STIG Date
Cisco ACI Router Security Technical Implementation Guide 2025-06-18

Details

Check Text (C-76131r1114274_chk)
Use the "show" command to verify the contract is attached to the management interface and that only permitted management traffic is allowed.

If the router does not restrict traffic that ingresses and egresses the management interface, this is a finding.

1. Verify the OOB contract is configured to explicitly permit only management traffic.

apic1(config)# contract MGMT_OOB
apic1(config)# filter ingress
apic1(config)# protocol icmp
apic1(config)# protocol tcp port 22, 80, 443
apic1(config)# protocol udp port 68, 67
apic1(config)# filter egress
apic1(config)# protocol icmp
apic1(config)# protocol tcp port 22, 80, 443
apic1(config)# protocol udp port 68, 67

2. Verify the contract attached to the OOB Interface.

apic1(config)# interface <leaf_switch_name>/<oob_interface_number>
apic1(config-if)# contract mgmt_oob
Fix Text (F-76038r1114275_fix)
Create a dedicated "OOB" contract that explicitly permits necessary management protocols on the OOB subnet, then apply this contract to the relevant node management interface.

1. Navigate to the relevant tenant and create a new external network instance profile for the OOB subnet.

apic1(config)# tenant <tenant_name>

2. Create the OOB contract.

apic1(config)# contract MGMT_OOB
apic1(config)# filter ingress
apic1(config)# protocol icmp
apic1(config)# protocol tcp port 22, 80, 443
apic1(config)# protocol udp port 68, 67
apic1(config)# filter egress
apic1(config)# protocol icmp
apic1(config)# protocol tcp port 22, 80, 443
apic1(config)# protocol udp port 68, 67

3. Apply the Contract to the OOB Interface.

apic1(config)# interface <leaf_switch_name>/<oob_interface_number>
apic1(config-if)# contract mgmt_oob