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 Router RTR Security Technical Implementation Guide

V-217084

CAT III (Low)

The Juniper multicast edge router must be configured to establish boundaries for administratively scoped multicast traffic.

Rule ID

SV-217084r604135_rule

STIG

Juniper Router RTR Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-001414

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 router configuration to verify it is blocking admin-scope multicast traffic (239.0.0.0/8) at the multicast domain edge as shown in the example below:

routing-options {
    …
    …
    …
    multicast {
        scope ADMIN_SCOPE {
            prefix 239.0.0.0/8;
            interface [ ge-1/0/1.0 ge-1/1/1.0 ];
        }
    }
}

If the router is not configured to block admin-scoped multicast traffic at the multicast domain edge, this is a finding.

Fix Text

Configure the router to block admin-scoped multicast traffic at the multicast domain edge as shown in the example below:

[edit routing-options]
set multicast scope ADMINL_SCOPE interface ge-1/0/1.0 prefix 239.0.0.0/8
set multicast scope ADMINL_SCOPE interface ge-1/1/1.0 prefix 239.0.0.0/8