STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94333SYMP-AG-000600SV-104287r1_ruleCCI-002656medium
Description
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.
STIGDate
Symantec ProxySG ALG Security Technical Implementation Guide2020-03-27

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (9) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
AU-4(1)Transfer to Alternate Storage
1.00
AU-5Response to Audit Logging Process Failures
1.00
SC-7(9)Restrict Threatening Outgoing Communications Traffic
1.00
SI-3Malicious Code Protection
1.00
SI-4(1)System-wide Intrusion Detection System
1.00
SI-4(22)Unauthorized Network Services
1.00
SI-4(5)System-generated Alerts
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Details

Check Text (C-104287r1_chk)

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 (F-100449r1_fix)

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.