STIGViewer Support

The Juniper SRX Services Gateway VPN must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-214688JUSX-VN-000021SV-214688r385519_ruleCCI-000804medium
Description
Lack of authentication and identification enables non-organizational users to gain access to the network or possibly a network element that provides opportunity for intruders to compromise resources within the network infrastructure. This requirement only applies to components where this is specific to the function of the device or has the concept of a non-organizational user.
STIGDate
Juniper SRX Services Gateway VPN Security Technical Implementation Guide2024-12-20

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 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 (39) 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-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-7Unsuccessful Logon Attempts
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00

+29 more (top 10 by confidence shown)

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-214688r385519_chk)

Verify that groups are not used for authentication. [edit] show security access profile <dynamic-profile-name> If LDAP is not configured as the first authentication-order, this is a finding.

Fix Text (F-15887r297652_fix)

Configure the LDAP access profile. The LDAP server must use DoD PKI for authentication of users. [edit] set access profile <VPN-LDAP-PROFILE-NAME> authentication-order ldap set access profile <VPN-LDAP-PROFILE-NAME> address-assignment pool dyn-vpn-pool set access profile <VPN-LDAP-PROFILE-NAME> ldap-options base-distinguished-name CN=Users, DC=firewall, DC=com (Location from where LDAP will start searching for users) set access profile <VPN-LDAP-PROFILE-NAME> ldap-options search search-filter sAMAccountName= set access profile <VPN-LDAP-PROFILE-NAME> ldap-options search admin-search distinguished-name CN=Administrator, CN=Users, DC=firewall, DC=com (User who is authorized to search the ldap tree) set access profile <VPN-LDAP-PROFILE-NAME> ldap-options search admin-search password <Administrator Password> set access profile <VPN-LDAP-PROFILE-NAME> ldap-server <AD Server IP address> port 389/636 set access firewall-authentication pass-through default-profile <VPN-LDAP-PROFILE-NAME> set access firewall-authentication web-authentication default-profile <VPN-LDAP-PROFILE-NAME> Note: To find the user or administrator base DN, use any LDAP browser. On an Internet search engine, search for ldp.exe, which is a very basic LDAP browser. When using LDAP groups to authenticate a user, or a user belonging to a group in the active directory, include the following statement: set access profile <VPN-LDAP-PROFILE-NAME> session-options client-group <group-name> Note: Without the above statement, users are not searched based on the group name or group string. The IP address pool configuration is as follows (the user will be assigned the IP from this pool): set access address-assignment pool dyn-vpn-pool family inet network <IP Network for Dynamic-VPN User> (e.g.. 192.168.100.0/24) set access address-assignment pool dyn-vpn-pool family inet range dyn-vpn-pool-range low <Starting IP address for Dynamic-VPN User> (e.g.. 192.168.100.1) set access address-assignment pool dyn-vpn-pool family inet range dyn-vpn-pool-range high <ending IP address for Dynamic-VPN User> (e.g.. 192.168.100.100) Note: The IP network used for dynamic VPN users should be different from the IP network of the external interface used in the IKE configuration. The access profile is linked to the xauth of the gateway for dynamic VPN. set security ike gateway <VPN-GATEWAY> xauth access-profile <VPN-LDAP-PROFILE-NAME> Under security >> dynamic-vpn, add all the users that are going to use the dynamic VPN. The command is as follows: set security dynamic-vpn clients all user Note: Users who are going to use dynamic VPN. This will be the AD user logon name for each user.