Details

If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.

To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized modification.

This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions and limiting log data locations.

Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

This does not apply to audit logs generated on behalf of the device itself (management).

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Configure the BIG-IP Core to protect audit information from unauthorized modification.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_F5_BIG-IP_11-x_Y20M10_STIG.zip

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-9
• CAT|II
• CCI|CCI-000163
• Rule-ID|SV-215750r557356_rule
• STIG-ID|F5BI-LT-000057
• STIG-Legacy|SV-74711
• STIG-Legacy|V-60281
• Vuln-ID|V-215750

Source

• Tenable.com/audits