| Checked | Name | Title |
|---|
| ☐ | SV-253973r843952_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-253974r843955_rule | The Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. |
| ☐ | SV-253975r843958_rule | The Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). |
| ☐ | SV-253976r843961_rule | 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. |
| ☐ | SV-253977r843964_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-253978r945854_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-253979r843970_rule | The Juniper router configured for Multicast Source Discovery Protocol (MSDP) must filter received source-active multicast advertisements for any undesirable multicast groups and sources. |
| ☐ | SV-253980r843973_rule | 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. |
| ☐ | SV-253981r843976_rule | The Juniper router configured for MSDP must limit the amount of source-active messages it accepts on per-peer basis. |
| ☐ | SV-253982r945855_rule | 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. |
| ☐ | SV-253983r843982_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-253984r843985_rule | The Juniper router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. |
| ☐ | SV-253985r843988_rule | The Juniper router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. |
| ☐ | SV-253986r843991_rule | The Juniper router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. |
| ☐ | SV-253987r843994_rule | The Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. |
| ☐ | SV-253988r843997_rule | The Juniper router must be configured to have all inactive interfaces disabled. |
| ☐ | SV-253989r997520_rule | 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. |
| ☐ | SV-253990r844003_rule | The Juniper perimeter router must not be configured to be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. |
| ☐ | SV-253991r844006_rule | 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. |
| ☐ | SV-253992r844009_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-253993r844012_rule | 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. |
| ☐ | SV-253994r844015_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-253995r844018_rule | 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. |
| ☐ | SV-253996r844021_rule | The Juniper router must be configured to produce audit records containing information to establish where the events occurred. |
| ☐ | SV-253997r844024_rule | The Juniper router must be configured to produce audit records containing information to establish the source of the events. |
| ☐ | SV-253998r844027_rule | The Juniper router must be configured to log all packets that have been dropped. |
| ☐ | SV-253999r844030_rule | The Juniper router must be configured to have all nonessential capabilities disabled. |
| ☐ | SV-254000r844033_rule | The Juniper router must not be configured to have any feature enabled that calls home to the vendor. |
| ☐ | SV-254001r844036_rule | The Juniper router must be configured to use encryption for routing protocol authentication. |
| ☐ | SV-254002r904444_rule | The Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. |
| ☐ | SV-254003r844042_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-254004r844045_rule | The Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features. |
| ☐ | SV-254005r844048_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-254006r997521_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-254007r997522_rule | The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile. |
| ☐ | SV-254008r997523_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-254009r844060_rule | The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception. |
| ☐ | SV-254010r997524_rule | The Juniper router must be configured to restrict traffic destined to itself. |
| ☐ | SV-254011r997525_rule | The Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. |
| ☐ | SV-254012r844069_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-254013r844072_rule | The Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. |
| ☐ | SV-254014r844075_rule | The Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. |
| ☐ | SV-254015r844078_rule | The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. |
| ☐ | SV-254016r997526_rule | The Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure. |
| ☐ | SV-254017r997527_rule | 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. |
| ☐ | SV-254018r997528_rule | 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. |
| ☐ | SV-254019r844090_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-254020r844093_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-254021r997529_rule | The Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. |
| ☐ | SV-254022r997530_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-254023r997531_rule | The Juniper perimeter router must be configured to block all packets with any IP options. |
| ☐ | SV-254024r997532_rule | The Juniper PE router must be configured to ignore or block all packets with any IP options. |
| ☐ | SV-254025r945861_rule | The Juniper router must be configured to implement message authentication for all control plane protocols. |
| ☐ | SV-254026r945862_rule | The Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. |
| ☐ | SV-254027r945863_rule | The Juniper router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. |
| ☐ | SV-254028r844260_rule | The router providing MPLS L2VPN services must be configured to authenticate targeted LDP sessions used to exchange VC information using a FIPS-approved message authentication code algorithm. |
| ☐ | SV-254029r844120_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets. |
| ☐ | SV-254030r844123_rule | The Juniper router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network. |
| ☐ | SV-254031r997533_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-254032r844129_rule | The Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces. |
| ☐ | SV-254033r997534_rule | The Juniper router must be configured to have IP directed broadcast disabled on all interfaces. |
| ☐ | SV-254034r844135_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces. |
| ☐ | SV-254035r844138_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces. |
| ☐ | SV-254036r844141_rule | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces. |
| ☐ | SV-254037r844144_rule | The Juniper BGP router must be configured to use the prefix limit feature to protect against route table flooding and prefix deaggregation attacks. |
| ☐ | SV-254038r844147_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-254039r844150_rule | The Juniper PE router 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. |
| ☐ | SV-254040r997535_rule | The Juniper multicast RP router must be configured to limit the multicast forwarding cache so that its resources are not saturated by managing an overwhelming number of PIM and MSDP source-active entries. |
| ☐ | SV-254041r844156_rule | The Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages. |
| ☐ | SV-254042r844159_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-254043r945856_rule | The Juniper 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. |
| ☐ | SV-254044r997536_rule | The Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). |
| ☐ | SV-254045r844168_rule | The Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. |
| ☐ | SV-254046r844171_rule | The Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. |
| ☐ | SV-254047r844174_rule | The Juniper perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces. |
| ☐ | SV-254048r844177_rule | The Juniper perimeter router must be configured to have Proxy ARP disabled on all external interfaces. |
| ☐ | SV-254049r945857_rule | The Juniper perimeter router must be configured to block all outbound management traffic. |
| ☐ | SV-254050r844262_rule | The Juniper multicast Designated Router (DR) must be configured to filter the IGMP and MLD Report messages to allow hosts to join only multicast groups that have been approved by the organization. |
| ☐ | SV-254051r844263_rule | The Juniper multicast Designated Router (DR) must be configured to filter the IGMP and MLD Report messages to allow hosts to join a multicast group only from sources that have been approved by the organization. |
| ☐ | SV-254052r844189_rule | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers. |
| ☐ | SV-254053r950991_rule | The Juniper perimeter router must be configured to drop fragmented IPv6 packets where the first fragment does not include the entire IPv6 header chain. |
| ☐ | SV-254054r844195_rule | The Juniper perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3255. |
| ☐ | SV-254055r844198_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values. |
| ☐ | SV-254056r844201_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing a Destination Option header with invalid option type values. |
| ☐ | SV-254057r844204_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option. |
| ☐ | SV-254058r844207_rule | The Juniper perimeter router must be configured to drop IPv6 packets containing the NSAP address option within Destination Option header. |
| ☐ | SV-254059r844210_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. |
| ☐ | SV-254060r844213_rule | The Juniper BGP router must be configured to use its loopback address as the source address for iBGP peering sessions. |
| ☐ | SV-254061r844216_rule | The Juniper MPLS router must be configured to use its loopback address as the source address for LDP peering sessions. |
| ☐ | SV-254062r844219_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-254063r844222_rule | The Juniper MPLS router must be configured to have TTL Propagation disabled. |
| ☐ | SV-254064r997537_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-254065r997538_rule | The Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). |
| ☐ | SV-254066r844231_rule | The Juniper PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD). |
| ☐ | SV-254067r844234_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-254068r997539_rule | The Juniper PE router 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. |
| ☐ | SV-254069r844240_rule | The Juniper PE router must be configured to enforce the split-horizon rule for all pseudowires within a Virtual Private LAN Services (VPLS) bridge domain. |
| ☐ | SV-254070r844243_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-254071r844246_rule | The Juniper router must be configured to advertise a hop limit of at least 32 in Router Advertisement messages for IPv6 stateless auto-configuration deployments. |
| ☐ | SV-254072r844249_rule | The Juniper router must not be configured to use IPv6 Site Local Unicast addresses. |
| ☐ | SV-254073r844252_rule | The Juniper perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. |
| ☐ | SV-254074r844255_rule | The Juniper router must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
STIGQter: STIG Summary: