Symantec ProxySG providing content filtering must send an alert to, at a minimum, the ISSO and ISSM when detection events occur.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-94345 | SYMP-AG-000660 | SV-104299r1_rule | CCI-002664 | medium |
| Description | ||||
| Without an alert, security personnel may be unaware of major detection incidents that require immediate action, and this delay may result in the loss or compromise of information. Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema. These systems must generate an alert when detection events from real-time monitoring occur. Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The ALG must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel. | ||||
| STIG | Date | |||
| Symantec ProxySG ALG Security Technical Implementation Guide | 2020-03-27 | |||
Related Frameworks
1 mapping across 4 frameworks
Related 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.
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (7) 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.
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2our copyintersects(normalised)DISA STIG Benchmark (XCCDF)V1R3our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R2intersects(normalised)DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-002664
1.00
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
NIST CSF 2.00 mappings
No source states a mapping between these directly.
Also reachable in 4 hops (2) 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.
DE.CM-01
1.00
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
- NIST OLIR Informative ReferenceOLIR 153 (2025-04-07)intersects(normalised)SCF Focal Document mapping (catalog)SCF 2026.2 focalintersects(normalised)
PR.PS-04
1.00
- DISA STIG Benchmark (XCCDF)V1R3intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
- NIST OLIR Informative ReferenceOLIR 153 (2025-04-07)intersects(normalised)SCF Focal Document mapping (catalog)SCF 2026.2 focalintersects(normalised)
Details
Check Text (C-104299r1_chk)
Verify that the ProxySG is configured to generate alerts for access attempts to unauthorized websites and/or services.
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 Policy >> Visual Policy Manager >> Launch.
4. For each Web Access Layer, verify that each rule has a value of "Email" in the "Track" column.
5. Right-click the "Track" field for each rule and select "Edit".
6. Click "Configure Custom Recipients Lists".
7. Click any recipient email list in the left side panel and verify that the ISSO's email address is listed in the "List Members" panel.
If Symantec ProxySG providing content filtering does not send an alert to, at a minimum, the ISSO and ISSM when detection events occur, this is a finding.
Fix Text (F-100461r1_fix)
Configure the ProxySG to generate alerts for access attempts to unauthorized websites and/or services.
Email may be used to send alerts directly to the ISSO/ISSM. However, use caution and be selective when choosing which Web Access rules on which to enable email notification.
1. Log on to the Web Management Console.
2. Browse to "Configuration" and click "Access Logging". Check the "Enable Access Logging" option and click "Apply".
3. Click Policy >> Visual Policy Manager >> Launch.
4. For each Web Access Layer, right-click the "Track" column for each rule and select "Set". Click "New" and select "Email".
5. Select "Custom Recipients" and click "Configure Custom Recipients Lists".
6. Click "New," provide a name for the list, and enter the ISSO and ISSM email addresses in the "List Members" field.
7. Click "OK" and click "OK" again. Create message text and click "OK".
8. Click "OK" and click "OK" again. Select File >> Install Policy on SG Appliance.