Rule ID
SV-288211r1252771_rule
Version
V1R0.1
CCIs
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an attacker could potentially use to their advantage. To ensure the veracity of audit data, the information system and/or the application must protect audit information from any and all unauthorized access. This includes read, write, and copy access. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Commonly employed methods for protecting audit information include least privilege permissions as well as restricting the location and number of log file repositories. Additionally, applications with user interfaces to audit records must not allow for the unfettered manipulation of or access to those records via the application. If the application provides access to the audit data, the application becomes accountable for ensuring audit information is protected from unauthorized access. Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
Review the application documentation and deployed configuration to determine whether the application's auditing mechanism protects audit information from any type of unauthorized read access. If the application's auditing mechanism does not protect audit information from any type of unauthorized read access, this is a finding.
Navigate to the auditing function configuration within the application. Configure the application's auditing mechanism to protect audit information from any type of unauthorized read access.