STIGQter: STIG Summary: Symantec Edge SWG ALG Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 25 Nov 2025:

The Edge SWG must ensure inbound and outbound traffic is monitored for compliance with remote access security policies.

DISA Rule

SV-279177r1170662_rule

Vulnerability Number

V-279177

Group Title

SRG-NET-000061-ALG-000009

Rule Version

SYME-00-004200

Severity

CAT II

CCI(s)

• CCI-000067 - Employ automated mechanisms to monitor remote access methods.
• CCI-000130 - Ensure that audit records containing information that establishes what type of event occurred.
• CCI-000131 - Ensure that audit records containing information that establishes when the event occurred.
• CCI-000132 - Ensure that audit records containing information that establishes where the event occurred.
• CCI-000133 - Ensure that audit records containing information that establishes the source of the event.
• CCI-000134 - Ensure that audit records containing information that establishes the outcome of the event.
• CCI-001487 - Ensure that audit records containing information that establishes the identity of any individuals, subjects, or objects/entities associated with the event.
• CCI-001919 - Provide the capability for organization-defined users or roles to select a user session to record; view; hear; or log the content of a user session under organization-defined circumstances.
• CCI-001851 - Transfer audit logs per organization-defined frequency to a different system, system component, or media than the system or system component conducting the logging.
• CCI-001314 - Reveal error messages only to organization-defined personnel or roles.
• CCI-000172 - Generate audit records for the event types defined in AU-2 c that include the audit record content defined in AU-3.

Weight

10

Fix Recommendation

1. In the Edge SWG Web UI, navigate to the VPM.
2. Select the Web Access Layer.
3. Click the first block or allow rule.
4. Left-click "Track".
5. Click "Set".
6. Click "Add New Object".
7. Click "Event Log".
8. Under "Details" add the following:
$(appliance.name)$(appliance.primary_address)$(c-ip)$(c-port)$(c-uri)$(c-uri-address)$(c-uri-cookie-domain)$(c-uri-extension)$(c-uri-host)$(c-uri-hostname)$(c-uri-path)$(c-uri-pathquery)$(client.address)$(client.certificate.subject)$(client.host)$(client.public_address)$(cs-auth-group)$(cs-categories-policy)$(date)$(user.name)$(user.x509.subject)

9. Under "Category", click "All".
10. Under "Display Options", click "Both".
11. Click "Apply".
12. Repeat these steps for each rule under the Web Access Layer.
13. Click "Apply Policy".

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Go to "Logging and Event Logging".
3. Scroll down to "syslog loghosts".
4. Click "Add Loghost".
5. Select "TLS".
6. Enter the hostname of the syslog server.
7. Enter the port. For TLS, it is normally 6514.
8. Select the SSL Device Profile that will be used. (Note: The SSL device profile must include the CA certificate chain that signed the certificate of the syslog server if it is different from the ones that signed the web server certificate).

Check Contents

1. In the Edge SWG Web UI, navigate to the Visual Policy Manager (VPM).
2. Navigate to "Administration and Event Logging".
3. Scroll down to "Syslog Loghosts".

If there is no Web Access Layer this is a finding.

If there is a Web Access Layer, but the Track is not set or not configured, this is a finding.

If no log hosts are configured, this is a finding.

Vulnerability Number

V-279177

Documentable

False

Rule Version

SYME-00-004200

Severity Override Guidance

1. In the Edge SWG Web UI, navigate to the Visual Policy Manager (VPM).
2. Navigate to "Administration and Event Logging".
3. Scroll down to "Syslog Loghosts".

If there is no Web Access Layer this is a finding.

If there is a Web Access Layer, but the Track is not set or not configured, this is a finding.

If no log hosts are configured, this is a finding.

Check Content Reference

M

Target Key

5725