OpenControls Logo

STIG Viewer

STIGViewer Support

Symantec ProxySG must produce audit records containing information to establish the source of the events.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94251SYMP-AG-000180SV-104205r1_ruleCCI-000133medium
Description
Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, security personnel need to know the source of the event. In addition to logging where events occur within the network, the audit records must also identify sources of events such as IP addresses, processes, and node or device names. This requirement does not apply to audit logs generated on behalf of the device itself (management).
STIGDate
Symantec ProxySG ALG Security Technical Implementation Guide2020-03-27

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) 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-01Continuous Monitoring
1.00
MON-01.4System Generated Alerts
1.00
MON-03Content of Event Logs
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (47) 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.

AC-16Security and Privacy Attributes
1.00
AC-17(1)Monitoring and Control
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3(3)Mandatory Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-12(3)Changes by Authorized Individuals
1.00
AU-14(1)System Start-up
1.00

+37 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 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.

3.3.1
1.00
3.3.2
1.00
CCI1 mapping
CCI-000133
1.00
NIST CSF 2.00 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.

PR.PS-04
1.00

Who does this work

6 NICE work roles and 5 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-104205r1_chk)

Verify that the ProxySG is configured to log user web traffic for auditing that includes the source of the event. 1. Log on to the Web Management Console. 2. Browse to "Configuration" and click "Access Logging". Verify that "Enable Access Logging" is checked. 3. Browse to "Access Logging", click "General", and note which Default Log is indicated for the HTTP protocol ("main" by default). 4. Click "Formats", select the "Default Log" from step 3, and click "Edit/View". 5. Review the log format string and verify that at least the "c-ip" variable is included. If Access Logging is not enabled and/or the specified log variables are not included, this is a finding.

Fix Text (F-100367r1_fix)

Configure the ProxySG to log user web traffic for auditing that includes the source of the event. 1. Log on to the Web Management Console. 2. Browse to "Configuration" and click "Access Logging". Check "Enable Access Logging" and click "Apply". 3. Browse to "Access Logging", click "General", and note which Default Log is indicated for the HTTP protocol ("main" by default). 4. Click "Formats," select the Default Log from step 3, and click "Edit/View". 5. Edit the log format string to include at least the "c-ip" variable. 6. Click OK >> Apply.