STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Symantec Edge SWG ALG Security Technical Implementation Guide

V-279187

CAT II (Medium)

In the event of a system failure of the ALG function, the Edge SWG must save diagnostic information, log system messages, and load the most current security policies, rules, and signatures when restarted.

Rule ID

SV-279187r1170651_rule

STIG

Symantec Edge SWG ALG Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001665

Discussion

Failure in a secure state can address safety or security in accordance with the mission needs of the organization. Failure to a secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. Preserving state information helps to facilitate the restart of the ALG application and a return to the operational mode with less disruption. This requirement applies to a failure of the ALG function rather than the device or operating system as a whole, which is addressed in the Network Device Management SRG. Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.

Check Content

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Go to "Logging and Access Logging".
3. Scroll down to "Logs" and click "Edit" on the Main log.

If there is no upload client configured, this is a finding.

Under upload schedule, if the is a schedule for "Periodically" is not selected, then this is a finding.

Fix Text

1. In the Edge SWG Web UI, navigate to the Administration tab.
2. Go to "Logging and Access Logging".
3. Scroll down to "Logs" and click "Edit" on the Main log.
4. Under "Upload Client", select "SCP".
5. Click "Open Settings" and configure the following variables: host, port, full path, username, and password.
6. Click "Apply and Test Upload". If there are connection issues, fix these before continuing.
7. Under "Transmission Parameters", select a signing certificate. This signing certificate must be the certificate used for SSL Proxying issued by the DOD WCF Certificate Authority (CA).
8. Check "Text File".
9. Under "Upload Schedule" select "Periodically".
10. Then, choose 5 seconds between connect attempts.
11. Select the "Daily interval" and select a time that works for the site SCP server.
12. Click "Upload Now" to test if the upload works. If there are connection issues, fix these before continuing.
13. Click "Apply and Save".