| V-253973 | | 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. | Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all networ... |
| V-253974 | | The Juniper BGP router must be configured to reject inbound route advertisements for any Bogon prefixes. | Accepting route advertisements for Bogon prefixes can result in the local autonomous system (AS) becoming a transit for malicious traffic as it will i... |
| V-253975 | | The Juniper BGP router must be configured to reject inbound route advertisements for any prefixes belonging to the local autonomous system (AS). | Accepting route advertisements belonging to the local AS can result in traffic looping, being black holed, or at a minimum using a nonoptimized path.... |
| V-253976 | | 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. | As a best practice, a service provider should only accept customer prefixes that have been assigned to that customer and any peering autonomous system... |
| V-253977 | | 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). | Advertisement of routes by an AS for networks that do not belong to any of its customers pulls traffic away from the authorized network. This causes a... |
| V-253984 | | The Juniper router must be configured to enforce approved authorizations for controlling the flow of information between interconnected networks in accordance with applicable policy. | Information flow control regulates authorized information to travel within a network and between interconnected networks. Controlling the flow of netw... |
| V-253985 | | The Juniper router must be configured to disable Protocol Independent Multicast (PIM) on all interfaces that are not required to support multicast routing. | If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel. Lim... |
| V-253986 | | The Juniper router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled. | PIM is a routing protocol used to build multicast distribution trees for forwarding multicast traffic across the network infrastructure. PIM traffic m... |
| V-253992 | | The Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network. | If the gateway router is not a dedicated device for the OOBM network, implementation of several safeguards for containment of management and productio... |
| V-253993 | | 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. | If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and product... |
| V-253996 | | The Juniper router must be configured to produce audit records containing information to establish where the events occurred. | Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
T... |
| V-253997 | | The Juniper router must be configured to produce audit records containing information to establish the source of the events. | Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
... |
| V-254000 | | The Juniper router must not be configured to have any feature enabled that calls home to the vendor. | Call home services will routinely send data such as configuration and diagnostic information to the vendor for routine or emergency analysis and troub... |
| V-254001 | | The Juniper router must be configured to use encryption for routing protocol authentication. | A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or even a rogue destinatio... |
| V-254002 | | The Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. | A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or even a rogue destinatio... |
| V-254003 | | 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. | VPLS defines an architecture that delivers Ethernet multipoint services over an MPLS network. Customer layer 2 frames are forwarded across the MPLS co... |
| V-254005 | | The Juniper PE router providing Virtual Private LAN Services (VPLS) must be configured to have traffic storm control thresholds on CE-facing interfaces. | A traffic storm occurs when packets flood a VPLS bridge, creating excessive traffic and degrading network performance. Traffic storm control prevents ... |
| V-254006 | | 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. | DoS is a condition when a resource is not available for legitimate users. Packet flooding distributed denial-of-service (DDoS) attacks are referred to... |
| V-254011 | | The Juniper router must be configured to drop all fragmented Internet Control Message Protocol (ICMP) packets destined to itself. | Fragmented ICMP packets can be generated by hackers for denial-of-service (DoS) attacks such as Ping O' Death and Teardrop. It is imperative that all ... |
| V-254012 | | 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. | Vulnerability assessments must be reviewed by the System Administrator, and protocols must be approved by the Information Assurance (IA) staff before ... |
| V-254013 | | The Juniper perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. | Firewall filters are used to separate data traffic into that which it will route (permitted packets) and that which it will not route (denied packets)... |
| V-254014 | | The Juniper perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. | Firewall filters are used to separate data traffic into that which it will route (permitted packets) and that which it will not route (denied packets)... |
| V-254015 | | The Juniper BGP router must be configured to reject outbound route advertisements for any prefixes belonging to the IP core. | Outbound route advertisements belonging to the core can result in traffic either looping or being black holed, or at a minimum, using a nonoptimized p... |
| V-254017 | | 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. | The uRPF feature, and ingress firewall filters, are defenses against spoofing and denial-of-service (DoS) attacks by verifying if the source address o... |
| V-254018 | | 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. | Using dedicated paths, the OOBM backbone connects the OOBM gateway routers located at the edge of the managed network and at the NOC. Dedicated links ... |
| V-254019 | | The Juniper out-of-band management (OOBM) gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC). | The OOBM network is an IP network used exclusively for the transport of OAM&P data from the network being managed to the OSS components located at the... |
| V-254020 | | 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. | If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and product... |
| V-254021 | | The Juniper router must be configured to only permit management traffic that ingresses and egresses the OOBM interface. | The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface... |
| V-254023 | | The Juniper perimeter router must be configured to block all packets with any IP options. | Packets with IP options are not fast switched and must be punted to the route engine (RE). Hackers who initiate denial-of-service (DoS) attacks on rou... |
| V-254024 | | The Juniper PE router must be configured to ignore or block all packets with any IP options. | Packets with IP options are not fast switched and, therefore, must be punted to the route engine (RE). Hackers who initiate denial-of-service (DoS) at... |
| V-254025 | | The Juniper router must be configured to implement message authentication for all control plane protocols. | A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or even a rogue destinatio... |
| V-254026 | | The Juniper BGP router must be configured to use a unique key for each autonomous system (AS) that it peers with. | If the same keys are used between eBGP neighbors, the chance of a hacker compromising any of the BGP sessions increases. It is possible that a malicio... |
| V-254027 | | The Juniper router must be configured to use keys with a duration not exceeding 180 days for authenticating routing protocol messages. | If the keys used for routing protocol authentication are guessed, the malicious user could create havoc within the network by advertising incorrect ro... |
| V-254028 | | 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. | Label Distribution Protocol (LDP) provides the signaling required for setting up and tearing down pseudowires (virtual circuits used to transport laye... |
| V-254029 | | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to authenticate all received MSDP packets. | MSDP peering with customer network routers presents additional risks to the core, whether from a rogue or misconfigured MSDP-enabled router. MSDP pass... |
| V-254030 | | The Juniper router must not be configured to have any zero-touch deployment feature enabled when connected to an operational network. | Network devices configured via a zero-touch deployment or auto-loading feature can have their startup configuration or image pushed to the device for ... |
| V-254031 | | The Juniper router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. | The Routing Engine (RE) is critical to all network operations because it is the component used to build all forwarding paths for the data plane via co... |
| V-254032 | | The Juniper router must be configured to have Gratuitous ARP disabled on all external interfaces. | A gratuitous ARP is an ARP broadcast in which the source and destination MAC addresses are the same. It is used to inform the network about a host IP ... |
| V-254034 | | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) unreachable notifications disabled on all external interfaces. | The ICMP supports IP traffic by relaying information about paths, routes, and network conditions. Routers automatically send ICMP messages under a wid... |
| V-254035 | | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) mask replies disabled on all external interfaces. | The ICMP supports IP traffic by relaying information about paths, routes, and network conditions. Routers automatically send ICMP messages under a wid... |
| V-254036 | | The Juniper router must be configured to have Internet Control Message Protocol (ICMP) redirects disabled on all external interfaces. | The ICMP supports IP traffic by relaying information about paths, routes, and network conditions. Routers automatically send ICMP messages under a wid... |
| V-254037 | | The Juniper BGP router must be configured to use the prefix limit feature to protect against route table flooding and prefix deaggregation attacks. | The effects of prefix deaggregation can degrade router performance due to the size of routing tables and also result in black-holing legitimate traffi... |
| V-254041 | | The Juniper multicast Rendezvous Point (RP) must be configured to rate limit the number of Protocol Independent Multicast (PIM) Register messages. | When a new source starts transmitting in a PIM Sparse Mode network, the DR will encapsulate the multicast packets into register messages and forward t... |
| V-254042 | | 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. | The current multicast paradigm can let any host join any multicast group at any time by sending an IGMP or MLD membership report to the DR. In a Proto... |
| V-254043 | | 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. | ASM can have many sources for the same groups (many-to-many). For many receivers, the path via the RP may not be ideal compared with the shortest path... |
| V-254045 | | The Juniper perimeter router must be configured to only allow incoming communications from authorized sources to be routed to authorized destinations. | Unrestricted traffic may contain malicious traffic that poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffi... |
| V-254046 | | The Juniper perimeter router must be configured to block inbound packets with source Bogon IP address prefixes. | Bogons include IP packets on the public internet that contain addresses that are not in any range allocated or delegated by the Internet Assigned Numb... |
| V-254048 | | The Juniper perimeter router must be configured to have Proxy ARP disabled on all external interfaces. | When Proxy ARP is enabled on a router, it allows that router to extend the network (at layer 2) across multiple interfaces (LAN segments). Because pro... |
| V-254049 | | The Juniper perimeter router must be configured to block all outbound management traffic. | For in-band management, the management network must have its own subnet to enforce control and access boundaries provided by layer 3 network nodes, su... |
| V-254051 | | 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. | Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone downloading a file ... |
| V-254052 | | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to only accept MSDP packets from known MSDP peers. | MSDP peering with customer network routers presents additional risks to the DISN Core, whether from a rogue or misconfigured MSDP-enabled router. To g... |
| V-254053 | | The Juniper perimeter router must be configured to drop fragmented IPv6 packets where the first fragment does not include the entire IPv6 header chain. | One of the fragmentation weaknesses known in IPv6 is the "undetermined transport" packet, which is the first fragment where the entire IPv6 header cha... |
| V-254054 | | The Juniper perimeter router must be configured drop IPv6 packets with a Routing Header type 0, 1, or 3255. | The routing header can be used maliciously to send a packet through a path where less robust security is in place, rather than through the presumably ... |
| V-254055 | | The Juniper perimeter router must be configured to drop IPv6 packets containing a Hop-by-Hop header with invalid option type values. | These options are intended to be for the Destination Options header only. The optional and extensible natures of the IPv6 extension headers require hi... |
| V-254056 | | The Juniper perimeter router must be configured to drop IPv6 packets containing a Destination Option header with invalid option type values. | These options are intended to be for the Hop-by-Hop header only. The optional and extensible natures of the IPv6 extension headers require higher scru... |
| V-254057 | | The Juniper perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option. | The optional and extensible natures of the IPv6 extension headers require higher scrutiny since many implementations do not always drop packets with h... |
| V-254058 | | The Juniper perimeter router must be configured to drop IPv6 packets containing the NSAP address option within Destination Option header. | The optional and extensible natures of the IPv6 extension headers require higher scrutiny since many implementations do not always drop packets with h... |
| V-254059 | | 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. | The optional and extensible natures of the IPv6 extension headers require higher scrutiny since many implementations do not always drop packets with h... |
| V-254063 | | The Juniper MPLS router must be configured to have TTL Propagation disabled. | The head end of the label-switched path (LSP), the label edge router (LER) will decrement the IP packet's time-to-live (TTL) value by one and then cop... |
| V-254066 | | The Juniper PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD). | An RD provides uniqueness to the customer address spaces within the MPLS L3VPN infrastructure. The concept of the VPN-IPv4 and VPN-IPv6 address famili... |
| V-254072 | | The Juniper router must not be configured to use IPv6 Site Local Unicast addresses. | As currently defined, site local addresses are ambiguous and can be present in multiple sites. The address itself does not contain any indication of t... |
| V-254073 | | The Juniper perimeter router must be configured to suppress Router Advertisements on all external IPv6-enabled interfaces. | Many of the known attacks in stateless autoconfiguration are defined in RFC 3756 were present in IPv4 ARP attacks. To mitigate these vulnerabilities, ... |
| V-254074 | | 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. | Configuring the network device to implement organization-wide security implementation guides and security checklists ensures compliance with federal s... |
| V-253978 | | 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. | Verifying the path a route has traversed will ensure the IP core is not used as a transit network for unauthorized or possibly even internet traffic. ... |
| V-253979 | | The Juniper router configured for Multicast Source Discovery Protocol (MSDP) must filter received source-active multicast advertisements for any undesirable multicast groups and sources. | The interoperability of BGP extensions for interdomain multicast routing and MSDP enables seamless connectivity of multicast domains between autonomou... |
| V-253980 | | 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. | To avoid global visibility of local information, there are a number of source-group (S, G) states in a PIM-SM domain that must not be leaked to anothe... |
| V-253981 | | The Juniper router configured for MSDP must limit the amount of source-active messages it accepts on per-peer basis. | To reduce any risk of a denial-of-service (DoS) attack from a rogue or misconfigured MSDP router, the router must be configured to limit the number of... |
| V-253982 | | 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. | Verifying the path a route has traversed will ensure that the local AS is not used as a transit network for unauthorized traffic. To ensure that the l... |
| V-253983 | | The Juniper router must be configured to disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication. | The use of POTS lines to modems connecting to network devices provides clear text of authentication traffic over commercial circuits that could be cap... |
| V-253987 | | The Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. | If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel.
Ad... |
| V-253988 | | The Juniper router must be configured to have all inactive interfaces disabled. | An inactive interface is rarely monitored or controlled and may expose a network to an undetected attack on that interface. Unauthorized personnel wit... |
| V-253991 | | 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. | If the static routes to the alternate gateway are being redistributed into an Exterior Gateway Protocol or Interior Gateway Protocol to a NIPRNet gate... |
| V-253994 | | 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. | Real-time multicast traffic can entail multiple large flows of data. An attacker can flood a network segment with multicast packets, over-using the av... |
| V-253995 | | 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. | Real-time multicast traffic can entail multiple large flows of data. An attacker can flood a network segment with multicast packets, over-using the av... |
| V-253998 | | The Juniper router must be configured to log all packets that have been dropped. | Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being done or attempted t... |
| V-253999 | | The Juniper router must be configured to have all nonessential capabilities disabled. | A compromised router introduces risk to the entire network infrastructure, as well as data resources that are accessible via the network. The perimete... |
| V-254004 | | The Juniper MPLS router with RSVP-TE enabled must be configured to enable refresh reduction features. | RSVP-TE can be used to perform constraint-based routing when building LSP tunnels within the network core that will support QoS and traffic engineerin... |
| V-254007 | | The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS DODIN Technical Profile. | Different applications have unique requirements and toleration levels for delay, jitter, bandwidth, packet loss, and availability. To manage the multi... |
| V-254008 | | The Juniper PE router must be configured to enforce a Quality-of-Service (QoS) policy in accordance with the QoS GIG Technical Profile. | Different applications have unique requirements and toleration levels for delay, jitter, bandwidth, packet loss, and availability. To manage the multi... |
| V-254033 | | The Juniper router must be configured to have IP directed broadcast disabled on all interfaces. | An IP directed broadcast is a datagram sent to the broadcast address of a subnet that is not directly attached to the sending machine. The directed br... |
| V-254038 | | 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. | The effects of prefix deaggregation can degrade router performance due to the size of routing tables and also result in black-holing legitimate traffi... |
| V-254039 | | 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. | IGMP snooping provides a way to constrain multicast traffic at layer 2. By monitoring the IGMP membership reports sent by hosts within the bridge doma... |
| V-254040 | | 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. | MSDP peering between networks enables sharing of multicast source information. Enclaves with an existing multicast topology using PIM-SM can configure... |
| V-254044 | | The Juniper BGP router must be configured to enable the Generalized TTL Security Mechanism (GTSM). | GTSM is designed to protect a router's IP-based control plane from DoS attacks. Many attacks focused on CPU load and line-card overload can be prevent... |
| V-254047 | | The Juniper perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces. | LLDPs are primarily used to obtain protocol addresses of neighboring devices and discover platform capabilities of those devices. Use of SNMP with the... |
| V-254050 | | 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. | Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone downloading a file ... |
| V-254060 | | The Juniper BGP router must be configured to use its loopback address as the source address for iBGP peering sessions. | Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of the BGP routers. It is ... |
| V-254061 | | The Juniper MPLS router must be configured to use its loopback address as the source address for LDP peering sessions. | Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of backbone routers. It is... |
| V-254062 | | 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. | Packet loss can occur when an IGP adjacency is established and the router begins forwarding packets using the new adjacency before the LDP label excha... |
| V-254069 | | 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. | A virtual forwarding instance (VFI) must be created on each participating PE router for each customer VLAN using VPLS for carrier Ethernet services. T... |
| V-254070 | | The Juniper Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic. | Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of MSDP routers. It is eas... |
| V-254071 | | 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. | The Neighbor Discovery protocol allows a hop limit value to be advertised by routers in a Router Advertisement message being used by hosts instead of ... |
| V-253989 | | 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. | Enclaves with alternate gateway connections must take additional steps to ensure there is no compromise on the enclave network or NIPRNet. Without ver... |
| V-253990 | | The Juniper perimeter router must not be configured to be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. | ISPs use BGP to share route information with other autonomous systems (i.e., other ISPs and corporate networks). If the perimeter router was configure... |
| V-254009 | | The Juniper perimeter router must be configured to deny network traffic by default and allow network traffic by exception. | A deny-all, permit-by-exception network communications traffic policy ensures that only connections that are essential and approved are allowed.
This... |
| V-254010 | | The Juniper router must be configured to restrict traffic destined to itself. | The routing engine (RE) handles traffic destined to the router—the key component used to build forwarding paths and is also instrumental with all netw... |
| V-254016 | | The Juniper PE router must be configured to block any traffic that is destined to IP core infrastructure. | IP/MPLS networks providing VPN and transit services must provide, at the least, the same level of protection against denial-of-service (DoS) attacks a... |
| V-254022 | | 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). | A compromised host in an enclave can be used by a malicious platform to launch cyberattacks on third parties. This is a common practice in "botnets", ... |
| V-254064 | | 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. | The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from ... |
| V-254065 | | The Juniper PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT). | The primary security model for an MPLS L3VPN as well as a VRF-lite infrastructure is traffic separation. Each interface can only be associated to one ... |
| V-254067 | | 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. | VPWS is an L2VPN technology that provides a virtual circuit between two PE routers to forward layer 2 frames between two customer-edge routers or swit... |
| V-254068 | | 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. | VPLS defines an architecture that delivers Ethernet multipoint services over an MPLS network. Customer layer 2 frames are forwarded across the MPLS co... |
