The Juniper 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-90879	JUNI-RT-000420	SV-101089r1_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
Juniper Router RTR Security Technical Implementation Guide	2018-11-15

Details

Check Text ( C-90143r2_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 routes from the global route table (inet.0) in the route table for the management VRF. } routing-options { interface-routes { rib-group inet INET0_GROUP; } rib-groups { INET0_GROUP { import-rib [ VRF_MGMT.inet.0 inet.0 ]; } } } 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-90143r2_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 routes from the global route table (inet.0) in the route table for the management VRF.

}
routing-options {
interface-routes {
rib-group inet INET0_GROUP;
}
rib-groups {
INET0_GROUP {
import-rib [ VRF_MGMT.inet.0 inet.0 ];
}
}
}

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-97187r2_fix)
This requirement is not applicable for the DoDIN Backbone. Remove the configuration that imports routes from the management network into the managed network or vice versa as shown in the example below. [edit routing-options] delete rib-groups INET0_GROUP delete interface-routes rib-group inet INET0_GROUP