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 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Symantec ProxySG ALG Security Technical Implementation Guide

V-94333

CAT II (Medium)

Symantec ProxySG providing content filtering must be configured to integrate with a system-wide intrusion detection system.

Rule ID

SV-104287r1_rule

STIG

Symantec ProxySG ALG Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002656

Discussion

Without coordinated reporting between separate devices, it is not possible to identify the true scale and possible target of an attack. Integration of the ALG with a system-wide intrusion detection system supports continuous monitoring and incident response programs. This requirement applies to monitoring at internal boundaries using TLS gateways, web content filters, email gateways, and other types of ALGs. ALGs can work as part of the network monitoring capabilities to off-load inspection functions from the external boundary IDPS by performing more granular content inspection of protocols at the upper layers of the OSI reference model.

Check Content

Verify that the ProxySG is configured to log to an intrusion detection system.

1. Log on to the Web Management Console.
2. Browse to "Configuration" and click "Access Logging. Verify that "Enable Access Logging" is checked.
3. Click Logs >> Upload Client and verify that the Client Type parameters are set to send logs to the intrusion detection system.
4. Click Policy >> Visual Policy Manager >> Launch.

If Symantec ProxySG providing content filtering is not be configured to integrate with a system-wide intrusion detection system, this is a finding.

Fix Text

Configure the ProxySG to log to an intrusion detection system.

1. Log on to the Web Management Console.
2. Browse to "Configuration" and click "Access Logging. Check the "Enable Access Logging" option.
3. Click Logs >> Upload Client and ensure that the Client Type parameters are set to send logs to the intrusion detection system.