STIGViewer Support

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.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283850NOKI-RT-000320SV-283850r1203799_ruleCCI-001368low
Description
The interoperability of Border Gateway Protocol (BGP) extensions for interdomain multicast routing and MSDP enables seamless connectivity of multicast domains between autonomous systems. Multiprotocol BGP (MP-BGP) advertises the unicast prefixes of the multicast sources used by Protocol Independent Multicast (PIM) routers to perform Reverse Path Forwarding (RPF) checks and build multicast distribution trees. MSDP is a mechanism used to connect multiple PIM sparse-mode domains, allowing RPs from different domains to share information about active sources. When Rendezvous Points (RPs) in peering multicast domains hear about active sources, they can pass that information on to their local receivers, thereby allowing multicast data to be forwarded between the domains. Configuring an import policy to block multicast advertisements for reserved, Martian, single-source multicast, and any other undesirable multicast groups, as well as any source-group (S, G) states with Bogon source addresses, would assist in avoiding unwanted multicast traffic from traversing the core.
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 (42) 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-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00
AC-6(9)Log Use of Privileged Functions
1.00

+32 more (top 10 by confidence shown)

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
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.

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-283850r1203799_chk)

Review the Nokia router configuration to determine if there is export policy to block local source-active multicast advertisements. Use the command below to view the details of the policy: - show router policy "MSDP-IMPORT-SA" entry 10 from prefix-list "Multicast Group and Source" exit action drop exit exit Verify the appropriate "Import Policy" has been applied to msdp peers using the command below: - show router msdp peer detail | match "Import Policy" Import Policy : MSDP-IMPORT-SA Verify an export policy is bound to each MSDP peer. If no export policy is applied, this is a finding.

Fix Text (F-88320r1203798_fix)

Configure the MSDP router to implement an import policy to block multicast advertisements for undesirable multicast groups and sources. Configure the prefix-list: - configure router policy-options - config>router>policy-options# begin - config>router>policy-options# prefix-list "Multicast Group and Source" - config>router>policy-options>prefix-list# prefix 172.200.200.2/32 exact - config>router>policy-options>prefix-list# prefix 233.0.0.0/8 exact - config>router>policy-options>prefix-list# exit Configure the policy statement: - config>router>policy-options# policy-statement "MSDP-IMPORT-SA" - config>router>policy-options>policy-statement# entry 10 - config>router>policy-options>policy-statement>entry# from prefix-list "Multicast Group and Source" - 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 policy: - configure router msdp peer 1.1.1.1 import "MSDP-IMPORT-SA"