Details
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).
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Configure the BIG-IP AFM module to produce audit records containing information to establish what type of events occurred.
Navigate to the BIG-IP System manager >> Security >> Event Logs >> Logging Profiles.
Click on ‘Create’.
Name the Profile.
Check the box next to ‘Network Firewall’.
Configure settings to log required information.
Click ‘Finished’.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system F5.
References
- 800-53|AU-3
- CAT|II
- CCI|CCI-000130
- Rule-ID|SV-74353r1_rule
- STIG-ID|F5BI-AF-000039
- Vuln-ID|V-59923