STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper EX Series Switches Router Security Technical Implementation Guide

V-253994

CAT III (Low)

The Juniper multicast Rendezvous Point (RP) router must be configured to filter Protocol Independent Multicast (PIM) Register messages received from the Designated Router (DR) for any undesirable multicast groups and sources.

Rule ID

SV-253994r844015_rule

STIG

Juniper EX Series Switches Router Security Technical Implementation Guide

Version

V2R1

CCIs

CCI-001414

Discussion

Real-time multicast traffic can entail multiple large flows of data. An attacker can flood a network segment with multicast packets, over-using the available bandwidth and thereby creating a denial-of-service (DoS) condition. Hence, it is imperative that register messages are accepted only for authorized multicast groups and sources.

Check Content

Verify that the RP router is configured to filter PIM register messages from unauthorized multicast groups and sources.
[edit policy-options]
policy-statement <name> {
    term filter_groups {
        from {
            route-filter <multicast address>/<mask> orlonger;
            route-filter <multicast address>/<mask> exact;
            <additional groups to filter>
        }
        then reject;
    }
    term filter_sources {
        from {
            source-address-filter <source host address>/32 exact;
            source-address-filter <source subnet address>/<mask> orlonger;
            <additional source addresses to filter>
        }
        then reject;
    }
    term accept_others {
        then accept;
    }
}

[edit protocols pim]
rp {
    rp-register-policy <policy name>;
} 

If the RP router peering with PIM-SM routers is not configured with a PIM import policy to block registration messages for any undesirable multicast groups and sources, this is a finding.

Fix Text

Configure the RP router to filter PIM register messages received from a multicast DR for any undesirable multicast groups or sources.

set policy-options policy-statement <name> term filter_groups from route-filter <multicast address>/<mask> <match criterion>
set policy-options policy-statement <name> term filter_groups from route-filter <additional multicast address>/<mask> <match criterion>
set policy-options policy-statement <name> term filter_groups then reject

set policy-options policy-statement <name> term filter_source from source-address-filter <source address>/<mask> <match criterion>
set policy-options policy-statement <name> term filter_source from source-address-filter <additional source address>/<mask> <match criterion>
set policy-options policy-statement <name> term filter_source then reject

set policy-options policy-statement <name> term accept_others then accept

set protocols pim rp rp-register-policy <policy name>