OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX switch must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273696RCKS-L2S-000300SV-273696r1110998_ruleCCI-004891medium
Description
Separating critical system components and functions from other noncritical system components and functions through separate subnetworks may be necessary to reduce susceptibility to a catastrophic or debilitating breach or compromise that results in system failure. For example, physically separating the command and control function from the in-flight entertainment function through separate subnetworks in a commercial aircraft provides an increased level of assurance in the trustworthiness of critical system functions. Satisfies: SRG-NET-000715-L2S-000120, SRG-NET-000760-L2S-000160
STIGDate
RUCKUS ICX Layer 2 Switch Security Technical Implementation Guide2025-06-03

Related Frameworks

2 mappings across 3 frameworks
SCF0 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.

BCD-10.4Alternate Communications Channels
1.00
CLD-03Cloud Infrastructure Security Subnet
0.50
NET-03.8Separate Subnet for Connecting to Different Security Domains
0.50
NET-06.1Security Management Subnets
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (9) 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-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
CM-6Configuration Settings
1.00
SC-47Alternate Communications Paths
1.00
SC-5(2)Capacity, Bandwidth, and Redundancy
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-8Transmission Confidentiality and Integrity
1.00
CCI2 mappings
CCI-004891
1.00
CCI-004931
1.00

Details

Check Text (C-273696r1110998_chk)

Review the RUCKUS ICX switch configuration. Router# Show Vlans PORT-VLAN 5, Name Organization_A, Priority level0, in single spanning tree domain Untagged Ports: None 2 Tagged Ports: (U1/M1) 4 6 8 10 12 14 Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 10, Name Organization_B, Priority level0, in single spanning tree domain Untagged Ports: None 20 21 22 Tagged Ports: (U1/M1) 1 3 5 7 9 11 Mac-Vlan Ports: None Monitoring: Disabled PORT-VLAN 12, Name IP_Phone, Priority level0, in single spanning tree domain Untagged Ports: None Tagged Ports: (U1/M1) 30 31 32 33 34 35 Mac-Vlan Ports: None Monitoring: Disabled If the RUCKUS ICX switch is not configured to implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions, this is a finding.

Fix Text (F-77692r1110749_fix)

Configure the layer 2 switch to implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. 1. Add appropriate VLAN by name. device# configure terminal Router(config)#vlan 5 Name Organization_A Router(config)#vlan 10 Name Organization_B Router(config)#vlan 10 Name IP_Phone 2. Add untagged Ports for the specific ports to the VLANs as needed. Router(config-vlan-5)#untag ethernet 1/1/2 3. Add tagged ports. Router(config-vlan-5)#tag ethernet 1/1/4 4. Save the configuration. Router(config-vlan-5)#write memory