The out-of-band management (OOBM) gateway router must be configured to have separate Interior Gateway Protocol (IGP) instances for the managed network and management network.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-207116 | SRG-NET-000019-RTR-000011 | SV-207116r1137925_rule | CCI-001414 | medium |
| Description | ||||
| If the gateway router is not a dedicated device for the OOBM network, implementation of several safeguards for containment of management and production traffic boundaries must occur. Since the managed and management network are separate routing domains, configuration of separate IGP routing instances is critical on the router to segregate traffic from each network. This requirement also applies to Zero Trust initiatives. | ||||
| STIG | Date | |||
| Router Security Requirements Guide | 2025-09-10 | |||
Related Frameworks
3 paths across 3 frameworks
Related Frameworks
NIST 800-531 mapping
AC-4
1.00
- DISA · V5R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.3
1.00
- DISA · V5R2 · disa_xccdf · related
- DISA · 2025-01-23 · disa_cci_list · equivalent
- NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001414
1.00
- DISA · V5R2 · disa_xccdf · related
Details
Check Text (C-207116r1137925_chk)
This requirement is not applicable for the DODIN Backbone.
Verify the OOBM interface is an adjacency in the IGP routing domain for the management network.
If the router does not enforce that IGP instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.
Fix Text (F-7377r1137924_fix)
This requirement is not applicable for the DODIN Backbone.
Configure the router to enforce that IGP instances configured on the OOBM gateway router peer only with their own routing domain.