OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco Multicast Source Discovery Protocol (MSDP) switch must be configured to only accept MSDP packets from known MSDP peers.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-221064CISC-RT-000900SV-221064r856427_ruleCCI-002403medium
Description
MSDP peering with customer network switches presents additional risks to the DISN Core, whether from a rogue or misconfigured MSDP-enabled switch. To guard against an attack from malicious MSDP traffic, the receive path or interface filter for all MSDP-enabled RP switches must be configured to only accept MSDP packets from known MSDP peers.
STIGDate
Cisco IOS XE Switch RTR Security Technical Implementation Guide2025-05-20

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

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

NET-03Boundary Protection
0.50
NET-04.1Deny Traffic by Default & Allow Traffic by Exception
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (8) 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.

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
CCI1 mapping
CCI-002403
1.00

Details

Check Text (C-221064r856427_chk)

Review the switch configuration to determine if there is a receive path or interface filter to only accept MSDP packets from known MSDP peers. Step 1: Verify that interfaces used for MSDP peering have an inbound ACL as shown in the example below: interface GigabitEthernet1/1 no switchport ip address x.1.28.8 255.255.255.0 ip access-group EXTERNAL_ACL_INBOUND in ip pim sparse-mode Step 2: Verify that the ACL restricts MSDP peering to only known sources. ip access-list extended EXTERNAL_ACL_INBOUND permit tcp any any established permit tcp host x.1.28.2 host x.1.28.8 eq 639 deny tcp any host x.1.28.8 eq 639 log permit tcp host x.1.28.2 host 10.1.28.8 eq bgp permit tcp host x.1.28.2 eq bgp host x.1.28.8 permit pim host x.1.28.2 host x.1.28.8 … … … deny ip any any log Note: MSDP connections is via TCP port 639. If the switch is not configured to only accept MSDP packets from known MSDP peers, this is a finding.

Fix Text (F-22768r408987_fix)

Configure the receive path or interface ACLs to only accept MSDP packets from known MSDP peers. SW1(config)#ip access-list extended EXTERNAL_ACL_INBOUND SW1(config-ext-nacl)#permit tcp any any established SW1(config-ext-nacl)#permit tcp host x.1.28.2 host x.1.28.8 eq 639 SW1(config-ext-nacl)#deny tcp any host x1.28.8 eq 639 SW1(config-ext-nacl)#permit tcp host x.1.28.2 host x.1.28.8 eq bgp SW1(config-ext-nacl)#permit tcp host x.1.28.2 eq bgp host x.1.28.8 SW1(config-ext-nacl)#permit pim host x.1.28.2 host x.1.28.8 … … … SW1(config-ext-nacl)#deny ip any any