STIGQter STIGQter: STIG Summary: Juniper Router RTR Security Technical Implementation Guide

Version: 1

Release: 3 Benchmark Date: 25 Oct 2019

CheckedNameTitle
SV-101017r2_ruleThe 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-101019r1_ruleThe Juniper router must be configured to implement message authentication for all control plane protocols.
SV-101021r1_ruleThe Juniper router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages.
SV-101023r1_ruleThe Juniper router must be configured to use encryption for routing protocol authentication.
SV-101025r1_ruleThe Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 140-2 message authentication code algorithm.
SV-101027r1_ruleThe Juniper router must be configured to have all inactive interfaces disabled.
SV-101029r1_ruleThe Juniper router must be configured to have all non-essential capabilities disabled.
SV-101031r1_ruleThe Juniper router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.
SV-101033r2_ruleThe Juniper router must be configured to restrict traffic destined to itself.
SV-101035r1_ruleThe Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself.
SV-101037r1_ruleThe Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces.
SV-101039r1_ruleThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces.
SV-101041r1_ruleThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces.
SV-101043r1_ruleThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces.
SV-101045r1_ruleThe Juniper router must be configured to log all packets that have been dropped.
SV-101047r1_ruleThe Juniper router must be configured to produce audit records containing information to establish where the events occurred.
SV-101049r1_ruleThe Juniper router must be configured to produce audit records containing information to establish the source of the events.
SV-101051r1_ruleThe Juniper router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication.
SV-101053r1_ruleThe Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception.
SV-101055r2_ruleThe 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-101057r2_ruleThe Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations.
SV-101059r2_ruleThe Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes.
SV-101061r1_ruleThe 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 sites address space.
SV-101063r1_ruleThe Juniper perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider.
SV-101065r1_ruleThe 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-101067r1_ruleThe 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-101069r1_ruleThe 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-101071r1_ruleThe Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction.
SV-101073r1_ruleThe Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction.
SV-101075r1_ruleThe Juniper perimeter router must be configured to block all packets with any IP options.
SV-101077r1_ruleThe Juniper perimeter router must be configured to have Link Layer Discovery Protocol (LLDP) disabled on all external interfaces.
SV-101079r1_ruleThe Juniper perimeter router must be configured to have Proxy ARP disabled on all external interfaces.
SV-101081r1_ruleThe Juniper perimeter router must be configured to block all outbound management traffic.
SV-101083r1_ruleThe 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-101085r1_ruleThe Juniper out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC).
SV-101087r1_ruleThe Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network.
SV-101089r1_ruleThe 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-101091r1_ruleThe 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-101093r2_ruleThe Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface.
SV-101095r1_ruleThe Juniper router providing connectivity to the NOC must be configured to forward all in-band management traffic via an IPsec tunnel.
SV-101097r1_ruleThe Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).
SV-101099r1_ruleThe Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with.
SV-101101r1_ruleThe Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes.
SV-101103r1_ruleThe Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS).
SV-101105r1_ruleThe 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-101107r3_ruleThe 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-101109r1_ruleThe Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core.
SV-101111r2_ruleThe 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-101113r1_ruleThe Juniper BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.
SV-101115r2_ruleThe 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-101117r1_ruleThe Juniper BGP router must be configured to use its loopback address as the source address for iBGP peering sessions.
SV-101119r1_ruleThe Juniper MPLS router must be configured to use its loopback address as the source address for LDP peering sessions.
SV-101121r1_ruleThe 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-101123r1_ruleThe Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features.
SV-101125r1_ruleThe Juniper MPLS router must be configured to have TTL Propagation disabled.
SV-101127r1_ruleThe 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-101129r1_ruleThe Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT).
SV-101131r1_ruleThe Juniper PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD).
SV-101133r1_ruleThe 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-101135r1_ruleThe 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-101137r1_ruleThe Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces.
SV-101139r1_ruleThe Juniper PE router must be configured to implement Protocol Independent Multicast (PIM) snooping for each Virtual Private LAN Services (VPLS) bridge domain.
SV-101141r1_ruleThe 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-101143r1_ruleThe Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure.
SV-101145r1_ruleThe Juniper PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces.
SV-101147r1_ruleThe Juniper PE router must be configured to ignore or block all packets with any IP options.
SV-101149r2_ruleThe Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DoDIN Technical Profile.
SV-101151r2_ruleThe Juniper P router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile.
SV-101153r1_ruleThe Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy so that all customer traffic receives forwarding treatment as specified in the service level agreement (SLA).
SV-101155r1_ruleThe Juniper 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-101157r1_ruleThe Juniper multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing.
SV-101159r1_ruleThe Juniper multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled.
SV-101161r2_ruleThe Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic.
SV-101163r1_ruleThe 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-101165r1_ruleThe 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-101167r2_ruleThe 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-101169r1_ruleThe Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages.
SV-101171r2_ruleThe 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-101173r2_ruleThe 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-101175r1_ruleThe 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-101177r1_ruleThe 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-101179r1_ruleThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers.
SV-101181r1_ruleThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets.
SV-101183r1_ruleThe 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-101185r1_ruleThe 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-101187r1_ruleThe 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-101189r1_ruleThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic.
SV-101191r1_ruleThe 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-105143r2_ruleThe 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.