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

The Edge SWG must be configured to send log data to at least one central log server for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).

DISA Rule

SV-279252r1170685_rule

Vulnerability Number

V-279252

Group Title

SRG-APP-000027-NDM-000209

Rule Version

SYME-ND-000410

Severity

CAT I

CCI(s)

• CCI-001403 - Automatically audit account modification actions.
• CCI-000018 - Automatically audit account creation actions.
• CCI-001404 - Automatically audit account disabling actions.
• CCI-001405 - Automatically audit account removal actions.
• CCI-000172 - Generate audit records for the event types defined in AU-2 c that include the audit record content defined in AU-3.
• CCI-000130 - Ensure that audit records containing information that establishes what type of event occurred.
• CCI-003938 - Automatically generate audit records of the enforcement actions.
• 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-003831 - Alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.

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". Once the SSL Device Profile has been created properly, scroll down to the "Syslog Loghosts".
3. Click "Add loghost".
4. Click "TLS".
5. Enter the fully qualified domain name of the log server.
6. Enter the port, by default TLS syslog is 6514.
7. Under "SSL Device Profile" select the profile associated with the DOD PKI certificate and key created previously.
8. Click "Add".
9. Scroll down to "Default Notifications", ensure "Syslog" is set to "Enabled", and the "Level" is "All Messages".
10. 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, under "Syslog".

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

Vulnerability Number

V-279252

Documentable

False

Rule Version

SYME-ND-000410

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, under "Syslog".

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

Check Content Reference

M

Target Key

5726