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).

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
high	V-279252	SRG-APP-000027-NDM-000209	SYME-ND-000410	SV-279252r1170685_rule	2025-12-18	1

Description
Before continuing, the site must follow the configuration steps under SYME-ND-000800. The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can be used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, are important in showing whether someone is an internal employee or an outside threat. Satisfies: SRG-APP-000027-NDM-000209, SRG-APP-000026-NDM-000208, SRG-APP-000028-NDM-000210, SRG-APP-000029-NDM-000211, SRG-APP-000091-NDM-000223, SRG-APP-000095-NDM-000225, SRG-APP-000381-NDM-000305, SRG-APP-000515-NDM-000325, SRG-APP-000516-NDM-000350, SRG-APP-000795-NDM-000130

Description

Before continuing, the site must follow the configuration steps under SYME-ND-000800. The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can be used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, are important in showing whether someone is an internal employee or an outside threat. Satisfies: SRG-APP-000027-NDM-000209, SRG-APP-000026-NDM-000208, SRG-APP-000028-NDM-000210, SRG-APP-000029-NDM-000211, SRG-APP-000091-NDM-000223, SRG-APP-000095-NDM-000225, SRG-APP-000381-NDM-000305, SRG-APP-000515-NDM-000325, SRG-APP-000516-NDM-000350, SRG-APP-000795-NDM-000130

ℹ️ Check
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

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.

✔️ Fix
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.

✔️ Fix

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.