STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Red Hat Enterprise Linux 10 Security Technical Implementation Guide

V-280932

CAT I (High)

RHEL 10 must check the GNU Privacy Guard (GPG) signature of software packages originating from external software repositories before installation.

Rule ID

SV-280932r1197215_rule

STIG

Red Hat Enterprise Linux 10 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-003992

Discussion

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 has been provided by a trusted vendor. All software packages must be signed with a cryptographic key recognized and approved by the organization. Verifying the authenticity of software prior to installation validates the integrity of the software package received from a vendor.

Check Content

Verify RHEL 10 dnf always checks the GPG signature of software packages originating from external software repositories before installation with the following command:

$ sudo grep -w gpgcheck /etc/dnf/dnf.conf
gpgcheck=1

If "gpgcheck" is not set to "1", or if the option is missing or commented out, ask the system administrator how the GPG signatures of software packages are being verified.

If no process to verify GPG signatures has been approved by the organization, this is a finding.

Fix Text

Configure RHEL 10 dnf to always check the GPG signature of software packages originating from external software repositories before installation.

Add or update the following line in the [main] section of the "/etc/dnf/dnf.conf" file:

gpgcheck=1