Skip to content

Cisco IOS Router RTR Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • The Cisco out-of-band management (OOBM) gateway router must be configured to not redistribute routes between the management network routing domain and the managed network routing domain.

    If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries; otherwise, it is possib...
    Rule Medium Severity
  • SRG-NET-000205-RTR-000011

    Group
  • The Cisco out-of-band management (OOBM) gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the Network Operations Center (NOC).

    If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries. It is imperative that h...
    Rule Medium Severity
  • SRG-NET-000205-RTR-000012

    Group
  • SRG-NET-000205-RTR-000013

    Group
  • The Cisco router providing connectivity to the Network Operations Center (NOC) must be configured to forward all in-band management traffic via an IPsec tunnel.

    When the production network is managed in-band, the management network could be housed at a NOC that is located remotely at single or multiple interconnected sites. NOC interconnectivity, as well a...
    Rule Medium Severity
  • SRG-NET-000018-RTR-000002

    Group
  • The Cisco BGP router must be configured to reject inbound route advertisements for any Bogon prefixes.

    Accepting route advertisements for Bogon prefixes can result in the local autonomous system (AS) becoming a transit for malicious traffic as it will in turn advertise these prefixes to neighbor aut...
    Rule Medium Severity
  • SRG-NET-000018-RTR-000003

    Group
  • The Cisco BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS).

    Accepting route advertisements belonging to the local AS can result in traffic looping or being black holed, or at a minimum using a non-optimized path.
    Rule Medium Severity
  • SRG-NET-000018-RTR-000004

    Group
  • The Cisco BGP router must be configured to reject inbound route advertisements from a customer edge (CE) router for prefixes that are not allocated to that customer.

    As a best practice, a service provider should only accept customer prefixes that have been assigned to that customer and any peering autonomous systems. A multi-homed customer with BGP speaking rou...
    Rule Medium Severity
  • SRG-NET-000018-RTR-000005

    Group
  • SRG-NET-000205-RTR-000006

    Group
  • The Cisco BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core.

    Outbound route advertisements belonging to the core can result in traffic either looping or being black holed, or at a minimum, using a non-optimized path.
    Rule Medium Severity
  • 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
  • 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
  • The MPLS router with RSVP-TE enabled must be configured with message pacing to adjust maximum burst and maximum number of RSVP messages to an output queue based on the link speed and input queue size of adjacent core routers.

    RSVP-TE can be used to perform constraint-based routing when building LSP tunnels within the network core that will support QoS and traffic engineering requirements. RSVP-TE is also used to enable ...
    Rule Low Severity
  • SRG-NET-000512-RTR-000004

    Group
  • 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-000205-RTR-000007

    Group
  • SRG-NET-000205-RTR-000008

    Group
  • The Cisco PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces.

    The uRPF feature is a defense against spoofing and denial-of-service (DoS) attacks by verifying if the source address of any ingress packet is reachable. To mitigate attacks that rely on forged sou...
    Rule Medium Severity
  • 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
  • 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
  • SRG-NET-000019-RTR-000013

    Group
  • SRG-NET-000019-RTR-000014

    Group
  • SRG-NET-000362-RTR-000121

    Group
  • SRG-NET-000364-RTR-000114

    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