Skip to content

Cisco IOS XE Router RTR Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-NET-000018-RTR-000003

    Group
  • SRG-NET-000018-RTR-000004

    Group
  • SRG-NET-000018-RTR-000005

    Group
  • SRG-NET-000205-RTR-000006

    Group
  • SRG-NET-000018-RTR-000006

    Group
  • SRG-NET-000018-RTR-000010

    Group
  • SRG-NET-000362-RTR-000117

    Group
  • SRG-NET-000362-RTR-000118

    Group
  • The Cisco BGP router must be configured to limit the prefix size on any inbound route advertisement to /24, or the least significant prefixes issued to the customer.

    The effects of prefix de-aggregation can degrade router performance due to the size of routing tables and also result in black-holing legitimate traffic. Initiated by an attacker or a misconfigured...
    Rule Low Severity
  • SRG-NET-000512-RTR-000001

    Group
  • The Cisco BGP router must be configured to use its loopback address as the source address for iBGP peering sessions.

    Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of the BGP routers. It is easier to construct appropriate ingress filters...
    Rule Low Severity
  • SRG-NET-000512-RTR-000002

    Group
  • The Cisco MPLS router must be configured to use its loopback address as the source address for LDP peering sessions.

    Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of backbone routers. It is easier to construct appropriate ingress filter...
    Rule Low Severity
  • SRG-NET-000512-RTR-000003

    Group
  • SRG-NET-000193-RTR-000001

    Group
  • SRG-NET-000512-RTR-000004

    Group
  • The Cisco MPLS router must be configured to have TTL Propagation disabled.

    The head end of the label-switched path (LSP), the label edge router (LER) will decrement the IP packet's time-to-live (TTL) value by one and then copy the value to the MPLS TTL field. At each labe...
    Rule Medium Severity
  • SRG-NET-000512-RTR-000005

    Group
  • The Cisco PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.

    The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from one VPN does not leak into another VPN or into ...
    Rule High Severity
  • SRG-NET-000512-RTR-000006

    Group
  • SRG-NET-000512-RTR-000007

    Group
  • SRG-NET-000343-RTR-000001

    Group
  • The Cisco PE router providing MPLS Layer 2 Virtual Private Network (L2VPN) services must be configured to authenticate targeted Label Distribution Protocol (LDP) sessions used to exchange virtual circuit (VC) information using a FIPS-approved message authentication code algorithm.

    LDP provides the signaling required for setting up and tearing down pseudowires (virtual circuits used to transport Layer 2 frames) across an MPLS IP core network. Using a targeted LDP session, eac...
    Rule Medium Severity
  • SRG-NET-000512-RTR-000008

    Group
  • SRG-NET-000512-RTR-000009

    Group
  • The Cisco PE router providing Virtual Private LAN Services (VPLS) must be configured to have all attachment circuits defined to the virtual forwarding instance (VFI) with the globally unique VPN ID assigned for each customer VLAN.

    VPLS defines an architecture that delivers Ethernet multipoint services over an MPLS network. Customer Layer 2 frames are forwarded across the MPLS core via pseudowires using IEEE 802.1q Ethernet b...
    Rule High Severity
  • SRG-NET-000512-RTR-000010

    Group
  • SRG-NET-000193-RTR-000002

    Group
  • The Cisco PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces.

    A traffic storm occurs when packets flood a VPLS bridge, creating excessive traffic and degrading network performance. Traffic storm control prevents VPLS bridge disruption by suppressing traffic w...
    Rule Medium Severity
  • SRG-NET-000362-RTR-000119

    Group
  • SRG-NET-000192-RTR-000002

    Group
  • SRG-NET-000205-RTR-000007

    Group
  • The Cisco PE router must be configured to block any traffic that is destined to IP core infrastructure.

    IP/MPLS networks providing VPN and transit services must provide, at the least, the same level of protection against denial of service (DoS) attacks and intrusions as Layer 2 networks. Although the...
    Rule High Severity
  • SRG-NET-000205-RTR-000008

    Group
  • SRG-NET-000193-RTR-000113

    Group
  • SRG-NET-000193-RTR-000114

    Group
  • The Cisco P router must be configured to enforce a Quality-of-Service (QoS) policy to provide preferred treatment for mission-critical applications.

    Different applications have unique requirements and toleration levels for delay, jitter, bandwidth, packet loss, and availability. To manage the multitude of applications and services, a network re...
    Rule Low Severity
  • SRG-NET-000193-RTR-000112

    Group
  • SRG-NET-000019-RTR-000003

    Group
  • SRG-NET-000019-RTR-000004

    Group
  • The Cisco multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled.

    PIM is a routing protocol used to build multicast distribution trees for forwarding multicast traffic across the network infrastructure. PIM traffic must be limited to only known PIM neighbors by c...
    Rule Medium Severity
  • SRG-NET-000019-RTR-000005

    Group
  • The Cisco multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic.

    If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel. Administrative scoped multicast addresses are loc...
    Rule Low Severity
  • SRG-NET-000362-RTR-000120

    Group
  • The Cisco multicast Rendezvous Point (RP) router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) source-active entries.

    MSDP peering between networks enables sharing of multicast source information. Enclaves with an existing multicast topology using PIM-SM can configure their RP routers to peer with MSDP routers. As...
    Rule Low Severity
  • SRG-NET-000019-RTR-000013

    Group
  • The Cisco multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Register messages received from the Designated Router (DR) for any undesirable multicast groups and sources.

    Real-time multicast traffic can entail multiple large flows of data. An attacker can flood a network segment with multicast packets, over-using the available bandwidth and thereby creating a denial...
    Rule Low Severity
  • SRG-NET-000019-RTR-000014

    Group
  • The Cisco multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Router (DR) for any undesirable multicast groups.

    Real-time multicast traffic can entail multiple large flows of data. An attacker can flood a network segment with multicast packets, over-using the available bandwidth and thereby creating a denial...
    Rule Low Severity
  • SRG-NET-000362-RTR-000121

    Group

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules