OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco multicast edge switch must be configured to establish boundaries for administratively scoped multicast traffic.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-221134CISC-RT-000810SV-221134r1137912_ruleCCI-001414low
Description
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.
STIGDate
Cisco NX OS Switch RTR Security Technical Implementation Guide2026-03-04

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (17) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AST-04Network Diagrams & Data Flow Diagrams (DFDs)
1.00
AST-04.2Control Applicability Boundary Graphical Representation
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
DCH-01Data Protection
1.00
DCH-19Geographic Location of Data
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
IAC-21Least Privilege
1.00

+7 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-12Audit Record Generation
1.00
CM-7Least Functionality
1.00
SC-5Denial-of-service Protection
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.1.3
1.00
CCI1 mapping
CCI-001414
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-09
1.00
ID.AM-03
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

18 NICE work roles and 10 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-221134r1137912_chk)

Multicast boundary for NX-OS can be established via combination of the border command along with an ACL to filter admin-scoped multicast traffic. Step 1: Verify that the interface at the multicast domain edge has been configured with both an ingress and egress ACL. interface Ethernet2/1 no switchport ip access-group FILTER_TRAFFIC_IN in ip access-group FILTER_TRAFFIC_OUT out ip address 10.1.12.1/24 ip pim sparse-mode ip pim border Note: The command ip pim border enables the interface to be on the border of PIM domain so that no bootstrap, candidate-RP, or Auto-RP messages are sent or received on the interface. Step 2: Verify that the ingress and egress ACLs block the address range for administratively scoped multicast traffic. ip access-list FILTER_TRAFFIC_IN 10 deny ip any 239.0.0.0/8 20 permit tcp any any established … … … 90 deny ip any any log ip access-list FILTER_TRAFFIC_OUT 10 deny ip any 239.0.0.0/8 20 deny ip … … 80 permit ip any any If the switch is not configured to establish boundaries for administratively scoped multicast traffic, this is a finding.

Fix Text (F-22838r409892_fix)

Step 1: Configure an ingress and egress ACL to block administratively scoped multicast traffic. SW1(config)# ip access-list FILTER_TRAFFIC_IN SW1(config-acl)# deny 239.0.0.0/8 SW1(config-acl)# permit tcp any any established SW1(config-acl)# … SW1(config-acl)# deny ip any any log SW1(config-acl)# exit SW1(config)# ip access-list FILTER_TRAFFIC_OUT SW1(config-acl)# deny 239.0.0.0/8 SW1(config-acl)# … SW1(config-acl)# permit ip any any SW1(config-acl)# exit Step 2: Apply the ingress and egress ACL to the applicable interfaces. SW1(config)# int e2/1 SW1(config-if)# ip access-group FILTER_TRAFFIC_IN in SW1(config-if)# ip access-group FILTER_TRAFFIC_OUT out SW1(config-if)# end