Changes to any software components can have significant effects on the overall security of the operating system. This requirement ensures the software has not been tampered with and that it has been provided by a trusted vendor.
Accordingly, patches, service packs, device drivers, or operating system components must be signed with a certificate recognized and approved by the organization.
Verifying the authenticity of the software prior to installation validates the integrity of the patch or upgrade received from a vendor. This ensures the software has not been tampered with and that it has been provided by a trusted vendor. Self-signed certificates are not allowed by this requirement. The operating system should not have to verify the software again. This requirement does not mandate DOD certificates for this purpose; however, the certificate used to verify the software must be from an approved certificate authority (CA).
Check
Confirm AlmaLinux and TuxCare package-signing keys are installed on the system and verify their fingerprints match vendor values.
The keys are stored as "RPM-GPG-KEY-AlmaLinux-9" and "RPM-GPG-KEY-TuxCare" inside the "/etc/pki/rpm-gpg/" directory.
List GPG keys installed on the system using the following command:
$ rpm -q --queryformat "%{SUMMARY}\n" gpg-pubkey
TuxCare (Software Signing Key) <packager@tuxcare.com> public key AlmaLinux OS 9 <packager@almalinux.org> public key
If the AlmaLinux and TuxCare GPG keys are not installed, this is a finding.
List key fingerprints of installed GPG keys using the following commands:
$ gpg -q --keyid-format short --with-fingerprint /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux-9
Using the steps listed in the Check, confirm the newly imported keys show as installed on the system and verify their fingerprints match vendor values.