SV-279255r1170692_rule
V-279255
SRG-APP-000096-NDM-000226
SYME-ND-000530
CAT II
10
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.
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.
V-279255
False
SYME-ND-000530
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.
M
5726