OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia multicast router must be configured to bind a Protocol Independent Multicast (PIM) neighbor filter to interfaces that have PIM enabled.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283866NOKI-RT-000480SV-283866r1203847_ruleCCI-001414medium
Description
PIM is a routing protocol used to build multicast distribution trees for forwarding multicast traffic across the network infrastructure. PIM traffic must be limited to only known PIM neighbors by configuring and binding a PIM neighbor filter to interfaces that have PIM enabled. If a PIM neighbor filter is not applied to interfaces that have PIM enabled, unauthorized routers can join the PIM domain, discover and use the rendezvous points, and also advertise their rendezvous points into the domain. This can result in a denial of service by traffic flooding or result in the unauthorized transfer of data.
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (17) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AST-04Network Diagrams & Data Flow Diagrams (DFDs)
1.00
AST-04.2Control Applicability Boundary Graphical Representation
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
DCH-19Geographic Location of Data
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
IAC-21Least Privilege
1.00

+7 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-12Audit Record Generation
1.00
CM-7Least Functionality
1.00
SC-5Denial-of-service Protection
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.3
1.00
CCI1 mapping
CCI-001414
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-09
1.00
ID.AM-03
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

18 NICE work roles and 10 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-283866r1203847_chk)

This requirement is not applicable for the DODIN Backbone. Review the multicast topology diagram and determine if router interfaces are enabled for IPv4 or IPv6 multicast routing. Verify the IPv4 and IPv6 filter is applied on the PIM-enabled interface using the command below: - show router interface "TO-PE3" detail | match "Ingress Filter" Egress Filter : none Ingress Filter : 50 - show router interface "TO-PE3" detail | match "Ingr IPv6 Flt" Egr IPv6 Flt : none Ingr IPv6 Flt : 60 If PIM neighbor filters are not bound to all interfaces that have PIM enabled, this is a finding.

Fix Text (F-88336r1203846_fix)

This requirement is not applicable for the DODIN Backbone. Configure IPv4 and IPv6 filters to only accept PIM control plane traffic from documented PIM neighbors and apply them to all PIM-enabled interfaces, as shown in the example below: Configure IPv4 and IPv6 filter: - configure filter ip-filter 50 create - config>filter>ip-filter$ entry 10 - config>filter>ip-filter$ entry 10 create - config>filter>ip-filter>entry$ match protocol "pim" - config>filter>ip-filter>entry>match$ src-ip 192.100.50.1/30 - config>filter>ip-filter>entry>match$ exit - config>filter>ip-filter>entry$ action forward - config>filter>ip-filter>entry$ exit - config>filter>ip-filter$ default-action drop - config>filter>ip-filter$ exit all - configure filter ipv6-filter 60 - config>filter>ipv6-filter# entry 10 create - config>filter>ipv6-filter>entry# match next-header 103 - config>filter>ipv6-filter>entry>match# exit - config>filter>ipv6-filter>entry# action drop - config>filter>ipv6-filter>entry# exit all Apply the IPv4 filter and IPv6 on the interface: - configure router interface "TO-PE3" ingress filter ip 50 - configure router interface "TO-PE3" ingress filter ipv6 60