The container platform must use cryptographic mechanisms to protect the integrity of audit tools.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-233142 | SRG-APP-000290 | SRG-APP-000290-CTR-000670 | SV-233142r961206_rule | 2024-12-05 | 2 |
Description |
---|
Protecting the integrity of the tools used for auditing purposes is a critical step to ensuring the integrity of audit data. Audit data includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. Audit tools include, but are not limited to, vendor provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. It is common for attackers to replace the audit tools or inject code into the existing tools with the purpose of providing the capability to hide or erase system activity from the audit logs. To address this risk, audit tools must be cryptographically signed in order to provide the capability to identify when the audit tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files. |
ℹ️ Check |
---|
Review the container platform configuration to determine if the integrity of the audit tools is protected using cryptographic mechanisms. If audit tools are not protected through cryptographic mechanisms, this is a finding. |
✔️ Fix |
---|
Configure the container platform to use cryptographic mechanisms to protect the integrity of audit tools. |