STIGQter STIGQter: STIG Summary: Symantec Edge SWG NDM Security Technical Implementation Guide Version: 1 Release: 2 Benchmark Date: 01 Apr 2026:

The Edge SWG must produce audit records containing information to establish when (date and time) the events occurred.

DISA Rule

SV-279255r1170692_rule

Vulnerability Number

V-279255

Group Title

SRG-APP-000096-NDM-000226

Rule Version

SYME-ND-000530

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Select the "Logging" and "Event Logging" areas.
Note: This section sets the "SSL Keyring", which is needed for the "SSL Device Profile".
3. Once the SSL Device Profile has been created properly, scroll down to the "Syslog Loghosts".
4. Click "Add loghost".
5. Click "TLS".
6. Enter the fully qualified domain name of the log server.
7. Enter the port, by default TLS syslog is 6514.
8. Under "SSL Device Profile", select the profile associated with the DOD PKI certificate and key created previously.
9. Click "Add".
10. Scroll down to "Default Notifications". Ensure that "Syslog" is set to "Enabled" and the "Level" is "All Messages".
11. On the syslog server, ensure the server is receiving the messages and troubleshoot any TLS-related communications issues.

Check Contents

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Select the "Logging" and "Event Logging" areas.
3. Scroll down to the "Syslog Loghosts".

If a syslog server hostname/IP address is not configured, this is a finding. If the syslog loghost is configured but is not using the TLS protocol, this is a finding.

4. Scroll down to the "Default Notification" section.

If "Syslog" is not "Enabled" and set to "all messages", this is a finding.

Vulnerability Number

V-279255

Documentable

False

Rule Version

SYME-ND-000530

Severity Override Guidance

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Select the "Logging" and "Event Logging" areas.
3. Scroll down to the "Syslog Loghosts".

If a syslog server hostname/IP address is not configured, this is a finding. If the syslog loghost is configured but is not using the TLS protocol, this is a finding.

4. Scroll down to the "Default Notification" section.

If "Syslog" is not "Enabled" and set to "all messages", this is a finding.

Check Content Reference

M

Target Key

5726