STIGViewer Support

AlmaLinux OS 9 must check the GPG signature of repository metadata before package installation.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-269166ALMA-09-009920SV-269166r1050048_ruleCCI-003992high
Description
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 disallowed 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).
STIGDate
Cloud Linux AlmaLinux OS 9 Security Technical Implementation Guide2026-02-27

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.2Signed Components
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (8) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-2(10)Shared and Group Account Credential Change
1.00
CM-14Signed Components
1.00
CM-5(3)Signed Components
1.00
CM-7(5)Authorized Software — Allow-by-exception
1.00
IA-2(5)Individual Authentication with Group Authentication
1.00
SC-23Session Authenticity
1.00
SC-3Security Function Isolation
1.00
SI-2Flaw Remediation
1.00
CCI1 mapping

Details

Check Text (C-269166r1050048_chk)

Verify that dnf always checks the GPG signature of repository metadata: $ grep repo_gpgcheck /etc/dnf/dnf.conf /etc/yum.repos.d/*.repo repo_gpgcheck=1 If "repo_gpgcheck" is not set to "1" in the global "/etc/dnf/dnf.conf" file, or if the option is missing or commented out, this is a finding. If "repo_gpgcheck" is set to "0" in any of the "/etc/yum.repos.d/*.repo" files and the information system security officer (ISSO) lacks a documented requirement, this is a finding. Note: Not all repositories support this feature.

Fix Text (F-73098r1047875_fix)

Configure dnf to always check the GPG signature of repository metadata. Add or update the following line in the [main] section of the /etc/dnf/dnf.conf file: repo_gpgcheck=1 Remove any instances of "repo_gpgcheck=0" from any "/etc/yum.repos.d/*.repo" files.