STIGViewer Support

The Edge SWG providing user authentication intermediary services must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279216SYME-00-009200SV-279216r1170672_ruleCCI-002038medium
Description
Without reauthentication, users may access resources or perform tasks for which they do not have authorization. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances: - When authenticators change. - When roles change. - When security categories of information systems change. - When the execution of privileged functions occurs. - After a fixed period of time. - Periodically. Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation and role changes. This requirement only applies to components for which this is specific to the function of the device or has the concept of user authentication (e.g., VPN or ALG capability). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management). Satisfies: SRG-NET-000337-ALG-000096, SRG-NET-000344-ALG-000098
STIGDate
Symantec Edge SWG ALG Security Technical Implementation Guide2025-12-16

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (6) 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
IAC-14Re-Authentication
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (42) 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-11Device Lock
1.00
AC-11(1)Pattern-hiding Displays
1.00
AC-12Session Termination
1.00
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-3(4)Discretionary Access Control
1.00
AC-4(17)Domain Authentication
1.00

+32 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 (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.

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-279216r1170672_chk)

1. In the Edge SWG Web UI, navigate to the Configuration tab. 2. Go to "Authentication Reams and Domains". 3. Select the "CAC/Certificate" realm. 4. Under "Advanced Setting", click "Show". If the setting "Use the same refresh time for all" is not checked, this is a finding. If it is checked, and the "Surrogate refresh time" is not set to at least "600 seconds", this is a finding.

Fix Text (F-83669r1170640_fix)

1. In the Edge SWG Web UI, navigate to the Configuration tab. 2. Go to "Authentication Reams and Domains". 3. Select the "CAC/Certificate" realm. 4. Under "Advanced Setting", click "Show". 5. Check the setting "Use the same refresh time for all". 6. Under "Surrogate refresh time" set it to at least "600 seconds", but the site policies may require less. 7. Click "Apply and Save".