| V-283824 | | The Nokia Provider Edge (PE) router providing Multiprotocol Label Switching (MPLS) Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit. | VPWS is a layer 2 virtual private network (L2VPN) technology that provides a virtual circuit between two PE routers to forward layer 2 frames between ... |
| V-283826 | | The Nokia Provider Edge (PE) router providing virtual private local area network 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 a Multiprotocol Label Switching (MPLS) network. Customer layer 2 frames a... |
| V-283841 | | The Nokia router must be configured to restrict traffic destined to itself. | The route processor handles traffic destined to the router, which is the key component used to build forwarding paths and is instrumental with all net... |
| V-283843 | | The Nokia Provider Edge (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 Multiprotocol Label Switching (MPLS) layer 3 virtual private networks (L3VPNs). | The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from ... |
| V-283844 | | The Nokia Provider Edge (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 a Multiprotocol Label Switching (MPLS) Layer 3 virtual private network (L3VPN), as well as a VRF-lite infrastructure, i... |
| V-283879 | | The Nokia perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider. | Internet Service Providers (ISPs) use BGP to share route information with other autonomous systems (i.e., other ISPs and corporate networks). If the p... |
| V-283880 | | The Nokia Provider Edge (PE) router must be configured to block any traffic that is destined to Internet Protocol (IP) core infrastructure. | IP/Multi-Protocol Label Switching (MPLS) networks providing VPN and transit services must provide, at the least, the same level of protection against ... |
| V-283893 | | The Nokia 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-283913 | | The Nokia 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-283914 | | The Nokia 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-283821 | | The Nokia 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 (local area network [LAN] s... |
| V-283822 | | The 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 Designated Router will encapsulate the multicast packets into register message... |
| V-283823 | | The Nokia perimeter router must be configured to filter traffic destined to the enclave in accordance with the guidelines contained in DOD Instruction (DODI) 8551.1. | Vulnerability assessments must be reviewed by the system administrator, and protocols must be approved by the information assurance staff before enter... |
| V-283825 | | The Nokia Provider Edge (PE) router must be configured to limit the number of MAC addresses it can learn for each virtual private local access network service (VPLS) bridge domain. | VPLS defines an architecture that delivers Ethernet multipoint services over a Multiprotocol Label Switching (MPLS) network. Customer layer 2 frames a... |
| V-283829 | | The Nokia out-of-band management (OOBM) gateway must be configured to transport management traffic to the Network Operations Center (NOC) via dedicated circuit, Multiprotocol Label Switching/Virtual Private Network (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-283833 | | The Nokia 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 other connected networks. Unrestricted traffic may also transi... |
| V-283836 | | The Nokia perimeter router must be configured to drop IPv6 packets that contain 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-283837 | | The 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 Option header only. The optional and extensible natures of the IPv6 extension headers require hig... |
| V-283839 | | The Nokia Provider Edge (PE) router must be configured with Unicast Reverse Path Forwarding (uRPF) loose mode enabled on all Customer Edge (CE)-facing interfaces. | The uRPF feature is a defense against spoofing and denial-of-service attacks by verifying if the source address of any ingress packet is reachable. To... |
| V-283840 | | The Nokia perimeter router must be configured drop IPv6 packets with a Routing Header type of 0, 1, or 3-255. | 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-283842 | | The Nokia router must be configured to protect against or limit the effects of denial-of-service (DoS) attacks by employing control plane protection. | The Route Processor (RP) is critical to all network operations because it is the component used to build all forwarding paths for the data plane via c... |
| V-283845 | | The Nokia 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 because many implementations do not always drop packets with... |
| V-283846 | | The Nokia 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-283847 | | The Nokia perimeter router must be configured to drop IPv6 packets containing the network service access point (NSAP) address option within the 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-283848 | | The Nokia 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 Operations, Administration, Maintenance, and Provisioning (OAM&P) data from th... |
| V-283851 | | The Nokia 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-283852 | | The Nokia 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-283853 | | The Nokia 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-283854 | | The Nokia Multiprotocol Label Switching (MPLS) router must be configured to have time-to-live (TTL) propagation disabled. | The head end of the label-switched path (LSP), the label edge router (LER) will decrement the IP packet's TTL value by one and then copy the value to ... |
| V-283856 | | The Nokia Border Gateway Protocol (BGP) router must be configured to use the maximum prefixes 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-283857 | | The Nokia 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-283858 | | The Nokia multicast Designated Router (DR) must be configured to increase the shortest-path tree (SPT) threshold or set it to infinity to minimize source-group (S, G) state within the multicast topology where Any Source Multicast (ASM) is deployed. | SM can have many sources for the same groups (many-to-many). For many receivers, the path via the Rendezvous Point (RP) may not be ideal compared with... |
| V-283859 | | The Nokia router must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. | Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessa... |
| V-283861 | | The Nokia router must be configured to have Address Resolution Protocol (ARP) Learn Unsolicited disabled on all external interfaces. | ARP Learn Unsolicited is an ARP broadcast in which the source and destination MAC addresses are the same. It is used to inform the network about a hos... |
| V-283863 | | The Nokia 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. | Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone doing a file downlo... |
| V-283866 | | The Nokia multicast 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-283867 | | The Nokia Provider Edge (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 router processor. Hackers who initiate denial-of-service (DoS) attac... |
| V-283868 | | The Nokia perimeter router must be configured to block all packets with any IP options. | Packets with IP options are not fast switched and therefore must be punted to the router processor. Hackers who initiate denial-of-service (DoS) attac... |
| V-283870 | | The Nokia Border Gateway Protocol (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-283871 | | The Nokia perimeter router must be configured to drop IPv6 undetermined transport packets. | One of the fragmentation weaknesses known in IPv6 is the undetermined transport packet. This packet contains an undetermined protocol due to fragmenta... |
| V-283872 | | The Nokia router must not be configured to have the auto-boot feature enabled when connected to an operational network. | Nokia network devices that are configured via a zero-touch deployment or auto-loading feature can have their startup configuration or image pushed to ... |
| V-283873 | | The Nokia 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 Defense Information Systems Network (DISN) Core, whether from a rogue or m... |
| V-283874 | | The Nokia 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 Defense Information Systems Network (DISN) core, whether from a rogue or m... |
| V-283876 | | The Nokia 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 and were present in IPv4 ARP attacks. To mitigate these vulnerabiliti... |
| V-283878 | | The Nokia Provider Edge (PE) router providing Multiprotocol Label Switching (MPLS) layer 2 virtual private network (L2VPN) services must be configured to authenticate targeted Label Distribution Protocol (LDP) sessions used to exchange virtual circuit information using a Federal Information Processing Standards (FIPS)-approved message authentication code algorithm. | LDP provides the signaling required for setting up and tearing down pseudowires (virtual circuits used to transport layer 2 frames) across an MPLS IP ... |
| V-283881 | | The Nokia 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-283884 | | The Nokia Border Gateway Protocol (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. A malicious user could exist ... |
| V-283885 | | The Nokia 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-283886 | | The Nokia 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. | 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-283887 | | The Nokia 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 Network Operations Center (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-283889 | | The Nokia multicast 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 could be intercepted by unauthorized or unintended personnel. Limiting where within... |
| V-283891 | | The Nokia 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 attacks such as Ping O' Death and Teardrop. It is imperative that all fragme... |
| V-283892 | | The Nokia 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-283894 | | The Nokia Provider Edge (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-283895 | | The Nokia router must employ organization-defined controls by type of denial of service (DoS) to achieve the DoS objective. | DoS events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organization... |
| V-283897 | | The Nokia 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-283899 | | The Nokia 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-283900 | | The Nokia Border Gateway Protocol (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-283901 | | The Nokia Provider Edge (PE) router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Distinguisher (RD). | An RD provides uniqueness to the customer address spaces within the Multiprotocol Label Switching (MPLS) layer 3 virtual private network (L3VPN) infra... |
| V-283904 | | The Nokia Border Gateway Protocol (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 autonomous system for networks that do not belong to any of its customers pulls traffic away from the authorized network... |
| V-283905 | | The Nokia perimeter router must be configured to filter egress traffic at the internal interface on an inbound direction. | Access control lists (ACLs) are used to separate data traffic into traffic that will be routed (permitted packets) and traffic that will not be routed... |
| V-283906 | | The Nokia perimeter router must be configured to filter ingress traffic at the external interface on an inbound direction. | Access control lists (ACLs) are used to separate data traffic into traffic that will be routed (permitted packets) and traffic that will not be routed... |
| V-283907 | | The Nokia Border Gateway Protocol (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-283908 | | The Nokia Border Gateway Protocol (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 or being black holed, or at a minimum using a nonoptimized path... |
| V-283910 | | The Nokia Provider Edge (PE) router providing virtual private local area network services (VPLS) must be configured to have traffic broadcast storm thresholds on customer edge-facing interfaces. | A traffic storm occurs when packets flood a VPLS bridge, creating excessive traffic and degrading network performance. Traffic storm control prevents ... |
| V-283911 | | The Nokia router must be configured to authenticate all routing protocol messages using National Institute of Standards and Technology (NIST)-validated Federal Information Processing Standards (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 rogue destination. This... |
| V-283912 | | The Nokia 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 rogue destination. This... |
| V-283915 | | The Nokia router must establish organization-defined alternate communications paths for system operations organizational command and control. | An incident, whether adversarial or nonadversarial, can disrupt established communications paths used for system operations and organizational command... |
| V-283916 | | The Nokia router providing connectivity to the Network Operations Center (NOC) must be configured to forward all in-band management traffic via a Media Access Control Security (MACsec) tunnel. | When the production network is managed in-band, the management network could be housed at a NOC that is located remotely at single or multiple interco... |
| V-283827 | | The Nokia Border Gateway Protocol (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 internet traffic. All a... |
| V-283828 | | The Nokia Border Gateway Protocol (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. | Verifying the path a route has traversed will ensure the local AS is not used as a transit network for unauthorized traffic. To ensure the local AS do... |
| V-283830 | | The Nokia Border Gateway Protocol (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-283831 | | The Nokia 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-283832 | | The Nokia Multiprotocol Label Switching (MPLS) router must be configured to use its loopback address as the source address for Label Distribution Protocol (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-283834 | | The Nokia Multicast Source Discovery Protocol (MSDP) router must be configured to limit the amount of source-active messages it accepts on a 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-283835 | | The Nokia 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. | To avoid global visibility of local information, a number of source-group (S, G) states in a Protocol Independent Multicast - Sparse Mode (PIM-SM) dom... |
| V-283838 | | The Nokia router must be configured to power off Bluetooth and disable the auxiliary port unless it is connected to a secured modem providing encryption and authentication. | The use of Plain Old Telephone Service (POTS) lines to modems connecting to network devices provides clear text of authentication traffic over commerc... |
| V-283849 | | The Nokia 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 routers to advertise a hop limit value, instead of the standardized default value, in a Router Advertisement me... |
| V-283850 | | The Nokia Multicast Source Discovery Protocol (MSDP) router must be configured to filter received source-active multicast advertisements for any undesirable multicast groups and sources. | The interoperability of Border Gateway Protocol (BGP) extensions for interdomain multicast routing and MSDP enables seamless connectivity of multicast... |
| V-283855 | | The Nokia Border Gateway Protocol (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 can result in black-holing legitimate traffic... |
| V-283860 | | The Nokia Multiprotocol Label Switching (MPLS) router with Resource Reservation Protocol - Traffic Engineering (RSVP-TE) enabled must be configured with message pacing or refresh reduction to adjust the maximum number of RSVP messages to an output queue based on the link speed and input queue size of adjacent core routers. | RSVP-TE can be used to perform constraint-based routing when building label-switched path (LSP) tunnels within the network core that will support qual... |
| V-283862 | | The Nokia 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. | Real-time multicast traffic can entail multiple large flows of data. Large unicast flows tend to be fairly isolated (i.e., someone doing a file downlo... |
| V-283864 | | The Nokia 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, overusing the ava... |
| V-283865 | | The Nokia 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, overusing the ava... |
| V-283869 | | The Nokia Multiprotocol Label Switching (MPLS) router must be configured to synchronize Interior Gateway Protocol (IGP) and Label Distribution Protocol (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-283875 | | The Nokia 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. | MSDP peering between networks enables sharing of multicast source information. Enclaves with an existing multicast topology using PIM-SM can configure... |
| V-283877 | | The Nokia perimeter router must be configured to have Link Layer Discovery Protocols (LLDPs) disabled on all external interfaces and ensure LLDPs are not included in the system level. | LLDPs are primarily used to obtain protocol addresses of neighboring devices and discover platform capabilities of those devices. Use of Simple Networ... |
| V-283882 | | The Nokia Provider Edge (PE) router must be configured to implement Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) snooping for each virtual private local area network 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-283883 | | The Nokia perimeter router must be configured to not redistribute static routes to an alternate gateway service provider into Border Gateway Protocol (BGP) or an Interior Gateway Protocol (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 (EGP) or IGP to a NIPRNet gateway, this could ... |
| V-283888 | | The Nokia multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic. | If multicast traffic is forwarded beyond the intended boundary, it could be intercepted by unauthorized or unintended personnel.
Administrative scope... |
| V-283890 | | The Nokia Border Gateway Protocol (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 denial-of-service attacks. Many attacks focused on CPU load and line-card overload ... |
| V-283898 | | The Nokia router must be configured to log all packets that have been dropped. | Auditing and logging are key components of any security architecture. Security personnel must know what is being done or attempted to be done, and by ... |
| V-283902 | | The Nokia 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-283903 | | The Nokia 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-283909 | | The Nokia Provider Edge (PE) router must be configured to enforce the split-horizon rule for all pseudowires within a virtual private local area network 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... |
