OpenControls Logo

STIG Viewer

STIGViewer Support

The RUCKUS ICX switch must authenticate all network-connected endpoint devices before establishing any connection.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-273676RCKS-L2S-000080SV-273676r1111002_ruleCCI-001958medium
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. For distributed architectures (e.g., service-oriented architectures), the decisions regarding the validation of authentication claims may be made by services separate from the services acting on those decisions. In such situations, it is necessary to provide authentication decisions (as opposed to the actual authenticators) to the services that need to act on those decisions. This requirement applies to applications that connect either locally, remotely, or through a network to an endpoint device (including, but not limited to, workstations, printers, servers [outside a datacenter], VoIP phones, and VTC codecs). Gateways and SOA applications are examples of where this requirement would apply. Device authentication is a solution enabling an organization to manage devices. It is an additional layer of authentication ensuring only specific pre-authorized devices can access the system.
STIGDate
RUCKUS ICX Layer 2 Switch Security Technical Implementation Guide2025-06-03

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (5) 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.

IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-04Identification & Authentication for Devices
1.00
IAC-05Identification & Authentication for Third-Party Technology Assets, Applications and/or Services (TAAS)
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (31) 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(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-7Unsuccessful Logon Attempts
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
CM-7(9)Prohibiting The Use of Unauthorized Hardware
1.00
IA-11Re-authentication
1.00

+21 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.5.1
1.00
3.5.2
1.00
CCI1 mapping
CCI-001958
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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.

PR.AA-01
1.00
PR.AA-03
1.00
PR.AA-05
0.50

Who does this work

7 NICE work roles and 5 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-273676r1111002_chk)

Verify if the switch configuration has 802.1x authentication implemented for all access switch ports connecting to LAN outlets (i.e., RJ-45 wall plates) or devices not located in the telecom room, wiring closets, or equipment rooms. MAC Authentication must be configured on those switch ports connected to devices that do not provide an 802.1x supplicant. show running-config authentication auth-default-vlan 100 re-authentication reauth-period 2000 dot1x enable dot1x enable ethernet 1/1/1 to 1/1/3 dot1x max-req 6 dot1x timeout tx-period 60 dot1x timeout quiet-period 30 mac-authentication enable mac-authentication enable ethernet 1/1/18 to 1/1/19 If 802.1x authentication or MAC Authentication is not configured on all access switch ports connecting to LAN outlets or devices not located in the telecom room, wiring closets, or equipment rooms, this is a finding.

Fix Text (F-77672r1110050_fix)

Configure dot1x: 1. Enter global config mode: Router#configure terminal 2. Authentication configuration settings: Router(config)#authentication Router(config-authen)#auth-default-vlan 600 (user preference) Router(config-authen)#re-authentication Router(config-authen)#reauth-period 2000 Router(config-authen)#dot1x enable Router(config-authen)#dot1x enable ethernet 1/1/14 to 1/1/15 Router(config-authen)#dot1x max-req 6 Router(config-authen)#dot1x timeout tx-period 60 Router(config-authen)#dot1x timeout quiet-period 30 Router(config-authen)#mac-authentication enable Router(config-authen)#mac-authentication enable ethernet 1/1/18 to 1/1/19 3. Save: Router#write memory