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

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-216623	CISC-RT-000800	SV-216623r531085_rule		Medium

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.

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.

STIG	Date
Cisco IOS Router RTR Security Technical Implementation Guide	2022-09-14

Details

Check Text ( C-17858r287238_chk )
This requirement is not applicable for the DODIN Backbone. Step 1: Verify all interfaces enabled for PIM have a neighbor ACL bound to the interface as shown in the example below. interface GigabitEthernet1/1 ip address 10.1.2.2 255.255.255.0 ip pim neighbor-filter PIM_NEIGHBORS ip pim sparse-mode Step 2: Review the configured ACL for filtering PIM neighbors as shown in the example below. ip access-list standard PIM_NEIGHBORS permit 10.1.2.6 If PIM neighbor ACLs are not bound to all interfaces that have PIM enabled, this is a finding.

Check Text ( C-17858r287238_chk )

This requirement is not applicable for the DODIN Backbone.

Step 1: Verify all interfaces enabled for PIM have a neighbor ACL bound to the interface as shown in the example below.

interface GigabitEthernet1/1
ip address 10.1.2.2 255.255.255.0
ip pim neighbor-filter PIM_NEIGHBORS
ip pim sparse-mode

Step 2: Review the configured ACL for filtering PIM neighbors as shown in the example below.

ip access-list standard PIM_NEIGHBORS
permit 10.1.2.6

If PIM neighbor ACLs are not bound to all interfaces that have PIM enabled, this is a finding.

Fix Text (F-17854r287239_fix)
This requirement is not applicable for the DODIN Backbone. Configure neighbor ACLs to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor ACLs to all PIM enabled interfaces. Step 1: Configure ACL for PIM neighbors R2(config)#ip access-list standard PIM_NEIGHBORS R2(config-std-nacl)#permit 10.1.2.6 R2(config-std-nacl)#exit Step 2: Apply the ACL to all interfaces enabled for PIM R2(config)#int g1/1 R2(config-if)#ip pim neighbor-filter PIM_NEIGHBORS

Fix Text (F-17854r287239_fix)

This requirement is not applicable for the DODIN Backbone.

Configure neighbor ACLs to only accept PIM control plane traffic from documented PIM neighbors. Bind neighbor ACLs to all PIM enabled interfaces.

Step 1: Configure ACL for PIM neighbors

R2(config)#ip access-list standard PIM_NEIGHBORS
R2(config-std-nacl)#permit 10.1.2.6
R2(config-std-nacl)#exit

Step 2: Apply the ACL to all interfaces enabled for PIM

R2(config)#int g1/1
R2(config-if)#ip pim neighbor-filter PIM_NEIGHBORS