STIGViewer Support

The Edge SWG using PKI-based user authentication must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279217SYME-00-009400SV-279217r1170674_ruleCCI-004068medium
Description
Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). The intent of this requirement is to require support for a secondary certificate validation method using a locally cached revocation data, such as Certificate Revocation List (CRL), in case access to OCSP (required by CCI-000185) is not available. Based on a risk assessment, an alternate mitigation is to configure the system to deny access when revocation data is unavailable. This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management).
STIGDate
Symantec Edge SWG ALG Security Technical Implementation Guide2025-12-16

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) 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-10.2PKI-Based Authentication
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (59) 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-10Concurrent Session Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
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-3(4)Discretionary Access Control
1.00

+49 more (top 10 by confidence shown)

CCI1 mapping

Details

Check Text (C-279217r1170674_chk)

1. In the Edge SWG Web UI, navigate to the Configuration tab. 2. Navigate to SSL and OCSP. If a responder is not configured, this is a finding. If a responder is configured, but the "Response Cache TTL" is set to "0", this is a finding. If there are any items checked under "Ignore Settings", this is a finding.

Fix Text (F-83670r1170643_fix)

1. In the Edge SWG Web UI, navigate to the Configuration tab. 2. Go to SSL and OCSP. 3. Click "Add a Responder". 4. Under URL either set it to "from certificate" if routing to the DODIN is allowed, or if it is not, click the other items and add the local site's URL. 5. Under "Issuer CCL", select the one that includes all DOD ID CAs. 6. Under the "Response Cache TTL" is set it to either "from OCSP response" or to a value of 1 or more. 7. Ensure there are no Ignore Settings checked or enabled.