V-94245

Discussion

Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit record content that may be necessary to satisfy this requirement includes, for example, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked. Associating event types with detected events in the gateway logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured network element. This requirement does not apply to audit logs generated on behalf of the device itself (management).

Check Content

Verify the ProxySG is configured to log user web traffic for auditing that includes the event type.

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 following variables are included:
  cs-method
  cs-protocol
  cs-uri-scheme
  cs-uri-path
  cs-uri-query
  sc-status
  s-action

If Access Logging is not enabled and/or the specified log variables are not included, this is a finding.