OpenControls Logo

STIG Viewer

STIGViewer Support

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.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283875NOKI-RT-000570SV-283875r1203874_ruleCCI-002385low
Description
MSDP peering between networks enables sharing of multicast source information. Enclaves with an existing multicast topology using PIM-SM can configure their RP routers to peer with MSDP routers. As a first step of defense against a denial-of-service attack, all RP routers must limit the multicast forwarding cache to ensure that router resources are not saturated managing an overwhelming number of PIM and MSDP source-active entries.
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (13) 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.

MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
MON-01.3Inbound & Outbound Communications Traffic
1.00
MON-01.4System Generated Alerts
1.00
MON-01.8Security Event Monitoring
1.00
NET-01Network Security Controls (NSC)
1.00
NET-02Layered Network Defenses
1.00
SEA-01Secure Engineering Principles
1.00
SEA-02Alignment With Enterprise Architecture
1.00
CAP-01Capacity & Performance Management
0.50

+3 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (36) 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-10Concurrent Session Control
1.00
AC-17(9)Disconnect or Disable Access
1.00
AC-2(4)Automated Audit Actions
1.00
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
AU-3Content of Audit Records
1.00
AU-5Response to Audit Logging Process Failures
1.00
CM-11(2)Software Installation with Privileged Status
1.00

+26 more (top 10 by confidence shown)

CCI1 mapping
CCI-002385
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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-01
1.00
PR.IR-01
1.00
PR.IR-04
0.50

Who does this work

12 NICE work roles and 9 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-283875r1203874_chk)

Review the router configuration to determine if forwarding cache thresholds are defined. Verify the dist-cpu-policy applied to the interface using the command below: - show router interface "TO-PE3" detail | match OperDCpuProtPlcy OperDCpuProtPlcy : test-dcp Verify the IPv4 filter is applied on the interface using the command below: - show router interface "TO-PE2" detail | match "Ingress Filter" Egress Filter : none Ingress Filter : 10 Verify the Register-Policy is applied using the command below: - show router pim status | match Policy post-lines 1 Policy Register Policy : PIM-JOIN-POLICY If the RP router is not configured to limit the multicast forwarding cache to ensure that its resources are not saturated, this is a finding.

Fix Text (F-88345r1203873_fix)

Configure MSDP-enabled RP routers to limit the multicast forwarding cache for source-active entries, as shown in the example below: Create a prefix-list: - configure router policy-options - config>router>policy-options# begin - config>router>policy-options# prefix-list PIM-JOIN-GROUP - config>router>policy-options>prefix-list$ prefix 224.0.0.1/32 - config>router>policy-options>prefix-list$ exit Create a policy statement: - config>router>policy-options# policy-statement PIM-JOIN-POLICY - config>router>policy-options>policy-statement$ entry 10 - config>router>policy-options>policy-statement>entry$ from prefix-list "PIM-JOIN-GROUP" - config>router>policy-options>policy-statement>entry$ action drop - config>router>policy-options>policy-statement>entry>action$ exit - config>router>policy-options>policy-statement>entry$ exit - config>router>policy-options>policy-statement$ default-action accept - config>router>policy-options>policy-statement>default-action$ exit - config>router>policy-options>policy-statement$ exit - config>router>policy-options# commit - config>router>policy-options# exit all Apply the import register-policy: - configure router pim import register-policy "PIM-JOIN-POLICY" Create a dist-cpu-protection policy: - configure system security dist-cpu-protection - config>sys>security>dist-cpu-protection# policy "test-dcp" create - config>sys>security>dist-cpu-protection>policy# static-policer "PIM-RATE-LIMIT" create - config>sys>security>dist-cpu-protection>policy>static# rate packets 1 within 1 - config>sys>security>dist-cpu-protection>policy>static# exceed-action discard - config>sys>security>dist-cpu-protection>policy>static# exit - config>sys>security>dist-cpu-protection>policy# protocol pim create - config>sys>security>dist-cpu-protection>policy>protocol# enforcement static "PIM-RATE-LIMIT" - config>sys>security>dist-cpu-protection>policy>protocol# exit all Apply the dist-cpu-protection policy on the interface: - configure router interface "TO-PE3" dist-cpu-protection "test-dcp" Create an IPv4 filter: - configure filter ip-filter 10 create - config>filter>ip-filter# entry 10 - config>filter>ip-filter>entry# match protocol "tcp" - config>filter>ip-filter>entry>match# src-port 639 eq - config>filter>ip-filter>entry>match# src-ip 2.2.2.2/32 - config>filter>ip-filter>entry>match# dst-ip 1.1.1.1/32 - config>filter>ip-filter>entry>match# exit - config>filter>ip-filter>entry# action drop - config>filter>ip-filter>entry# exit all Apply the IPv4 filter on the interface: - configure router interface "TO-PE2" ingress filter ip 10