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

V-216997

CAT I (High)

The Cisco perimeter router must be configured to restrict it from accepting outbound IP packets that contain an illegitimate address in the source address field via egress filter or by enabling Unicast Reverse Path Forwarding (uRPF).

Rule ID

SV-216997r945858_rule

STIG

Cisco IOS XE Router RTR Security Technical Implementation Guide

Version

V3R5

CCIs

CCI-001094

Discussion

A compromised host in an enclave can be used by a malicious platform to launch cyberattacks on third parties. This is a common practice in "botnets", which are a collection of compromised computers using malware to attack other computers or networks. DDoS attacks frequently leverage IP source address spoofing to send packets to multiple hosts that in turn will then send return traffic to the hosts with the IP addresses that were forged. This can generate significant amounts of traffic. Therefore, protection measures to counteract IP source address spoofing must be taken. When uRPF is enabled in strict mode, the packet must be received on the interface that the device would use to forward the return packet, thereby mitigating IP source address spoofing.

Check Content

This requirement is not applicable for the DODIN Backbone.

Review the router configuration to verify uRPF or an egress ACL has been configured on all internal interfaces to restrict the router from accepting outbound IP packets that contain an illegitimate address in the source address field.

uRPF example:

interface GigabitEthernet0/1
 description downstream link to LAN
 ip address 10.1.25.5 255.255.255.0
 ip verify unicast source reachable-via rx

Egress ACL example:

interface GigabitEthernet0/1
 description downstream link to LAN
 ip address 10.1.25.5 255.255.255.0
 ip access-group EGRESS_FILTER in
…
…
…
ip access-list extended EGRESS_FILTER
 permit udp 10.1.15.0 0.0.0.255 any eq domain
 permit tcp 10.1.15.0 0.0.0.255 any eq ftp
 permit tcp 10.1.15.0 0.0.0.255 any eq ftp-data
 permit tcp 10.1.15.0 0.0.0.255 any eq www
 permit icmp 10.1.15.0 0.0.0.255 any
 permit icmp 10.1.15.0 0.0.0.255 any echo
 deny   ip any any

If uRPF or an egress ACL to restrict the router from accepting outbound IP packets that contain an illegitimate address in the source address field has not been configured on all internal interfaces in an enclave, this is a finding.

Fix Text

This requirement is not applicable for the DODIN Backbone.

Configure the router to ensure that an egress ACL or uRPF is configured on internal interfaces to restrict the router from accepting any outbound IP packet that contains an illegitimate address in the source field. The example below enables uRPF.

R5(config)#int g0/1
R5(config-if)#ip verify unicast source reachable-via rx