V-66139

Discussion

If multicast traffic is forwarded beyond the intended boundary, it is possible that it can be intercepted by unauthorized or unintended personnel. Administrative scoped multicast addresses are locally assigned and are to be used exclusively by the enterprise network or enclave. Administrative scoped multicast traffic must not cross the enclave perimeter in either direction. Restricting multicast traffic makes it more difficult for a malicious user to access sensitive traffic. Admin-Local scope is encouraged for any multicast traffic within a network intended for network management, as well as for control plane traffic that must reach beyond link-local destinations.

Check Content

Review the multicast topology diagram to determine if there are any documented Admin-Local (FFx4::/16), Site-Local (FFx5::/16), or Organization-Local (FFx8::/16) multicast boundaries for IPv6 traffic or any Local-Scope (239.255.0.0/16) boundaries for IPv4 traffic.

Verify the appropriate boundaries are configured on the applicable multicast-enabled interfaces.

If appropriate multicast scope boundaries have not been configured, this is a finding.

[HP] display current-configuration interface GigabitEthernet 0/2
interface GigabitEthernet0/2
 port link-mode route
 description OVERSUBSCRIBE
 ip address 201.6.36.1 255.255.255.0
 multicast boundary 239.255.0.0 16
 ipv6 multicast boundary scope 4
 ipv6 multicast boundary scope 5
 ipv6 multicast boundary scope 8
 ipv6 address 2115:C:24::1/120