The Cisco out-of-band management (OOBM) gateway router must be configured to not redistribute routes between the management network routing domain and the managed network routing domain.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-96749	CISC-RT-000430	SV-105887r1_rule		Medium

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; otherwise, it is possible that management traffic will not be separated from production traffic. Since the managed network and the management network are separate routing domains, separate Interior Gateway Protocol routing instances must be configured on the router, one for the managed network and one for the OOBM network. In addition, the routes from the two domains must not be redistributed to each other.

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; otherwise, it is possible that management traffic will not be separated from production traffic. Since the managed network and the management network are separate routing domains, separate Interior Gateway Protocol routing instances must be configured on the router, one for the managed network and one for the OOBM network. In addition, the routes from the two domains must not be redistributed to each other.

STIG	Date
Cisco IOS XR Router RTR Security Technical Implementation Guide	2019-07-24

Details

Check Text ( C-95585r1_chk )
This requirement is not applicable for the DODIN Backbone. Verify the Interior Gateway Protocol (IGP) instance used for the managed network does not redistribute routes into the IGP instance used for the management network, and vice versa. The example below imports OSPF routes from the production route table (VRF PROD) into the management route table (VRF MGMT) using BGP. vrf MGMT address-family ipv4 unicast import route-target 4:4 8:8 ! export route-target 4:4 ! ! ! vrf PROD address-family ipv4 unicast import route-target 8:8 ! export route-target 8:8 ! ! ! … … … router ospf 2 vrf MGMT redistribute bgp 64512 area 0 interface GigabitEthernet0/0/0/0.2 ! ! ! ! router ospf 3 vrf PROD area 0 interface GigabitEthernet0/0/0/0.3 ! ! ! ! router bgp 64512 address-family ipv4 unicast ! address-family vpnv4 unicast ! vrf MGMT rd 4:4 address-family ipv4 unicast redistribute ospf 2 ! ! vrf PROD rd 8:8 address-family ipv4 unicast redistribute ospf 3 ! ! ! If the IGP instance used for the managed network redistributes routes into the IGP instance used for the management network, or vice versa, this is a finding.

Check Text ( C-95585r1_chk )

This requirement is not applicable for the DODIN Backbone.

Verify the Interior Gateway Protocol (IGP) instance used for the managed network does not redistribute routes into the IGP instance used for the management network, and vice versa. The example below imports OSPF routes from the production route table (VRF PROD) into the management route table (VRF MGMT) using BGP.

vrf MGMT
address-family ipv4 unicast
import route-target
4:4
8:8
!
export route-target
4:4
!
!
!
vrf PROD
address-family ipv4 unicast
import route-target
8:8
!
export route-target
8:8
!
!
!
…
…
…
router ospf 2
vrf MGMT
redistribute bgp 64512
area 0
interface GigabitEthernet0/0/0/0.2
!
!
!
!
router ospf 3
vrf PROD
area 0
interface GigabitEthernet0/0/0/0.3
!
!
!
!
router bgp 64512
address-family ipv4 unicast
!
address-family vpnv4 unicast
!
vrf MGMT
rd 4:4
address-family ipv4 unicast
redistribute ospf 2
!
!
vrf PROD
rd 8:8
address-family ipv4 unicast
redistribute ospf 3
!
!
!

If the IGP instance used for the managed network redistributes routes into the IGP instance used for the management network, or vice versa, this is a finding.

Fix Text (F-102427r1_fix)
This requirement is not applicable for the DODIN Backbone. Remove the configuration that imports routes from the managed network into the management network or vice versa as shown in the example below. RP/0/0/CPU0:R2(config)#vrf MGMT RP/0/0/CPU0:R2(config-vrf)#address-family ipv4 unicast RP/0/0/CPU0:R2(config-vrf-af)#no import route-target 8:8 RP/0/0/CPU0:R2(config-vrf-af)#end