Cisco NX-OS Switch RTR Security Technical Implementation Guide

Description

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V2R1

Published: 2021-03-29

Updated At: 2021-05-02 20:54:03

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-221071r622190_rule CISC-RT-000010 CCI-001368 MEDIUM The Cisco switch must be configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies. Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all network traffic must be monitored and controlled so it does not introduce any unacceptable risk to the network
    SV-221072r622190_rule CISC-RT-000020 CCI-000366 MEDIUM The Cisco switch must be configured to implement message authentication for all control plane protocols. A rogue switch could send a fictitious routing update to convince a site's perimeter switch to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network, or
    SV-221073r622190_rule CISC-RT-000030 CCI-000366 MEDIUM The Cisco switch must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. If the keys used for routing protocol authentication are guessed, the malicious user could create havoc within the network by advertising incorrect routes and redirecting traffic. Some routing protocols allow the use of key chains for authentication. A ke
    SV-221074r622190_rule CISC-RT-000040 CCI-000803 MEDIUM The Cisco switch must be configured to use encryption for routing protocol authentication. A rogue switch could send a fictitious routing update to convince a site's perimeter switch to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network or
    SV-221075r622190_rule CISC-RT-000050 CCI-000803 MEDIUM The Cisco switch must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. A rogue switch could send a fictitious routing update to convince a site's perimeter switch to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network or
    SV-221076r622190_rule CISC-RT-000060 CCI-001414 LOW The Cisco switch must be configured to have all inactive layer 3 interfaces disabled. An inactive interface is rarely monitored or controlled and may expose a network to an undetected attack on that interface. Unauthorized personnel with access to the communication facility could gain access to a switch by connecting to a configured interf
    SV-221077r622190_rule CISC-RT-000070 CCI-000381 LOW The Cisco switch must be configured to have all non-essential capabilities disabled. A compromised switch introduces risk to the entire network infrastructure, as well as data resources that are accessible via the network. The perimeter defense has no oversight or control of attacks by malicious users within the network. Preventing networ
    SV-221078r622190_rule CISC-RT-000080 CCI-002403 MEDIUM The Cisco switch must not be configured to have any feature enabled that calls home to the vendor. Call home services will routinely send data such as configuration and diagnostic information to the vendor for routine or emergency analysis and troubleshooting. There is a risk that transmission of sensitive data sent to unauthorized persons could result
    SV-221079r622190_rule CISC-RT-000120 CCI-002385 MEDIUM The Cisco switch must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. The Route Processor (RP) is critical to all network operations because it is the component used to build all forwarding paths for the data plane via control plane processes. It is also instrumental with ongoing network management functions that keep the s
    SV-221080r622190_rule CISC-RT-000130 CCI-001097 HIGH The Cisco switch must be configured to restrict traffic destined to itself. The route processor handles traffic destined to the switch—the key component used to build forwarding paths and is instrumental with all network management functions. Hence, any disruption or DoS attack to the route processor can result in mission criti
    SV-221081r622190_rule CISC-RT-000140 CCI-001097 MEDIUM The Cisco switch must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. Fragmented ICMP packets can be generated by hackers for DoS attacks such as Ping O' Death and Teardrop. It is imperative that all fragmented ICMP packets are dropped.
    SV-221082r622190_rule CISC-RT-000150 CCI-002385 MEDIUM The Cisco switch must be configured to have Gratuitous ARP disabled on all external interfaces. A gratuitous ARP is an ARP broadcast in which the source and destination MAC addresses are the same. It is used to inform the network about a host IP address. A spoofed gratuitous ARP message can cause network mapping information to be stored incorrectly,
    SV-221083r622190_rule CISC-RT-000160 CCI-002385 LOW The Cisco switch must be configured to have IP directed broadcast disabled on all interfaces. An IP directed broadcast is a datagram sent to the broadcast address of a subnet that is not directly attached to the sending machine. The directed broadcast is routed through the network as a unicast packet until it arrives at the target subnet, where it
    SV-221084r622190_rule CISC-RT-000170 CCI-002385 MEDIUM The Cisco switch must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces. The ICMP supports IP traffic by relaying information about paths, routes, and network conditions. Switches automatically send ICMP messages under a wide variety of conditions. Host unreachable ICMP messages are commonly used by attackers for network mappi
    SV-221085r622190_rule CISC-RT-000190 CCI-002385 MEDIUM The Cisco switch must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces. The ICMP supports IP traffic by relaying information about paths, routes, and network conditions. Switches automatically send ICMP messages under a wide variety of conditions. Redirect ICMP messages are commonly used by attackers for network mapping and d
    SV-221086r622190_rule CISC-RT-000200 CCI-000134 LOW The Cisco switch must be configured to log all packets that have been dropped at interfaces via an ACL. Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being done or attempted to be done, and by whom, to compile an accurate risk assessment. Auditing the actions on network devices p
    SV-221087r622190_rule CISC-RT-000240 CCI-001109 HIGH The Cisco perimeter switch must be configured to deny network traffic by default and allow network traffic by exception. A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed. This requirement applies to both inbound and outbound network communications traffic. All inbound and outboun
    SV-221088r622190_rule CISC-RT-000250 CCI-001414 MEDIUM The Cisco perimeter switch must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. Information flow control regulates authorized information to travel within a network and between interconnected networks. Controlling the flow of network traffic is critical so it does not introduce any unacceptable risk to the network infrastructure or d
    SV-221089r622190_rule CISC-RT-000260 CCI-002403 MEDIUM The Cisco perimeter switch must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. Unrestricted traffic may contain malicious traffic that poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth and other resources. Traffic can be restricted directly by
    SV-221090r622190_rule CISC-RT-000270 CCI-002403 MEDIUM The Cisco perimeter switch must be configured to block inbound packets with source Bogon IP address prefixes. Packets with Bogon IP source addresses should never be allowed to traverse the IP core. Bogon IP networks are RFC1918 addresses or address blocks that have never been assigned by the IANA or have been reserved.
    SV-221091r622190_rule CISC-RT-000310 CCI-001094 HIGH The Cisco perimeter switch 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). 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
    SV-221092r622190_rule CISC-RT-000320 CCI-001097 MEDIUM The Cisco perimeter switch must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DoD Instruction 8551.1. Vulnerability assessments must be reviewed by the System Administrator, and protocols must be approved by the Information Assurance (IA) staff before entering the enclave. ACLs are the first line of defense in a layered security approach. They permit aut
    SV-221093r622190_rule CISC-RT-000330 CCI-001097 MEDIUM The Cisco perimeter switch must be configured to filter ingress traffic at the external interface on an inbound direction. Access lists are used to separate data traffic into that which it will route (permitted packets) and that which it will not route (denied packets). Secure configuration of switches makes use of access lists for restricting access to services on the switch
    SV-221094r622190_rule CISC-RT-000340 CCI-001097 MEDIUM The Cisco perimeter switch must be configured to filter egress traffic at the internal interface on an inbound direction. Access lists are used to separate data traffic into that which it will route (permitted packets) and that which it will not route (denied packets). Secure configuration of switches makes use of access lists for restricting access to services on the switch
    SV-221095r622190_rule CISC-RT-000350 CCI-002403 MEDIUM The Cisco perimeter switch must be configured to block all packets with any IP options. Packets with IP options are not fast switched and henceforth must be punted to the switch processor. Hackers who initiate denial-of-service (DoS) attacks on switches commonly send large streams of packets with IP options. Dropping the packets with IP opti
    SV-221096r622190_rule CISC-RT-000360 CCI-002403 LOW The Cisco perimeter switch must be configured to have Link Layer Discovery Protocol (LLDP) disabled on all external interfaces. LLDP is a neighbor discovery protocol used to advertise device capabilities, configuration information, and device identity. LLDP is media-and-protocol-independent as it runs over layer 2; therefore, two network nodes that support different layer 3 protoc
    SV-221097r622190_rule CISC-RT-000370 CCI-002403 LOW The Cisco perimeter switch must be configured to have Cisco Discovery Protocol (CDP) disabled on all external interfaces. CDP is a Cisco proprietary neighbor discovery protocol used to advertise device capabilities, configuration information, and device identity. CDP is media-and-protocol-independent as it runs over layer 2; therefore, two network nodes that support differen
    SV-221098r622190_rule CISC-RT-000380 CCI-002403 MEDIUM The Cisco perimeter switch must be configured to have Proxy ARP disabled on all external interfaces. When Proxy ARP is enabled on a switch, it allows that switch to extend the network (at Layer 2) across multiple interfaces (LAN segments). Because proxy ARP allows hosts from different LAN segments to look like they are on the same segment, proxy ARP is o
    SV-221099r622190_rule CISC-RT-000390 CCI-001097 MEDIUM The Cisco perimeter switch must be configured to block all outbound management traffic. 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 switches and firewalls. Management traffic between the managed network elements and the ma
    SV-221100r622190_rule CISC-RT-000450 CCI-001097 MEDIUM The Cisco switch must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface. The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interfac
    SV-221101r622190_rule CISC-RT-000470 CCI-002385 LOW The Cisco BGP switch must be configured to check whether a single-hop eBGP peer is directly connected. As described in RFC 3682, GTSM is designed to protect a switch's IP-based control plane from DoS attacks. Many attacks focused on CPU load and line-card overload can be prevented by implementing GTSM on all Exterior Border Gateway Protocol-speaking switch
    SV-221102r622190_rule CISC-RT-000480 CCI-002205 MEDIUM The Cisco BGP switch must be configured to use a unique key for each autonomous system (AS) that it peers with. If the same keys are used between eBGP neighbors, the chance of a hacker compromising any of the BGP sessions increases. It is possible that a malicious user exists in one autonomous system who would know the key used for the eBGP session. This user would
    SV-221103r622190_rule CISC-RT-000490 CCI-001368 MEDIUM The Cisco BGP switch 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 autonomous systems.
    SV-221104r622190_rule CISC-RT-000500 CCI-001368 MEDIUM The Cisco BGP switch 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.
    SV-221105r622190_rule CISC-RT-000510 CCI-001368 MEDIUM The Cisco BGP switch must be configured to reject inbound route advertisements from a customer edge (CE) switch 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 switches connected to the Internet or other external networks
    SV-221106r622190_rule CISC-RT-000520 CCI-001368 MEDIUM The Cisco BGP switch must be configured to reject outbound route advertisements for any prefixes that do not belong to any customers or the local autonomous system (AS). Advertisement of routes by an autonomous system for networks that do not belong to any of its customers pulls traffic away from the authorized network. This causes a denial of service (DoS) on the network that allocated the block of addresses and may caus
    SV-221107r622190_rule CISC-RT-000530 CCI-001097 MEDIUM The Cisco BGP switch 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.
    SV-221108r622190_rule CISC-RT-000540 CCI-000032 LOW The Cisco BGP switch must be configured to reject route advertisements from BGP peers that do not list their autonomous system (AS) number as the first AS in the AS_PATH attribute. Verifying the path a route has traversed will ensure the IP core is not used as a transit network for unauthorized or possibly even internet traffic. All autonomous system boundary switches (ASBRs) must ensure updates received from eBGP peers list their A
    SV-221109r622190_rule CISC-RT-000550 CCI-000032 LOW The Cisco BGP switch must be configured to reject route advertisements from CE switches with an originating AS in the AS_PATH attribute that does not belong to that customer. Verifying the path a route has traversed will ensure that the local AS is not used as a transit network for unauthorized traffic. To ensure that the local AS does not carry any prefixes that do not belong to any customers, all PE switches must be configur
    SV-221110r622190_rule CISC-RT-000560 CCI-002385 MEDIUM The Cisco BGP switch must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks. The effects of prefix de-aggregation can degrade switch performance due to the size of routing tables and also result in black-holing legitimate traffic. Initiated by an attacker or a misconfigured switch, prefix de-aggregation occurs when the announcemen
    SV-221111r622190_rule CISC-RT-000570 CCI-002385 LOW The Cisco BGP switch 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 switch performance due to the size of routing tables and also result in black-holing legitimate traffic. Initiated by an attacker or a misconfigured switch, prefix de-aggregation occurs when the announcemen
    SV-221112r622190_rule CISC-RT-000580 CCI-000366 LOW The Cisco BGP switch 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 switches. It is easier to construct appropriate ingress filters for switch management plane traffic destined to the netw
    SV-221113r622190_rule CISC-RT-000590 CCI-000366 LOW The Cisco MPLS switch 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 switches. It is easier to construct appropriate ingress filters for switch management plane traffic destined to the net
    SV-221114r622190_rule CISC-RT-000600 CCI-000366 LOW The Cisco MPLS switch must be configured to synchronize Interior Gateway Protocol (IGP) and LDP to minimize packet loss when an IGP adjacency is established prior to LDP peers completing label exchange. Packet loss can occur when an IGP adjacency is established and the switch begins forwarding packets using the new adjacency before the LDP label exchange completes between the peers on that link. Packet loss can also occur if an LDP session closes and the
    SV-221115r622190_rule CISC-RT-000610 CCI-001095 LOW The MPLS switch 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 switches. 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 MPLS Fast Reroute, a network restoration mechanism that wi
    SV-221116r622190_rule CISC-RT-000620 CCI-000366 MEDIUM The Cisco MPLS switch must be configured to have TTL Propagation disabled. The head end of the label-switched path (LSP), the label edge switch (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 label-switched switch (LSR) hop, the MPLS TTL value is decreme
    SV-221117r622190_rule CISC-RT-000630 CCI-000366 HIGH The Cisco PE switch 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 the core, and that core traffic must not leak into any VPN
    SV-221118r622190_rule CISC-RT-000640 CCI-000366 HIGH The Cisco PE switch must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). The primary security model for an MPLS L3VPN as well as a VRF-lite infrastructure is traffic separation. Each interface can only be associated to one VRF, which is the fundamental framework for traffic separation. Forwarding decisions are made based on th
    SV-221119r622190_rule CISC-RT-000650 CCI-000366 MEDIUM The Cisco PE switch must be configured to have each VRF with the appropriate Route Distinguisher (RD). An RD provides uniqueness to the customer address spaces within the MPLS L3VPN infrastructure. The concept of the VPN-IPv4 and VPN-IPv6 address families consists of the RD prepended before the IP address. Hence, if the same IP prefix is used in several di
    SV-221120r622190_rule CISC-RT-000660 CCI-001958 MEDIUM The Cisco PE switch 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, each PE switch advertises a virtual circuit label mapping tha
    SV-221121r622190_rule CISC-RT-000670 CCI-000366 HIGH The Cisco PE switch providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit. VPWS is an L2VPN technology that provides a virtual circuit between two PE switches to forward Layer 2 frames between two customer-edge switches or switches through an MPLS-enabled IP core. The ingress PE switch (virtual circuit head-end) encapsulates Eth
    SV-221122r622190_rule CISC-RT-000680 CCI-000366 HIGH The Cisco PE switch 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 bridging principles. A pseudowire is a virtual bidirectiona
    SV-221123r622190_rule CISC-RT-000700 CCI-001095 MEDIUM The Cisco PE switch 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 when the number of packets reaches configured threshold lev
    SV-221124r622190_rule CISC-RT-000710 CCI-002385 LOW The Cisco PE switch must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each Virtual Private LAN Services (VPLS) bridge domain. IGMP snooping provides a way to constrain multicast traffic at Layer 2. By monitoring the IGMP membership reports sent by hosts within the bridge domain, the snooping application can set up Layer 2 multicast forwarding tables to deliver traffic only to po
    SV-221125r622190_rule CISC-RT-000720 CCI-001094 MEDIUM The Cisco PE switch must be configured to limit the number of MAC addresses it can learn for each Virtual Private LAN Services (VPLS) bridge domain. 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 bridging principles. A pseudowire is a virtual bidirectiona
    SV-221126r622190_rule CISC-RT-000730 CCI-001097 HIGH The Cisco PE switch must be configured to block any traffic that is destined to the 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 IP core network elements are hidden, security should neve
    SV-221127r622190_rule CISC-RT-000740 CCI-001097 MEDIUM The Cisco PE switch 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 source addresses, all provider edge switches must enable uRPF
    SV-221128r622190_rule CISC-RT-000750 CCI-002403 MEDIUM The Cisco PE switch must be configured to ignore or drop all packets with any IP options. Packets with IP options are not fast-switched and therefore must be punted to the switch processor. Hackers who initiate denial-of-service (DoS) attacks on switches commonly send large streams of packets with IP options. Dropping the packets with IP optio
    SV-221129r622190_rule CISC-RT-000760 CCI-001095 LOW The Cisco PE switch must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. 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 requires a QoS framework to differentiate traffic and provid
    SV-221130r622190_rule CISC-RT-000770 CCI-001095 LOW The Cisco P switch must be configured to implement a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. 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 requires a QoS framework to differentiate traffic and provid
    SV-221131r622190_rule CISC-RT-000780 CCI-001095 MEDIUM The Cisco switch must be configured to enforce a Quality-of-Service (QoS) policy to limit the effects of packet flooding denial-of-service (DoS) attacks. DoS is a condition when a resource is not available for legitimate users. Packet flooding distributed denial-of-service (DDoS) attacks are referred to as volumetric attacks and have the objective of overloading a network or circuit to deny or seriously de
    SV-221132r622190_rule CISC-RT-000790 CCI-001414 MEDIUM The Cisco multicast switch must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel. Limiting where, within the network, a given multicast group's data is permitted to flow is an important firs
    SV-221133r622190_rule CISC-RT-000800 CCI-001414 MEDIUM The Cisco multicast switch 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 configuring and binding a PIM neighbor filter to those inte
    SV-221134r622190_rule CISC-RT-000810 CCI-001414 LOW The Cisco multicast edge switch 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 locally assigned and are to be used exclusively by the enterp
    SV-221135r622190_rule CISC-RT-000820 CCI-002385 LOW The Cisco multicast Rendezvous Point (RP) switch 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 switches to peer with MSDP switches. As a first step of defense against a denial-of-service (Do
    SV-221136r622190_rule CISC-RT-000830 CCI-001414 LOW The Cisco multicast Rendezvous Point (RP) switch must be configured to filter Protocol Independent Multicast (PIM) Register messages received from the Designated switch (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-of-service (DoS) condition. Hence, it is imperative that
    SV-221137r622190_rule CISC-RT-000840 CCI-001414 LOW The Cisco multicast Rendezvous Point (RP) switch must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Cisco switch (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-of-service (DoS) condition. Hence, it is imperative that
    SV-221138r622190_rule CISC-RT-000860 CCI-002403 LOW The Cisco multicast Designated switch (DR) must be configured to filter the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Report messages to allow hosts to join only multicast groups that have been approved by the organization. Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone doing a file download here or there), whereas multicast can have broader impact on bandwidth consumption, resulting in extre
    SV-221139r622190_rule CISC-RT-000870 CCI-002403 MEDIUM The Cisco multicast Designated switch (DR) must be configured to filter the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Report messages to allow hosts to join a multicast group only from sources that have been approved by the organization. Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone doing a file download here or there), whereas multicast can have broader impact on bandwidth consumption, resulting in extre
    SV-221140r622190_rule CISC-RT-000880 CCI-002385 MEDIUM The Cisco multicast Designated switch (DR) must be configured to limit the number of mroute states resulting from Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Host Membership Reports. The current multicast paradigm can let any host join any multicast group at any time by sending an IGMP or MLD membership report to the DR. In a Protocol Independent Multicast (PIM) Sparse Mode network, the DR will send a PIM Join message for the group to
    SV-221141r648772_rule CISC-RT-000890 CCI-000366 MEDIUM The Cisco multicast Designated switch (DR) must be configured to set the shortest-path tree (SPT) threshold to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed. ASM can have many sources for the same groups (many-to-many). For many receivers, the path via the RP may not be ideal compared with the shortest path from the source to the receiver. By default, the last-hop switch will initiate a switch from the shared
    SV-221142r622190_rule CISC-RT-000900 CCI-002403 MEDIUM The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to only accept MSDP packets from known MSDP peers. MSDP peering with customer network switches presents additional risks to the DISN Core, whether from a rogue or misconfigured MSDP-enabled switch. To guard against an attack from malicious MSDP traffic, the receive path or interface filter for all MSDP-en
    SV-221143r622190_rule CISC-RT-000910 CCI-001958 MEDIUM The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to authenticate all received MSDP packets. MSDP peering with customer network switches presents additional risks to the core, whether from a rogue or misconfigured MSDP-enabled switch. MSDP password authentication is used to validate each segment sent on the TCP connection between MSDP peers, prot
    SV-221144r622190_rule CISC-RT-000920 CCI-001368 LOW The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. The interoperability of BGP extensions for interdomain multicast routing and MSDP enables seamless connectivity of multicast domains between autonomous systems. MP-BGP advertises the unicast prefixes of the multicast sources used by Protocol Independent M
    SV-221145r622190_rule CISC-RT-000930 CCI-001368 LOW The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to filter source-active multicast advertisements to external MSDP peers to avoid global visibility of local-only multicast sources and groups. To avoid global visibility of local information, there are a number of source-group (S, G) states in a PIM-SM domain that must not be leaked to another domain, such as multicast sources with private address, administratively scoped multicast addresses, an
    SV-221146r622190_rule CISC-RT-000940 CCI-001368 LOW The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to limit the amount of source-active messages it accepts on a per-peer basis. To reduce any risk of a denial-of-service (DoS) attack from a rogue or misconfigured MSDP switch, the switch must be configured to limit the number of source-active messages it accepts from each peer.
    SV-221147r622190_rule CISC-RT-000950 CCI-000366 LOW The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to use a loopback address as the source address when originating MSDP traffic. Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of MSDP switches. It is easier to construct appropriate ingress filters for switch management plane traffic destined to the network
    SV-237754r648783_rule CISC-RT-000236 CCI-000366 LOW The Cisco switch must be configured to advertise a hop limit of at least 32 in Switch Advertisement messages for IPv6 stateless auto-configuration deployments. The Neighbor Discovery protocol allows a hop limit value to be advertised by routers in a Router Advertisement message being used by hosts instead of the standardized default value. If a very small value was configured and advertised to hosts on the LAN s
    SV-237757r648788_rule CISC-RT-000237 CCI-000366 MEDIUM The Cisco switch must not be configured to use IPv6 Site Local Unicast addresses. As currently defined, site local addresses are ambiguous and can be present in multiple sites. The address itself does not contain any indication of the site to which it belongs. The use of site-local addresses has the potential to adversely affect networ
    SV-237760r648795_rule CISC-RT-000391 CCI-000366 MEDIUM The Cisco perimeter switch must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. Many of the known attacks in stateless autoconfiguration are defined in RFC 3756 were present in IPv4 ARP attacks. To mitigate these vulnerabilities, links that have no hosts connected such as the interface connecting to external gateways must be configur