Automation Controller must use cryptographic mechanisms to protect the integrity of log tools.

Protecting the integrity of the tools used for logging purposes is a critical step in ensuring the integrity of log data. Log data includes all information (e.g., log records, log settings, and log reports) needed to successfully log information system activity.

It is not uncommon for attackers to replace the log tools or inject code into the existing tools for the purpose of providing the capability to hide or erase system activity from the logs.

To address this risk, log tools must be cryptographically signed in order to provide the capability to identify when the log tools have been modified, manipulated, or replaced. An example is a checksum hash of the file or files.

Automation Controller server log tools must use cryptographic mechanisms to protect the integrity of the tools or allow cryptographic protection mechanisms to be applied to their tools.

As an administrator, log in to each Automation Controller host.

Verify the correct Red Hat RPM signing key is available on each host: rpm -qa gpg-pubkey*

Manually inspect against publicly listed keys on https://www.redhat.com. If the keys do not match, this is a finding.

Import the key if missing: rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

Verify the integrity of installed RPMs necessary for Automation Controller: rpm -Va --nofiles --noconfig 2>/dev/null | grep -v '^$' && echo "FINDING" || echo "PASSED"

If "FINDING" is displayed, investigate the modified files. If modifications are unauthorized, this is a finding.

The administrator must reinstall all Automation Controller hosts and Automation Controller.