STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-253949JUEX-L2-000020SV-253949r843880_ruleCCI-000778high
Description
Controlling LAN access via 802.1x authentication can assist in preventing a malicious user from connecting an unauthorized PC to an access interface to inject or receive data from the network without detection. 802.1x includes Static MAC Bypass and MAC RADIUS for those devices that do not offer a supplicant.
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 (15) 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
AU-10(1)Association of Identities
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
IA-3Device Identification and Authentication
1.00
IA-3(1)Cryptographic Bidirectional Authentication
1.00
IA-5(1)Password-based Authentication
1.00
SC-20Secure Name/Address Resolution Service (Authoritative Source)
1.00

+5 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-253949r843880_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 that the RADIUS server(s) are configured. RADIUS servers can be configured globally at [edit access radius-server] or defined for each group. [edit 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>; } --or-- radius-server { <RADIUS IPv4 or IPv6 address> secret "PSK"; ## SECRET-DATA } } Verify 802.1x or MAC RADIUS is configured on all host-facing access interfaces when RADIUS is available as shown in the following example: [edit protocols dot1x] authenticator { authentication-profile-name dot1x_radius; interface { ge-0/0/0.0 { <<< Connected device with 802.1x supplicant supplicant single-secure; } ge-0/0/1.0 { <<< Connected device with 802.1x supplicant and interface support for MAC RADIUS supplicant multiple; mac-radius; } ge-0/0/2.0 { <<< Connected device without 802.1x supplicant mac-radius { restrict; } } } } Note: Junos simultaneously supports both 802.1x and MAC RADIUS on the same access interface. To prevent 802.1x and have the interface use only MAC RADIUS, configure the "restrict" qualifier. If RADIUS is unavailable or not configured: [edit protocols] dot1x { authenticator { static { <MAC address>/48 { vlan-assignment <vlan name>; interface <interface name>.<logical unit>; } } } } If the switch does not uniquely identify all network-connected endpoint devices before establishing any connection for 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-57352r843879_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. Configure RADIUS if available: set access radius-server <RADIUS IPv4 or IPv6 address> secret "<PSK>" set access profile dot1x_radius radius authentication-server <RADIUS IPv4 or IPv6 address> -or- set access profile dot1x_radius radius-server <RADIUS IPv4 or IPv6 address> secret "<PSK>" set access profile dot1x_radius authentication-order radius To configure 802.1x on an access interface: set protocols dot1x authenticator authentication-profile-name dot1x_radius set protocols dot1x authenticator interface <name>.<logical unit> supplicant single-secure --or-- set protocols dot1x authenticator interface <name>.<logical unit> supplicant multiple --or-- set protocols dot1x authenticator interface <name>.<logical unit> supplicant multiple set protocols dot1x authenticator interface <name>.<logical unit> mac-radius set protocols dot1x authenticator interface <name>.<logical unit> mac-radius restrict Note: Configure the "restrict" keyword if the connected device does not support a supplicant. Although a non 802.1x aware client will use MAC RADIUS if configured, without the "restrict" keyword 802.1x authentication is attempted before attempting MAC RADIUS, which increases the time the device must wait before gaining network access. To configure Static MAC Bypass: set protocols dot1x authenticator static <MAC address>/48 vlan-assignment <vlan name> set protocols dot1x authenticator static <MAC address>/48 interface <interface name>.<logical unit>