STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated just now
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Router Security Requirements Guide

V-207167

CAT II (Medium)

The perimeter router must be configured to block all outbound management traffic.

Rule ID

SV-207167r945857_rule

STIG

Router Security Requirements Guide

Version

V5R2

CCIs

CCI-002403

Discussion

For in-band management, the management network must have its own subnet in order to enforce control and access boundaries provided by Layer 3 network nodes, such as routers and firewalls. Management traffic between the managed network elements and the management network is routed via the same links and nodes as that used for production or operational traffic. Safeguards must be implemented to ensure that the management traffic does not leak past the perimeter of the managed network.

Check Content

This requirement is not applicable for the DoDIN Backbone.

The perimeter router of the managed network must be configured with an access control list (ACL) or filter on the egress interface to block all management traffic.

If management traffic is not blocked at the perimeter, this is a finding.

Fix Text

This requirement is not applicable for the DoDIN Backbone.

Configure the perimeter router of the managed network with an ACL or filter on the egress interface to block all outbound management traffic.