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 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Cisco IOS XR Router RTR Security Technical Implementation Guide

V-216767

CAT II (Medium)

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

Rule ID

SV-216767r945857_rule

STIG

Cisco IOS XR Router RTR Security Technical Implementation Guide

Version

V3R3

CCIs

CCI-001097

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 outbound ACL on the egress interface to block all management traffic as shown in the example below.

Step 1: Verify that all external interfaces has been configured with an outbound ACL as shown in the example below.

interface GigabitEthernet0/0/0/2
 ipv4 address 10.1.35.3 255.255.255.0
 ipv4 access-group EXTERNAL_ACL_OUTBOUND egress

Step 2: Verify that the outbound ACL discards management traffic as shown in the example below.

ipv4 access-list EXTERNAL_ACL_OUTBOUND
 10 deny tcp any any eq tacacs log-input
 20 deny tcp any any eq ssh log-input
 30 deny udp any any eq snmp log-input
 40 deny udp any any eq snmptrap log-input
 50 deny udp any any eq syslog log-input
 60 permit tcp any any eq www log-input
 70 deny ipv4 any any log-input

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 outbound ACL on the egress interface to block all management traffic.

Step 1: Configure an ACL to block egress management traffic.

RP/0/0/CPU0:R3(config)#Ipv4 access-list EXTERNAL_ACL_OUTBOUND
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   tcp any any eq tacacs log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   tcp any any eq 22 log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   udp any any eq snmp log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   udp any any eq snmptrap log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   udp any any eq syslog log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#permit tcp any any eq www log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#deny   ip any any log-input
RP/0/0/CPU0:R3(config-ipv4-acl)#end

Note: Permit commands would be configured to allow applicable outbound traffic. The example above  is allowing web traffic.

Step 2: Configure the external interfaces with the outbound ACL.

RP/0/0/CPU0:R3(config)#int g0/0/0/2
RP/0/0/CPU0:R3(config-if)#ipv4 access-group EXTERNAL_ACL_OUTBOUND egress