JUEX-RT-000010 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000020 - The Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. | ACCESS CONTROL |
JUEX-RT-000030 - The Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). | ACCESS CONTROL |
JUEX-RT-000040 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000050 - The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes that do not belong to any customers or the local autonomous system (AS). | ACCESS CONTROL |
JUEX-RT-000060 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000070 - The Juniper router configured for Multicast Source Discovery Protocol (MSDP) must filter received source-active multicast advertisements for any undesirable multicast groups and sources. | ACCESS CONTROL |
JUEX-RT-000080 - The Juniper router configured for Multicast Source Discovery Protocol (MSDP) must filter source-active multicast advertisements to external MSDP peers to avoid global visibility of local-only multicast sources and groups. | ACCESS CONTROL |
JUEX-RT-000090 - The Juniper router configured for MSDP must limit the amount of source-active messages it accepts on per-peer basis. | ACCESS CONTROL |
JUEX-RT-000100 - The Juniper router configured for BGP must reject route advertisements from CE routers with an originating AS in the AS_PATH attribute that does not belong to that customer. | ACCESS CONTROL |
JUEX-RT-000110 - The Juniper router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication. | ACCESS CONTROL |
JUEX-RT-000120 - The Juniper router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. | ACCESS CONTROL |
JUEX-RT-000130 - The Juniper router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. | ACCESS CONTROL |
JUEX-RT-000140 - The Juniper router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. | ACCESS CONTROL |
JUEX-RT-000150 - The Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. | ACCESS CONTROL |
JUEX-RT-000160 - The Juniper router must be configured to have all inactive interfaces disabled. | ACCESS CONTROL |
JUEX-RT-000170 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000180 - The Juniper perimeter router must not be configured to be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. | ACCESS CONTROL |
JUEX-RT-000190 - The Juniper perimeter router must not be configured to redistribute static routes to an alternate gateway service provider into BGP or an IGP peering with the NIPRNet or to other autonomous systems. | ACCESS CONTROL |
JUEX-RT-000200 - The Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network. | ACCESS CONTROL |
JUEX-RT-000210 - The Juniper out-of-band management (OOBM) gateway router must not be configured to redistribute routes between the management network routing domain and the managed network routing domain. | ACCESS CONTROL |
JUEX-RT-000220 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000230 - The Juniper 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. | ACCESS CONTROL |
JUEX-RT-000240 - The Juniper router must be configured to produce audit records containing information to establish where the events occurred. | AUDIT AND ACCOUNTABILITY |
JUEX-RT-000250 - The Juniper router must be configured to produce audit records containing information to establish the source of the events. | AUDIT AND ACCOUNTABILITY |
JUEX-RT-000260 - The Juniper router must be configured to log all packets that have been dropped. | AUDIT AND ACCOUNTABILITY |
JUEX-RT-000270 - The Juniper router must be configured to have all nonessential capabilities disabled. | CONFIGURATION MANAGEMENT |
JUEX-RT-000280 - The Juniper router must not be configured to have any feature enabled that calls home to the vendor. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000290 - The Juniper router must be configured to use encryption for routing protocol authentication. | IDENTIFICATION AND AUTHENTICATION |
JUEX-RT-000300 - The Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. | IDENTIFICATION AND AUTHENTICATION |
JUEX-RT-000310 - The Juniper PE router must be configured to limit the number of MAC addresses it can learn for each Virtual Private LAN Services (VPLS) bridge domain. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000320 - The Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000330 - The Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000340 - The Juniper 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. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000350 - The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000360 - The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile - QoS policy in accordance with the QoS GIG Technical Profile. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000370 - The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000380 - The Juniper router must be configured to restrict traffic destined to itself. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000390 - The Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000400 - The Juniper perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DoD Instruction 8551.1. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000410 - The Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000420 - The Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000430 - The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000440 - The Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000450 - The Juniper PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode, or a firewall filter, enabled on all CE-facing interfaces. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000460 - The Juniper out-of-band management (OOBM) gateway must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit, MPLS/VPN service, or IPsec tunnel. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000470 - The Juniper out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000480 - The Juniper 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 NOC. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000490 - The Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. | SYSTEM AND COMMUNICATIONS PROTECTION |
JUEX-RT-000500 - The Juniper 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). | SYSTEM AND COMMUNICATIONS PROTECTION |