STIGQter: STIG Summary: Juniper EX Series Switches Router Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 24 Jul 2024:

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

DISA Rule

SV-253995r844018_rule

Vulnerability Number

V-253995

Group Title

SRG-NET-000019-RTR-000014

Rule Version

JUEX-RT-000230

Severity

CAT III

CCI(s)

• CCI-001414 - Enforce approved authorizations for controlling the flow of information between connected systems based on organization-defined information flow control policies.

Weight

10

Fix Recommendation

RP routers that are peering with customer PIM-SM routers must implement a PIM import policy to block join messages for reserved and any undesirable multicast groups.

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 import <policy name>

Check Contents

Verify that the RP router is configured to filter PIM register messages.
[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 {
mode sparse;
import <policy name>;
}

Note: Alternative is to verify all designated routers are filtering IGMP Membership Report (a.k.a., join) messages received from hosts.

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 Bogon sources, this is a finding.

Vulnerability Number

V-253995

Documentable

False

Rule Version

JUEX-RT-000230

Severity Override Guidance

Verify that the RP router is configured to filter PIM register messages.
[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 {
mode sparse;
import <policy name>;
}

Note: Alternative is to verify all designated routers are filtering IGMP Membership Report (a.k.a., join) messages received from hosts.

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 Bogon sources, this is a finding.

Check Content Reference

M

Target Key

5479