RUCKUS ICX Router Security Technical Implementation Guide

Version: 1

Updated: 04 Sep 2025

Findings: 81

Findings

V-273569 - The RUCKUS ICX router must be configured to enforce approved authorizations for controlling the flow of information within the network based on organization-defined information flow control policies. (medium)
V-273570 - The RUCKUS ICX BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. (medium)
V-273571 - The RUCKUS ICX BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). (medium)
V-273572 - The RUCKUS ICX 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. (medium)
V-273573 - The RUCKUS ICX BGP router must be configured to reject outbound route advertisements for any prefixes that do not belong to any customer or the local autonomous system (AS). (medium)
V-273574 - The RUCKUS ICX BGP router 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. (low)
V-273575 - The RUCKUS ICX Multicast Source Discovery Protocol router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. (low)
V-273576 - The RUCKUS ICX Multicast Source Discovery Protocol router must be configured to filter source-active multicast advertisements to external MSDP peers to avoid global visibility of local-only multicast sources and groups. (low)
V-273577 - The RUCKUS ICX MSDP router must be configured to limit the amount of source-active messages it accepts on a per peer basis. (low)
V-273578 - The RUCKUS ICX BGP router must be configured to reject route advertisements from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. (low)
V-273580 - The RUCKUS ICX perimeter router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. (medium)
V-273581 - The RUCKUS ICX multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. (medium)
V-273582 - The RUCKUS ICX multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. (medium)
V-273583 - The RUCKUS ICX multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. (low)
V-273584 - The RUCKUS ICX router must be configured to have all inactive interfaces disabled. (low)
V-273585 - The RUCKUS ICX perimeter router must be configured to protect an enclave connected to an alternate gateway by using an inbound filter that only permits packets with destination addresses within the site's address space. (high)
V-273586 - The RUCKUS ICX perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. (high)
V-273587 - The RUCKUS ICX perimeter router must be configured to not redistribute static routes to an alternate gateway service provider into BGP or an IGP peering with the NIPRNet or to other autonomous systems. (low)
V-273588 - The RUCKUS ICX out-of-band management (OOBM) gateway router must be configured to have separate Interior Gateway Protocol (IGP) instances for the managed network and management network. (medium)
V-273589 - The RUCKUS ICX 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. (medium)
V-273590 - The RUCKUS ICX multicast Rendezvous Pointerface (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. (low)
V-273591 - The RUCKUS ICX multicast Rendezvous Pointerface (RP) router must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Router (DR) for any undesirable multicast groups. (low)
V-273594 - The RUCKUS ICX router must be configured to log all packets that have been dropped. (low)
V-273596 - The RUCKUS ICX router must not be configured to have any feature enabled that calls home to the vendor. (medium)
V-273597 - The RUCKUS ICX router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. (medium)
V-273601 - The RUCKUS ICX PE router must be configured to enforce a Quality-of-Service (QoS) policy to limit the effects of packet flooding denial-of-service (DoS) attacks. (medium)
V-273602 - The RUCKUS ICX PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile. (low)
V-273603 - The RUCKUS ICX P router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. (low)
V-273604 - The RUCKUS ICX perimeter router must be configured to deny network traffic by default and allow network traffic by exception. (high)
V-273605 - The RUCKUS ICX router must be configured to restrict traffic destined to itself. (high)
V-273606 - The RUCKUS ICX router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. (medium)
V-273607 - The RUCKUS ICX perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DOD Instruction 8551.1. (medium)
V-273608 - The RUCKUS ICX perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. (medium)
V-273609 - The RUCKUS ICX perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. (medium)
V-273610 - The RUCKUS ICX BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. (medium)
V-273611 - The RUCKUS ICX PE router must be configured to block any traffic destined to IP core infrastructure. (high)
V-273612 - The RUCKUS ICX PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces. (medium)
V-273613 - The RUCKUS ICX management network gateway must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit. (medium)
V-273614 - The RUCKUS ICX out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). (medium)
V-273615 - The RUCKUS ICX 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). (medium)
V-273616 - The RUCKUS ICX router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. (medium)
V-273618 - The RUCKUS ICX 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). (high)
V-273619 - The RUCKUS ICX perimeter router must be configured to block all packets with any IP options. (medium)
V-273620 - The RUCKUS ICX PE router must be configured to ignore or block all packets with any IP options. (medium)
V-273621 - The RUCKUS ICX router must be configured to implement message authentication for all control plane protocols. (medium)
V-273622 - The RUCKUS ICX BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. (medium)
V-273623 - The RUCKUS ICX router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. (medium)
V-273626 - The RUCKUS Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets. (medium)
V-273627 - The RUCKUS ICX Router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network. (medium)
V-273628 - The RUCKUS ICX router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. (medium)
V-273629 - The RUCKUS ICX router must be configured to have Gratuitous Address Resolution Protocol (ARP) disabled on all external interfaces. (medium)
V-273630 - The RUCKUS ICX router must be configured to have IP directed broadcast disabled on all interfaces. (low)
V-273631 - The RUCKUS ICX router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces. (medium)
V-273632 - The RUCKUS ICX router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces. (medium)
V-273633 - The RUCKUS ICX router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces. (medium)
V-273634 - The RUCKUS ICX BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks. (medium)
V-273635 - The RUCKUS ICX 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. (low)
V-273637 - The RUCKUS ICX multicast Rendezvous Pointerface (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. (low)
V-273638 - The RUCKUS ICX multicast Rendezvous Pointerface (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages. (medium)
V-273639 - The RUCKUS ICX Router 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. (medium)
V-273640 - The RUCKUS ICX multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimalize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed. (medium)
V-273641 - The RUCKUS ICX BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). (low)
V-273642 - The RUCKUS ICX perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. (medium)
V-273643 - The RUCKUS ICX perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. (medium)
V-273644 - The RUCKUS ICX perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces. (low)
V-273645 - The RUCKUS ICX perimeter router must be configured to have Proxy ARP disabled on all external interfaces. (medium)
V-273646 - The RUCKUS ICX perimeter router must be configured to block all outbound management traffic. (medium)
V-273647 - The RUCKUS ICX multicast Designated Router (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. (low)
V-273648 - The RUCKUS ICX multicast Designated Router (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. (medium)
V-273650 - The RUCKUS ICX perimeter router must be configured to drop IPv6 undetermined transport packets. (medium)
V-273651 - The RUCKUS ICX perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3-255. (medium)
V-273652 - The RUCKUS ICX perimeter router must be configured to drop IPv6 packets containing a hop-by-hop and destination options header with invalid or undefined option type values. (medium)
V-273654 - The RUCKUS ICX BGP Router must be configured to use its loopback address as the source address for internal border gateway protocol (iBGP) peering sessions. (low)
V-273660 - The RUCKUS ICX Router must be configured to have each VRF with the appropriate Route Distinguisher (RD). (medium)
V-273664 - The RUCKUS ICX Multicast Source Discovery Protocol (MSDP) Router must be configured to use its loopback address when originating MSDP traffic. (low)
V-273665 - The RUCKUS ICX Router must be configured to advertise a hop limit of at least 32 in Router Advertisement messages for IPv6 stateless autoconfiguration deployments. (low)
V-273666 - The RUCKUS ICX Router must not be configured to use IPv6 Site Local Unicast addresses. (medium)
V-273667 - The RUCKUS ICX Router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. (medium)
V-273669 - The RUCKUS ICX router must employ organization-defined controls by type of denial of service (DoS) to achieve the DoS objective. (medium)
V-273670 - The RUCKUS ICX router must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. (medium)
V-273671 - The RUCKUS ICX router must establish organization-defined alternate communications paths for system operations organizational command and control. (medium)