Rule ID
SV-283888r1203913_rule
Version
V1R1
CCIs
If multicast traffic is forwarded beyond the intended boundary, it could 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.
Review the router configuration and verify admin-scope multicast traffic is blocked at the external edge. Use the command below to display the IPv4 filter applied. - show router interface "TO-PE3" detail | match "Ingress Filter" Egress Filter : none Ingress Filter : 10 If the router is not configured to establish boundaries for administratively scoped multicast traffic, this is a finding.
Create an IPv4 filter using the example below: - configure filter ip-filter 10 - config>filter>ip-filter# default-action forward - config>filter>ip-filter# entry 10 create - config>filter>ip-filter>entry$ match dst-ip 239.0.0.0/8 - config>filter>ip-filter>entry$ action drop - config>filter>ip-filter>entry$ exit all Apply an IPv4 filter on the interface using the example below: - configure router interface "TO-PE3" ingress filter ip 10