OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco out-of-band management (OOBM) gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the Network Operations Center (NOC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-216682CISC-RT-000440SV-216682r531086_ruleCCI-001097medium
Description
If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries. It is imperative that hosts from the managed network are not able to access the OOBM gateway router.
STIGDate
Cisco IOS XE Router RTR Security Technical Implementation Guide2025-08-14

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (18) 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.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00

+8 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (10) 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.

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
SI-4System Monitoring
1.00
SI-4(11)Analyze Communications Traffic Anomalies
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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.1
1.00
3.13.2
1.00
3.13.5
1.00
CCI1 mapping
CCI-001097
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 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.

DE.CM-01
1.00
PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

15 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-216682r531086_chk)

This requirement is not applicable for the DODIN Backbone. It is only applicable if the OOBM gateway router is not a dedicated device to the OOBM backbone. Verify that traffic destined to itself is only sourced by the OOBM or the NOC. In the example below, the OOBM backbone network is 10.11.1.0/24, the NOC address spaces is 10.12.1.0/24, and the OOBM LAN address space at remote site connecting to the managed network is 10.13.1.0/24. Step 1: Note the inbound ACL applied to the OOBM interfaces. interface GigabitEthernet0/2 description OOB link to NOC ip address 10.11.1.8 255.255.255.0 ip access-group TRAFFIC_FROM_NOC in ! interface GigabitEthernet0/3 description link to OOBM LAN access switch ip address 10.13.1.1 255.255.255.0 ip access-group TRAFFIC_TO_NOC in If the ACL is not configured to only allow traffic to the route processor from the OOBM backbone and the NOC, this is a finding. Step 2: Review the inbound ACL bound to any OOB interface connecting to the OOBM backbone and verify traffic destined to itself is only from the OOBM or NOC address space. ip access-list extended TRAFFIC_FROM_NOC permit ip 10.11.1.0 0.255.255.255 host 10.11.1.8 permit ip 10.12.1.0 0.255.255.255 host 10.11.1.8 permit ip 10.11.1.0 0.255.255.255 host 10.13.1.1 permit ip 10.12.1.0 0.255.255.255 host 10.13.1.1 deny ip any host 10.11.1.8 log-input deny ip any host 10.13.1.1 log-input permit ip 10.11.1.0 0.0.0.255 10.13.1.0 0.0.0.255 permit ip 10.12.1.0 0.0.0.255 10.13.1.0 0.0.0.255 deny ip any any log-input Step 3: Review the inbound ACL bound to any OOBM LAN interfaces and verify traffic destined to itself is from the OOBM LAN address space. ip access-list extended TRAFFIC_TO_NOC permit ip 10.13.1.0 0.255.255.255 host 10.13.1.1 permit ip 10.13.1.0 0.255.255.255 host 10.11.1.8 deny ip any host 10.13.1.1 log-input deny ip any host 10.11.1.8 log-input permit ip 10.13.1.0 0.255.255.255 10.11.1.0 0.0.0.255 permit ip 10.13.1.0 0.255.255.255 10.12.1.0 0.0.0.255 deny ip any any log-input If the ACL is not configured to only allow traffic to the route processor from the OOBM LAN, this is a finding.

Fix Text (F-17913r287998_fix)

This requirement is not applicable for the DODIN Backbone. It is only applicable if the OOBM gateway router is not a dedicated device to the OOBM backbone. Step 1: Configure the ACL to only allow traffic to the route processor from the OOBM backbone and the NOC. R4(config)#ip access-list extended TRAFFIC_FROM_NOC R4(config-ext-nacl)#permit ip 10.11.1.0 0.255.255.255 host 10.11.1.8 R4(config-ext-nacl)#permit ip 10.12.1.0 0.255.255.255 host 10.11.1.8 R4(config-ext-nacl)#permit ip 10.11.1.0 0.255.255.255 host 10.13.1.1 R4(config-ext-nacl)#permit ip 10.12.1.0 0.255.255.255 host 10.13.1.1 R4(config-ext-nacl)#deny ip any host 10.11.1.8 log-input R4(config-ext-nacl)#deny ip any host 10.13.1.1 log-input R4(config-ext-nacl)#permit ip 10.11.1.0 0.0.0.255 10.13.1.0 0.0.0.255 R4(config-ext-nacl)#permit ip 10.12.1.0 0.0.0.255 10.13.1.0 0.0.0.255 R4(config-ext-nacl)#deny ip any any log-input Step 2: Configure the ACL to only allow traffic to the route processor from the OOBM LAN. R4(config)#ip access-list extended TRAFFIC_TO_NOC R4(config-ext-nacl)#permit ip 10.13.1.0 0.255.255.255 host 10.13.1.1 R4(config-ext-nacl)#permit ip 10.13.1.0 0.255.255.255 host 10.11.1.8 R4(config-ext-nacl)#deny ip any host 10.13.1.1 log-input R4(config-ext-nacl)#deny ip any host 10.11.1.8 log-input R4(config-ext-nacl)#permit ip 10.13.1.0 0.255.255.255 10.11.1.0 0.0.0.255 R4(config-ext-nacl)#permit ip 10.13.1.0 0.255.255.255 10.12.1.0 0.0.0.255 R4(config-ext-nacl)#deny ip any any log-input R4(config-ext-nacl)#exit Step 3: Apply the ACLs configured above to the appropriate OOBM interfaces as shown in the example below: R4(config)#int g0/2 R4(config-if)#ip access-group TRAFFIC_FROM_NOC in R4(config)#int g0/3 R4(config-if)#ip access-group TRAFFIC_TO_NOC in R4(config-if)#end