STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Juniper Router RTR Security Technical Implementation Guide

Version

V3R2

Release Date

Dec 5, 2024

SCAP Benchmark ID

Juniper_Router_RTR_STIG

Total Checks

96

Tags

network
CAT I: 10CAT II: 60CAT III: 26

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (96)

V-217011MEDIUMThe 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.V-217012MEDIUMThe Juniper router must be configured to implement message authentication for all control plane protocols.V-217013MEDIUMThe Juniper router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages.V-217014MEDIUMThe Juniper router must be configured to use encryption for routing protocol authentication.V-217015MEDIUMThe Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 140-2 message authentication code algorithm.V-217016LOWThe Juniper router must be configured to have all inactive interfaces disabled.V-217017LOWThe Juniper router must be configured to have all non-essential capabilities disabled.V-217018MEDIUMThe Juniper router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection.V-217019HIGHThe Juniper router must be configured to restrict traffic destined to itself.V-217020MEDIUMThe Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself.V-217021MEDIUMThe Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces.V-217022MEDIUMThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable messages disabled on all external interfaces.V-217023MEDIUMThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask reply messages disabled on all external interfaces.V-217024MEDIUMThe Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirect messages disabled on all external interfaces.V-217025LOWThe Juniper router must be configured to log all packets that have been dropped.V-217026MEDIUMThe Juniper router must be configured to produce audit records containing information to establish where the events occurred.V-217027MEDIUMThe Juniper router must be configured to produce audit records containing information to establish the source of the events.V-217028LOWThe Juniper router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication.V-217029HIGHThe Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception.V-217030MEDIUMThe Juniper perimeter router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy.V-217031MEDIUMThe Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations.V-217032MEDIUMThe Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes.V-217033HIGHThe 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.V-217034HIGHThe Juniper perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an approved gateway service provider.V-217035LOWThe 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.V-217036HIGHThe 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).V-217037MEDIUMThe Juniper perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DoD Instruction 8551.1.V-217038MEDIUMThe Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction.V-217039MEDIUMThe Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction.V-217040MEDIUMThe Juniper perimeter router must be configured to block all packets with any IP options.V-217041LOWThe Juniper perimeter router must be configured to have Link Layer Discovery Protocol (LLDP) disabled on all external interfaces.V-217042MEDIUMThe Juniper perimeter router must be configured to have Proxy ARP disabled on all external interfaces.V-217043MEDIUMThe Juniper perimeter router must be configured to block all outbound management traffic.V-217044MEDIUMThe 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.V-217045MEDIUMThe Juniper out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC).V-217046MEDIUMThe Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network.V-217047MEDIUMThe 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.V-217048MEDIUMThe 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.V-217049MEDIUMThe Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface.V-217050MEDIUMThe Juniper router providing connectivity to the NOC must be configured to forward all in-band management traffic via an IPsec tunnel.V-217051LOWThe Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM).V-217052MEDIUMThe Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with.V-217053MEDIUMThe Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes.V-217054MEDIUMThe Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS).V-217055MEDIUMThe 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.V-217056MEDIUMThe 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).V-217057MEDIUMThe Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core.V-217058LOWThe 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.V-217059LOWThe 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.V-217060MEDIUMThe Juniper BGP router must be configured to use the maximum prefixes feature to protect against route table flooding and prefix de-aggregation attacks.V-217061LOWThe 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.V-217062LOWThe Juniper BGP router must be configured to use its loopback address as the source address for iBGP peering sessions.V-217063LOWThe Juniper MPLS router must be configured to use its loopback address as the source address for LDP peering sessions.V-217064LOWThe 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.V-217065LOWThe Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features.V-217066MEDIUMThe Juniper MPLS router must be configured to have TTL Propagation disabled.V-217067HIGHThe 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.V-217068HIGHThe Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT).V-217069MEDIUMThe Juniper PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD).V-217070MEDIUMThe 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.V-217071HIGHThe 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.V-217072HIGHThe 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.V-217073MEDIUMThe Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces.V-217074LOWThe Juniper PE router must be configured to implement Protocol Independent Multicast (PIM) snooping for each Virtual Private LAN Services (VPLS) bridge domain.V-217075MEDIUMThe 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.V-217076HIGHThe Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure.V-217077MEDIUMThe Juniper PE router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all CE-facing interfaces.V-217078MEDIUMThe Juniper PE router must be configured to ignore or block all packets with any IP options.V-217079LOWThe Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile.V-217080LOWThe Juniper P router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile.V-217081MEDIUMThe 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.V-217082MEDIUMThe Juniper multicast router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing.V-217083MEDIUMThe Juniper multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled.V-217084LOWThe Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic.V-217085LOWThe 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.V-217086LOWThe 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.V-217087LOWThe 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.V-217088MEDIUMThe Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages.V-217089LOWThe 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.V-217090MEDIUMThe 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.V-217091MEDIUMThe 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.V-217092MEDIUMThe 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.V-217093MEDIUMThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers.V-217094MEDIUMThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets.V-217095LOWThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources.V-217096LOWThe 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.V-217097LOWThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to limit the amount of source-active messages it accepts on per-peer basis.V-217098LOWThe Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic.V-233292MEDIUMThe Juniper perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces.V-233293MEDIUMThe Juniper router must not be configured to use IPv6 Site Local Unicast addresses.V-233294MEDIUMThe Juniper perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3255.V-233295MEDIUMThe Juniper perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values.V-233296MEDIUMThe Juniper perimeter router must be configured to drop IPv6 packets containing a Destination Option header with invalid option type values.V-233297MEDIUMThe Juniper perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option.V-233298MEDIUMThe Juniper perimeter router must be configured to drop IPv6 packets containing the NSAP address option within Destination Option header.V-233299MEDIUMThe 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.