IGP instances configured on the OOBM gateway router do not peer only with their appropriate routing domain.

From Perimeter L3 Switch Security Technical Implementation Guide

Part of IGP instances do not peer with appropriate domain

Associated with IA controls: ECSC-1

SV-19068r1_rule IGP instances configured on the OOBM gateway router do not peer only with their appropriate routing domain.

Vulnerability discussion

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. Since the managed network and the management network are separate routing domains, separate IGP routing instances must be configured on the router—one for the managed network and one for the OOBM network.

Check content

Verify that the OOBM interface is an adjacency only in the IGP routing domain for the management network.

Fix text

Ensure that multiple IGP instances configured on the OOBM gateway router peer only with their appropriate routing domain. Verify that the all interfaces are configured for the appropriate IGP instance.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.