| Checked | Name | Title |
|---|
| ☐ | SV-217011r604135_rule | 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. |
| ☐ | SV-217012r945861_rule | The Juniper router must be configured to implement message authentication for all control plane protocols. |
| ☐ | SV-217013r945863_rule | The Juniper router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. |
| ☐ | SV-217014r604135_rule | The Juniper router must be configured to use encryption for routing protocol authentication. |
| ☐ | SV-217015r604135_rule | The Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 140-2 message authentication code algorithm. |
| ☐ | SV-217016r604135_rule | The Juniper router must be configured to have all inactive interfaces disabled. |
| ☐ | SV-217017r604135_rule | The Juniper router must be configured to have all non-essential capabilities disabled. |
| ☐ | SV-217018r991997_rule | The Juniper router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. |
| ☐ | SV-217019r604135_rule | The Juniper router must be configured to restrict traffic destined to itself. |
| ☐ | SV-217020r604135_rule | The Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. |
| ☐ | SV-217021r855889_rule | The Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces. |
| ☐ | SV-217022r855890_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces. |
| ☐ | SV-217023r855891_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces. |
| ☐ | SV-217024r855892_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces. |
| ☐ | SV-217025r604135_rule | The Juniper router must be configured to log all packets that have been dropped. |
| ☐ | SV-217026r604135_rule | The Juniper router must be configured to produce audit records containing information to establish where the events occurred. |
| ☐ | SV-217027r604135_rule | The Juniper router must be configured to produce audit records containing information to establish the source of the events. |
| ☐ | SV-217028r604135_rule | The Juniper router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication. |
| ☐ | SV-217029r604135_rule | The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception. |
| ☐ | SV-217030r604135_rule | The Juniper perimeter router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. |
| ☐ | SV-217031r855893_rule | The Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. |
| ☐ | SV-217032r855894_rule | The Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. |
| ☐ | SV-217033r1050846_rule | The Juniper perimeter router must be configured to protect an enclave connected to an approved gateway by using an inbound filter that only permits packets with destination addresses within the site's address space. |
| ☐ | SV-217034r1050849_rule | The Juniper perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an approved gateway service provider. |
| ☐ | SV-217035r604135_rule | The Juniper 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. |
| ☐ | SV-217036r945858_rule | 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). |
| ☐ | SV-217037r604135_rule | 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. |
| ☐ | SV-217038r604135_rule | The Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. |
| ☐ | SV-217039r604135_rule | The Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. |
| ☐ | SV-217040r945859_rule | The Juniper perimeter router must be configured to block all packets with any IP options. |
| ☐ | SV-217041r855896_rule | The Juniper perimeter router must be configured to have Link Layer Discovery Protocol (LLDP) disabled on all external interfaces. |
| ☐ | SV-217042r855897_rule | The Juniper perimeter router must be configured to have Proxy ARP disabled on all external interfaces. |
| ☐ | SV-217043r1050852_rule | The Juniper perimeter router must be configured to block all outbound management traffic. |
| ☐ | SV-217044r1050855_rule | The Juniper out-of-band management (OOBM) gateway router must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit, MPLS/VPN service, or IPsec tunnel. |
| ☐ | SV-217045r604135_rule | The Juniper out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). |
| ☐ | SV-217046r604135_rule | The Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network. |
| ☐ | SV-217047r604135_rule | The Juniper 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. |
| ☐ | SV-217048r604135_rule | 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. |
| ☐ | SV-217049r604135_rule | The Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. |
| ☐ | SV-217050r604135_rule | The Juniper router providing connectivity to the NOC must be configured to forward all in-band management traffic via an IPsec tunnel. |
| ☐ | SV-217051r855898_rule | The Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). |
| ☐ | SV-217052r945862_rule | The Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. |
| ☐ | SV-217053r604135_rule | The Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. |
| ☐ | SV-217054r604135_rule | The Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). |
| ☐ | SV-217055r604135_rule | The Juniper BGP router must be configured to reject inbound route advertisements from a customer edge (CE) Juniper router for prefixes that are not allocated to that customer. |
| ☐ | SV-217056r604135_rule | 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). |
| ☐ | SV-217057r604135_rule | The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. |
| ☐ | SV-217058r945854_rule | 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. |
| ☐ | SV-217059r945855_rule | The Juniper 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. |
| ☐ | SV-217060r855900_rule | The Juniper BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks. |
| ☐ | SV-217061r855901_rule | The Juniper 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. |
| ☐ | SV-217062r992001_rule | The Juniper BGP router must be configured to use its loopback address as the source address for iBGP peering sessions. |
| ☐ | SV-217063r992002_rule | The Juniper MPLS router must be configured to use its loopback address as the source address for LDP peering sessions. |
| ☐ | SV-217064r604135_rule | The Juniper MPLS router must be configured to synchronize IGP and LDP to minimize packet loss when an IGP adjacency is established prior to LDP peers completing label exchange. |
| ☐ | SV-217065r604135_rule | The Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features. |
| ☐ | SV-217066r604135_rule | The Juniper MPLS router must be configured to have TTL Propagation disabled. |
| ☐ | SV-217067r992003_rule | The Juniper 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. |
| ☐ | SV-217068r992004_rule | The Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). |
| ☐ | SV-217069r992005_rule | The Juniper PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD). |
| ☐ | SV-217070r878055_rule | The Juniper 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. |
| ☐ | SV-217071r992006_rule | The Juniper PE router providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit. |
| ☐ | SV-217072r992007_rule | The Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have all attachment circuits defined to the routing instance with the globally unique VPLS ID assigned for each customer VLAN. |
| ☐ | SV-217073r604135_rule | The Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces. |
| ☐ | SV-217074r855903_rule | The Juniper PE router must be configured to implement Protocol Independent Multicast (PIM) snooping for each Virtual Private LAN Services (VPLS) bridge domain. |
| ☐ | SV-217075r604135_rule | 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. |
| ☐ | SV-217076r604135_rule | The Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure. |
| ☐ | SV-217077r604135_rule | The Juniper PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces. |
| ☐ | SV-217078r945860_rule | The Juniper PE router must be configured to ignore or block all packets with any IP options. |
| ☐ | SV-217079r604135_rule | The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. |
| ☐ | SV-217080r604135_rule | The Juniper P router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. |
| ☐ | SV-217081r604135_rule | 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. |
| ☐ | SV-217082r604135_rule | The Juniper multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. |
| ☐ | SV-217083r604135_rule | The Juniper multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. |
| ☐ | SV-217084r604135_rule | The Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. |
| ☐ | SV-217085r878057_rule | The Juniper 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. |
| ☐ | SV-217086r604135_rule | 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. |
| ☐ | SV-217087r604135_rule | The Juniper multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Join messages received from the Designated Juniper router (DR) for any undesirable multicast groups. |
| ☐ | SV-217088r855906_rule | The Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages. |
| ☐ | SV-217089r878058_rule | The Juniper 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. |
| ☐ | SV-217090r878059_rule | The Juniper 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. |
| ☐ | SV-217091r855909_rule | The Juniper multicast Designated Router (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. |
| ☐ | SV-217092r945856_rule | The Juniper multicast Designated Router (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. |
| ☐ | SV-217093r855911_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers. |
| ☐ | SV-217094r855912_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets. |
| ☐ | SV-217095r835204_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. |
| ☐ | SV-217096r819169_rule | The Juniper Multicast Source Discovery Protocol (MSDP) 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. |
| ☐ | SV-217097r604135_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to limit the amount of source-active messages it accepts on per-peer basis. |
| ☐ | SV-217098r992008_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic. |
| ☐ | SV-233292r604135_rule | The Juniper perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. |
| ☐ | SV-233293r604135_rule | The Juniper router must not be configured to use IPv6 Site Local Unicast addresses. |
| ☐ | SV-233294r878056_rule | The Juniper perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3255. |
| ☐ | SV-233295r855914_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values. |
| ☐ | SV-233296r855915_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing a Destination Option header with invalid option type values. |
| ☐ | SV-233297r855916_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option. |
| ☐ | SV-233298r855917_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing the NSAP address option within Destination Option header. |
| ☐ | SV-233299r855918_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop or Destination Option extension header with an undefined option type. |
STIGQter: STIG Summary: