OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper 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-217083JUNI-RT-000790SV-217083r604135_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 those interfaces that have PIM enabled. If a PIM neighbor filter is not applied to those 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
Juniper Router RTR Security Technical Implementation Guide2024-12-05

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-217083r604135_chk)

This requirement is not applicable for the DoDIN Backbone. Verify all interfaces enabled for PIM have a neighbor filter bound to the interface as shown in the example below. protocols { … … … pim { interface ge-1/0/1.0 { mode sparse; neighbor-policy PIM_NBR1_POLICY; } interface ge-1/1/1.0 { mode sparse; neighbor-policy PIM_NBR2_POLICY; } interface ge-2/1/0.0 { mode sparse; neighbor-policy PIM_NBR3_POLICY; } } Review the prefix list and policy statements configured for filtering PIM neighbors as shown in the example below. policy-options { prefix-list PIM_NBR1 { x.x.x.x/32; } prefix-list PIM_NBR2 { x.x.x.x/32; } prefix-list PIM_NBR3 { x.x.x.x/32; } policy-statement PIM_NBR1_POLICY { from { prefix-list PIM_NBR1; } then accept; } policy-statement PIM_NBR2_POLICY { from { prefix-list PIM_NBR2; } then accept; } policy-statement PIM_NBR3_POLICY { from { prefix-list PIM_NBR3; } then accept; } If PIM neighbor filters are not bound to all interfaces that have PIM enabled, this is a finding.

Fix Text (F-18310r297118_fix)

This requirement is not applicable for the DoDIN Backbone. Configure neighbor filters to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor filters to all PIM enabled interfaces. Configure prefix list for each neighbor. [edit policy-options] set prefix-list PIM_NBR1 x.x.x.x/32 set prefix-list PIM_NBR2 x.x.x.x/32 set prefix-list PIM_NBR3 x.x.x.x/32 Configure policy statements for each PIM neighbor. [edit policy-options] set policy-statement PIM_NBR1_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR1_POLICY then accept set policy-statement PIM_NBR2_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR2_POLICY then accept set policy-statement PIM_NBR3_POLICY from prefix-list PIM_NBR1 set policy-statement PIM_NBR3_POLICY then accept Apply the neighbor policy to all interfaces enabled for PIM. [edit protocols pim] set interface ge-1/0/1.0 neighbor-policy PIM_NBR1_POLICY set interface ge-1/1/1.0 neighbor-policy PIM_NBR1_POLICY set interface ge-2/1/0.0 neighbor-policy PIM_NBR1_POLICY