From Juniper Router RTR Security Technical Implementation Guide
Part of SRG-NET-000362-RTR-000122
Associated with: CCI-002385
The current multicast paradigm can let any host join any multicast group at any time by sending an IGMP or MLD membership report to the DR. In a Protocol Independent Multicast (PIM) Sparse Mode network, the DR will send a PIM Join message for the group to the RP. Without any form of admission control, this can pose a security risk to the entire multicast domain - specifically the multicast routers along the shared tree from the DR to the RP that must maintain the mroute state information for each group join request. Hence, it is imperative that the DR is configured to limit the number of mroute state information that must be maintained to mitigate the risk of IGMP or MLD flooding.
Review the DR configuration to verify that it is limiting the number of mroute states via IGMP or MLD. protocols { igmp { interface ge-1/0/1.0 { group-limit nnn; } } If the DR is not limiting multicast join requests via IGMP or MLD, this is a finding.
Configure the DR on a global or interface basis to limit the number of mroute states resulting from IGMP or MLD membership reports. [edit protocols igmp] set interface ge-1/0/1.0 group-limit nnn
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer