STIGViewer Support

The Juniper EX switch must be configured to authenticate all network-connected endpoint devices before establishing any connection.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-253954JUEX-L2-000070SV-253954r1082969_ruleCCI-001958medium
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. 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. 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. For Juniper EX, configure 802.1 x authentication on all host-facing access interfaces. To authenticate those devices that do not support an 802.1x supplicant, Static MAC Bypass or MAC RADIUS must be configured. Junos supports three supplicant types: single-secure (authenticate and permit only a single device), multiple (separately authenticate and permit multiple devices), and single (authenticate the first supplicant and permit all others). The authentication order must be appropriate for the target environment. Authentication must be configured on all access interfaces connecting to LAN outlets or devices not located in the telecom room, wiring closets, or equipment rooms.
STIGDate
Juniper EX Series Switches Layer 2 Switch Security Technical Implementation Guide2026-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
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.

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-253954r1082969_chk)

Verify the switch configuration has 802.1x authentication implemented for all access interfaces connecting to LAN outlets (i.e., RJ-45 wall plates) or devices not located in the telecom room, wiring closets, or equipment rooms. Static MAC Bypass or MAC RADIUS must be configured on access interfaces connected to devices that do not support an 802.1x supplicant. Junos supports three supplicant types: single-secure (authenticate and permit only a single device), multiple (separately authenticate and permit multiple devices), and single (authenticate the first supplicant and permit all others). Verify the available RADIUS server(s) are configured. RADIUS servers can be configured globally at [edit access radius-server] or defined for each group. user@host> show configuration access radius-server { <RADIUS IPv4 or IPv6 address> secret "PSK"; ## SECRET-DATA } profile dot1x_radius { authentication-order radius; radius { authentication-server <RADIUS IPv4 or IPv6 address>; <<< Must be defined if using global RADIUS server. Optional if RADIUS is defined specifically for the profile. } radius-server { <RADIUS IPv4 or IPv6 address> secret "PSK"; ## SECRET-DATA <<< Must be defined if not using global RADIUS server. Takes precedence if both profile and global RADIUS is configured. } } Verify 802.1x or MAC RADIUS is configured on all host-facing access interfaces when RADIUS is available as shown in the following example. The default authentication order is dot1x, mac-radius, and captive-portal. This order is applied to all interfaces without the authentication order directive configured (int-01 shown below). For interfaces with connected devices that do not support 802.1x (int-02 below), it may be necessary to change the authentication order because the device authentication attempt may timeout before the switch fails over from dot1x to mac-radius. When restricting to mac-radius authentication only (int-03 below), the authentication order cannot be set. user@host> show configuration protocols dot1x authenticator { authentication-profile-name dot1x_radius; interface { <int-01 name> { <<< Connected device with 802.1x supplicant supplicant single-secure; } <int-02 name> { <<< Connected device with 802.1x supplicant and interface support for MAC RADIUS, MAC RADIUS authentication preferred authentication-order [ mac-radius dot1x captive-portal ]; supplicant multiple; mac-radius; } <int-03 name> { <<< Connected device without 802.1x supplicant mac-radius { restrict; } } } } Note: The interface names, supplicant type, MAC RADIUS support, and authentication order must be appropriate for the target environment. If RADIUS is unavailable or not configured: user@host> show configuration protocols dot1x authenticator { static { <MAC address>/48 { vlan-assignment <vlan name>; interface <interface name>.<logical unit>; } } } If 802.1x authentication, Static MAC Bypass, or MAC RADIUS is not configured on all access interfaces connecting to LAN outlets or devices not located in the telecom room, wiring closets, or equipment rooms, this is a finding.

Fix Text (F-57357r1082968_fix)

Configure 802.1 x authentication on all host-facing access interfaces. To authenticate those devices that do not support an 802.1x supplicant, Static MAC Bypass or MAC RADIUS must be configured. The authentication order must be appropriate for the target environment. Configure RADIUS if available: user@host> configure user@host# set access radius-server <RADIUS IPv4 or IPv6 address (global)> secret "<PSK>" user@host# set access profile dot1x_radius authentication-order radius user@host# set access profile dot1x_radius radius authentication-server <RADIUS IPv4 or IPv6 address (global)> -or- user@host# set access profile dot1x_radius radius-server <RADIUS IPv4 or IPv6 address> secret "<PSK>" To configure 802.1x on an access interface using the default authentication order: user@host# set protocols dot1x authenticator authentication-profile-name dot1x_radius user@host# set protocols dot1x authenticator interface <int-01> supplicant single-secure To configure 802.1x and MAC RADIUS on an access interface and prefer MAC RADIUS in the authentication order: user@host# set protocols dot1x authenticator interface <int-02> authentication-order mac-radius user@host# set protocols dot1x authenticator interface <int-02> authentication-order dot1x user@host# set protocols dot1x authenticator interface <int-02> authentication-order captive-portal user@host# set protocols dot1x authenticator interface <int-02> supplicant multiple user@host# set protocols dot1x authenticator interface <int-02> mac-radius To configure only MAC RADIUS on an access interface for devices that do not support 802.1x (authentication order cannot be set): user@host# set protocols dot1x authenticator interface <int-03> mac-radius restrict To configure Static MAC Bypass: user@host# set protocols dot1x authenticator static <MAC address>/48 vlan-assignment <vlan name> user@host# set protocols dot1x authenticator static <MAC address>/48 interface <interface name>.<logical unit>