Libgcrypt cryptography module for AlmaLinux 9

Certificate

Approved Algorithms (47)

Security Levels (Table 1)

Derived Review-Risk Graph (review prompts, not findings)

flowchart LR
  %% Deterministic review-risk graph for Libgcrypt cryptography module for AlmaLinux 9
  %% Review prompts and evidence gaps, NOT vulnerability findings.
  subgraph CMVP["CMVP-disclosed clues"]
    C2["[low] Firmware update / recovery<br/>/ rollback (referenced in<br/>text)<br/><i>update<br/>Recovery</i>"]
    C3["[high] Unauthenticated /<br/>self-test / status service<br/>surface<br/><i>Symmetric encryption and decryption<br/>Symmetric encryption and decryption with AES XTS…<br/>Show status</i>"]
    C5["[low] Protocol / secure-channel<br/>references (may be KDF<br/>names, not a live channel)<br/><i>TLS<br/>HTTPS<br/>no library/version identified</i>"]
    C6["[low] Operating system / runtime<br/>referenced (boundary<br/>membership not asserted)<br/><i>operating system<br/>linux<br/>kernel</i>"]
  end
  subgraph Inference["Derived inference"]
    I2["Possible only, trusted<br/>code is reachable through<br/>update and recovery paths."]
    I3["Some services may process<br/>input before, or without,<br/>operator authentication."]
    I5["Possible only, a protocol<br/>is referenced, but whether<br/>it is a live channel or<br/>only a KDF/algorithm name<br/>is unconfirmed."]
    I6["Possible only, a<br/>runtime/OS is referenced,<br/>but its membership in the<br/>cryptographic boundary is<br/>not established."]
  end
  subgraph Risk["Reviewer question"]
    R2["Are update images<br/>authenticated before<br/>parsing, and are<br/>downgrade/rollback paths<br/>constrained?"]
    R3["Can unauthenticated<br/>services leak state,<br/>consume resources, or<br/>transition security state?"]
    R5["If a live TLS/SSH/IKE<br/>channel exists, could<br/>library CVEs apply, or is<br/>this only a<br/>KDF/documentation name?"]
    R6["If the OS/runtime is<br/>in-boundary, could its<br/>CVEs be hidden by<br/>firmware-only versioning?"]
  end
  subgraph Evidence["Evidence needed to close"]
    E2["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>update image format ·<br/>signature-before-parse<br/>proof · anti-rollback /<br/>downgrade policy"]
    E3["pre-auth reachability<br/>matrix · rate limits and<br/>output redaction ·<br/>abuse-case tests"]
    E5["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>library identity and<br/>version ·<br/>certificate-validation<br/>behaviour · protocol-CVE<br/>disposition"]
    E6["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>runtime identity and<br/>config · kernel/runtime<br/>hardening profile ·<br/>patch/backport manifest"]
  end
  C2 --> I2 --> R2 --> E2
  C3 --> I3 --> R3 --> E3
  C5 --> I5 --> R5 --> E5
  C6 --> I6 --> R6 --> E6
  classDef clue fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef infer fill:#fff7e6,stroke:#b98500,color:#6b4e00;
  classDef risk fill:#fbe9e9,stroke:#b02a2a,color:#7a1f1f;
  classDef evidence fill:#e6f4ea,stroke:#1e7d34,color:#14532d;
  class C2,C3,C5,C6 clue;
  class I2,I3,I5,I6 infer;
  class R2,R3,R5,R6 risk;
  class E2,E3,E5,E6 evidence;

flowchart LR
  %% Deterministic clue tier for Libgcrypt cryptography module for AlmaLinux 9
  %% confidence: high = structured record field; medium = structured but soft; low (dashed) = bare keyword hit, context unverified
  subgraph CMVP["CMVP-disclosed clues (deterministic)"]
    C2["[low] Firmware update / recovery / rollback (referenced in text)<br/><i>update<br/>Recovery</i><br/>src: text:keyword"]
    C3["[high] Unauthenticated / self-test / status service surface<br/><i>Symmetric encryption and decryption<br/>Symmetric encryption and decryption with AES XTS…<br/>Show status</i><br/>src: securityPolicy.services"]
    C5["[low] Protocol / secure-channel references (may be KDF names, not a live channel)<br/><i>TLS<br/>HTTPS<br/>no library/version identified</i><br/>src: text:keyword"]
    C6["[low] Operating system / runtime referenced (boundary membership not asserted)<br/><i>operating system<br/>linux<br/>kernel</i><br/>src: text:keyword"]
  end
  classDef clueHigh fill:#eef3f9,stroke:#2f6fb0,stroke-width:2px,color:#1f3a5f;
  classDef clueMedium fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef clueLow fill:#f7f7f7,stroke:#999,stroke-dasharray:4 4,color:#444;
  class C2,C5,C6 clueLow;
  class C3 clueHigh;

Security Policy, page by page

Cloudlinux Inc., TuxCare division Libgcrypt cryptography module for AlmaLinux 9 Prepared by: atsec information security corporation

Libgcrypt cryptography module for AlmaLinux 9 Austin, TX 78759 Document version: 1.2 www.atsec.com Last update: 2026-13-04 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table of Contents © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 List of Tables List of Figures © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

This document is the non-proprietary FIPS 140-3 Security Policy for version 1.10.0-9a1db72d64086a2f of the Libgcrypt cryptography module for AlmaLinux 9. It contains the security rules under which the module must operate and describes how this module meets the requirements as specified in FIPS PUB 140-3 (Federal Information Processing Standards Publication 140-3) for an overall Security Level 1 module.

This Security Policy describes the features and design of the module named Libgcrypt cryptography module for AlmaLinux 9 using the terminology contained in the FIPS 140-3 specification. The FIPS 140-3 Security Requirements for Cryptographic Module specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information. The NIST/CCCS Cryptographic Module Validation Program (CMVP) validates cryptographic module to FIPS 140-3. Validated products are accepted by the Federal agencies of both the USA and Canada for the protection of sensitive or designated information. including this notice. Other documentation is proprietary to their authors. In preparing the Security Policy document, the laboratory formatted the vendor-supplied documentation for consolidation without altering the technical statements therein contained. The further refining of the Security Policy document was conducted iteratively throughout the conformance testing, wherein the Security Policy was submitted to the vendor, who would then edit, modify, and add technical contents. The vendor would also © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 supply additional documentation, which the laboratory formatted into the existing Security Policy, and resubmitted to the vendor for their final editing. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

Purpose and Use: The Libgcrypt cryptography module for AlmaLinux 9 (hereafter referred to as “the module”) is a software library implementing general purpose cryptographic algorithms. The module provides cryptographic services to applications running in the user space of the underlying operating system through an application program interface (API). Module Type: Software Module Embodiment: Multi-Chip Standalone Cryptographic Boundary: The module consists of the shared library file (i.e. libgcrypt.so.20.4.0) which constitutes the cryptographic boundary. The block diagram in Figure 1 shows the cryptographic boundary of the module, its interfaces with the operational environment and the flow of information between the module and operator. Tested Operational Environment’s Physical Perimeter (TOEPP): The TOEPP is the general-purpose computer on which the module is installed. Figure 1: Block Diagram © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

Tested Module Identification

• Hardware: N/A for this module. Tested Module Identification
• Software, Firmware, Hybrid (Executable Code Sets): 1.10.0N/A Table 2: Tested Module Identification
• Software, Firmware, Hybrid (Executable Code Sets) Tested Module Identification
• Hybrid Disjoint Hardware: N/A for this module. Tested Operational Environments - Software, Firmware, Hybrid: 9.2 N/A 1.10.09a1db72d64086a2f 9.2 N/A 1.10.09a1db72d64086a2f N/A 1.10.09a1db72d64086a2f N/A 1.10.09a1db72d64086a2f Table 3: Tested Operational Environments - Software, Firmware, Hybrid Vendor-Affirmed Operational Environments - Software, Firmware, Hybrid: Table 4: Vendor-Affirmed Operational Environments - Software, Firmware, Hybrid CMVP makes no statement as to the correct operation of the module or the security strengths of the generated keys when so ported if the specific operational environment is not listed on the validation certificate.

The module does not claim any excluded components. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

Modes List and Description: Table 5: Modes List and Description NonApproved Mode Change Instructions and Status: When the module starts up successfully, after passing all the pre-operational self-test and the cryptographic algorithms self-tests (CASTs), the module is operating in the approved mode of operation by default and can only be transitioned into the non-approved mode by calling one of the non-approved services listed in the NonApproved Services table. The module will transition back to approved mode when approved service is called. Section 4 provides details on the service indicator implemented by the module. The service indicator identifies The module does not implement a degraded mode of operation.

Approved Algorithms: © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 2.0 2.0 2.0 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 2.0 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2256 HMAC-SHA2256 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMAC-SHA2256 HMAC-SHA2256 HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2384 HMAC-SHA2384 HMAC-SHA2384 HMAC-SHA2384 HMAC-SHA2512 HMAC-SHA2512 HMAC-SHA2512 HMAC-SHA2512 HMAC-SHA2512 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMAC-SHA3224 HMAC-SHA3224 HMAC-SHA3224 HMAC-SHA3256 HMAC-SHA3256 HMAC-SHA3256 HMAC-SHA3384 HMAC-SHA3384 HMAC-SHA3384 HMAC-SHA3512 HMAC-SHA3512 HMAC-SHA3512 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 6: Approved Algorithms The above table lists all approved cryptographic algorithms of the module, including specific key lengths employed for approved services, and implemented modes or methods of operation of the algorithms. Vendor-Affirmed Algorithms: Table 7: Vendor-Affirmed Algorithms N/A Non-Approved, Allowed Algorithms: N/A for this module. The module does not implement non-approved algorithms that are allowed in the approved mode of operation. Non-Approved, Allowed Algorithms with No Security Claimed: N/A for this module. The module does not implement non-approved algorithms that are allowed in the approved mode of operation with no security claimed. Non-Approved, Not Allowed Algorithms: Table 8: Non-Approved, Not Allowed Algorithms The table above lists all non-approved cryptographic algorithms of the module employed by the non-approved services.

© 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 AsymKeyPairKeyVer () © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 () © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 9: Security Function Implementations

AES XTS The AES algorithm in XTS mode can be only used for the cryptographic protection of data on storage devices, as specified in [SP800-38E]. The length of a single data unit encrypted with the XTS-AES shall not exceed 2²⁰ AES blocks, that is 16MB of data. To meet the requirement stated in IG C.I, the module implements a check that ensures, before performing any cryptographic operation, that the two AES keys used in AES XTS mode are not identical. The AES-XTS mode shall only be used for the cryptographic protection of data on storage devices. The AESXTS shall not be used for other purposes, such as the encryption of data in transit. Key derivation using SP800-132 PBKDF The module provides password-based key derivation (PBKDF), compliant with SP800-132. The module supports option 1a from Section 5.4 of [SP800-132], in which the Master Key (MK) or a segment of it is used directly as the Data Protection Key (DPK). In accordance with [SP800-132] and FIPS 140-3 IG D.N, the following requirements shall be met.

• Derived keys shall only be used in storage applications. The Master Key (MK) shall not be used for other purposes. The module accepts length of the MK or DPK of 112 bits or more.
• A portion of the salt, with a length of at least 128 bits, shall be generated randomly using the SP80090A DRBG.
• The iteration count shall be selected as large as possible, as long as the time required to generate the key using the entered password is acceptable for the users. The minimum value accepted by the module is 1000.
• Passwords or passphrases, used as an input for the PBKDF, shall not be used as cryptographic keys.
• The minimum length of the password or passphrase accepted by the module is 8 characters. The probability of guessing the value, assuming a worst-case scenario of all digits, is estimated to be at most © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 10-8. Combined with the minimum iteration count as described below, this provides an acceptable trade-off between user experience and security against brute-force attacks. The calling application shall also observe the rest of the requirements and recommendations specified in [SP800-132]. SHA-1 Use SHA-1 is only approved when used in approved modes for message digest, HMAC, KDF (PBKDF), and DRBG. The use of SHA-1 for digital signature generation (e.g., ECDSA, RSA) or verification is non-approved.

Table 10: Entropy Certificates 3.4.0 NonPhysical Table 11: Entropy Sources The Module provides an SP800-90A-compliant Deterministic Random Bit Generator (DRBG) for creation of key components of asymmetric keys, and random number generation. The seeding (and automatic reseeding) of the DRBG is done with getrandom(). The DRBG supports the Hash_DRBG, HMAC_DRBG and CTR_DRBG mechanisms. The DRBG is initialized during module initialization; the module loads by default the DRBG using the HMAC_DRBG mechanism with SHA-256 and without prediction resistance. A different DRBG mechanism can be chosen by invoking the gcry_control(GCRYCTL_DRBG_REINIT) function. The module uses an [SP800-90B]-compliant entropy source specified in the above table. This entropy source is located within the module’s physical perimeter but outside of the module’s cryptographic boundary. The module obtains 384 bits to seed the DRBG, and 256 bits to reseed it. The module performs the DRBG health tests as defined in Section 11.3 of [SP800-90A].

The module provides the following key generation methods:

• Key pair generation with ECDSA (CKG): curves P-224, P-256, P-384, P-521 with method B.4.2 Testing Candidates. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

• Key pair generation with RSA (CKG): 2048, 3072, 4096 bit keys with method B.3.3 Random Probable Primes.

The module provides the following key establishment methods:

• Key wrapping with AES: 128, 192, 256 bit keys with AES-KW, AES-CCM. Compliant with IG D.G.
• Key unwrapping with AES: 128, 192, 256 bit keys with AES-KW, AES-CCM. Compliant with IG D.G.

The module does not implement industry protocols, therefore this section is not applicable. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

N/A N/A N/A Table 12: Ports and Interfaces N/A As a software-only module, the module does not have physical ports. The operator can only interact with the module through the API provided by the module. Thus, the physical ports are interpreted to be the physical ports of the hardware platform on which the module runs. All data output via data output interface is inhibited when the module is performing pre-operational test or zeroization or when the module enters error state. The module does not implement a control output interface. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

The module does not support authentication.

Table 13: Roles The module supports the Crypto Officer role only. This sole role is implicitly and always assumed by the operator of the module.

t y t d W,E © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 y ) G,E c G,E A G,E c © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 y G,E W,E A W,E c W,E © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 G G y A c W,E A c W,E m r t: W,E © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 y G G,E G (V , G,W, E m r t: W,E G G,E G (V ,C ): © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 y G,W, E e e e e C W,E W,E © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Perform ondemand Perform selftests N/A N/A N/A N/A y W,E F : W,E G N/A e C N/A N/A N/A © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 N/A N/A y Table 14: Approved Services The table above lists the approved services. For each service, the table lists the associated cryptographic algorithm(s), the role to perform the service, the cryptographic keys or CSPs involved, and their access type(s). The following convention is used to specify access rights to a CSP: • G = Generate: The module generates or derives the SSP. • R = Read: The SSP is read from the module (e.g., the SSP is output). • W = Write: The SSP is updated, imported, or written to the module. • E = Execute: The module uses the SSP in performing a cryptographic operation. • Z = Zeroise: The module zeroises the SSP. • N/A: the calling application does not access any CSP or key during its operation. The details of the approved cryptographic algorithms including the CAVP certificate numbers can be found in the Approved Algorithm table. In order to check whether it utilizes an approved security function or not, the operator is responsible to invoke the gcry_control() API along with dedicated controls in the form of API input parameters. The module implements the following controls depending on the requested service:

1. GCRYCTL_FIPS_SERVICE_INDICATOR_CIPHER - For symmetric algorithms and the related modes.
2. GCRYCTL_FIPS_SERVICE_INDICATOR_KDF - For KDF operations.
3. GCRYCTL_FIPS_SERVICE_INDICATOR_PK_FLAGS - For asymmetric operations. 1
4. GCRYCTL_FIPS_SERVICE_INDICATOR_MD - For digest operations.
5. GCRYCTL_FIPS_SERVICE_INDICATOR_MAC - For MAC operations. In addition to that, for the below-mentioned services, the approved service indicator corresponds to the GPG_ERR_NO_ERROR returned from listed functions in the indicator column below. They don’t use gcry_control() API:
6. Random number generation service: gcry_randomize(), gcry_random_bytes(), gcry_random_bytes_secure().
7. Public key validation service: gcry_mpi_ec_curve_point().

1 The list of public key flags allowed in approved mode of operation is described in Section 4.6 Additional Information.

© 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 For all approved services, GPG_ERR_NO_ERROR (i.e., “0”) return code indicates the service is approved. In case the above-mentioned controls are used in conjunction, the operator is responsible to check that all of the called functions return GPG_ERR_NO_ERROR (i.e., “0”). For all non-approved services, "non-zero" return code indicates the service is not approved. Table 15: Non-Approved Services The table above lists the non-approved services. For the services listed below, the module implements an additional service indicator in the form of a control named GCRYCTL_FIPS_SERVICE_INDICATOR_FUNCTION. The operator is responsible to invoke the gcry_control() API along with the following input parameters: GCRYCTL_FIPS_SERVICE_INDICATOR_FUNCTION control; the name of the API 2 representing the service.

The module does not have the capability of loading software or firmware from an external source.

Below are listed the approved public key flags for an input s-expression:

2 The list of APIs supported by the module can be found in the documentation included in the optional libgcrypt-devel package.

© 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 d e n q r s © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

The integrity of the module is verified comparing the HMAC-SHA-256 value calculated at run time with the HMAC-SHA-256 value embedded in the module’s ELF header that was computed at build time for each software component of the module. If the HMAC values do not match, the test fails and the module enters the error state.

Integrity tests are performed as part of the Pre-Operational Self-Tests. The module provides the Self-Test service to perform self-tests on demand which includes the pre-operational tests (i.e., integrity test) and cryptographic algorithm self-tests (CASTs). This service can be invoked relying on the gcry_control(GCRYCTL_SELFTEST) API function call or by powering-off and reloading the module. During the execution of the on-demand self-tests, services are not available, and no data output or input is possible. In order to verify whether the self-tests have succeeded and the module is in the Operational state, the calling application may invoke the gcry_control(GCRYCTL_OPERATIONAL_P). The function will return TRUE if the module is in the operational state, FALSE if the module is in the Error state. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

Type of Operational Environment: Modifiable How Requirements are Satisfied: The module should be compiled and installed as stated in section 11. The user should confirm that the module is installed correctly by running: 1. 2. fips-mode-setup --check command to verify that the system is operating in Approved mode check the output of the gcry_get_config() API, which should output Libgcrypt cryptography module for AlmaLinux 9 1.10.0-9a1db72d64086a2f The module does not support concurrent operators.

Instrumentation tools like the ptrace system call, gdb and strace, userspace live patching, as well as other tracing mechanisms offered by the Linux environment such as ftrace or systemtap, shall not be used in the operational environment. The use of any of these tools implies that the cryptographic module is running in a non-validated operational environment.

The module shall be installed as stated in Section 11. If properly installed, the operating system provides process isolation and memory protection mechanisms that ensure appropriate separation for memory access among the processes on the system. Each process has control over its own data and uncontrolled access to the data of other processes is prevented. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

The module is comprised of software only and therefore this section is not applicable. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

This module does not implement any non-invasive security mechanism, and therefore this Section is not applicable. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

Table 16: Storage Areas appropriate zeroization function calls. Table 17: SSP Input-Output Methods form within the physical perimeter of the operational environment. This is allowed by [FIPS140-3_IG] 9.5.A, according to the “CM Software to/from App via TOEPP Path” entry on the Key Establishment Table. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 N/A Table 18: SSP Zeroization Methods The memory occupied by SSPs is allocated by regular memory allocation operating system calls. The application that is acting as the CO is responsible for calling the appropriate zeroization functions provided in the module's API and listed in the above table. Calling gcry_free(), which will zeroize the SSPs and also invoke the corresponding API functions listed in the above table to zeroize SSPs. The zeroization functions overwrite the operating system call. In case of abnormal termination, or swap in/out of a physical memory page of a process, the keys in physical memory are overwritten by the Linux kernel before the physical memory is allocated to another process. The completion of a zeroization routine(s) will indicate that a zeroization procedure succeeded. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 19: SSP Table 1 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 20: SSP Table 2 The tables above summarizes the Sensitive Security Parameters (SSPs) that are used by the cryptographic services implemented in the module.

The SHA-1 algorithm as implemented by the module will be non-approved for all purposes, starting January 1, 2030. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 Table 21: Pre-Operational Self-Tests The module performs pre-operational self-tests automatically when the module is becoming available for the consuming application. Pre-operational self-tests ensure that the module is not corrupted. While the module is executing the pre-operational self-tests, services are not available, input and output are inhibited. The module is not available for use by the calling application until the pre-operational self-tests are completed successfully. After the pre-operational self-tests and the CASTs succeed, the module becomes operational. If any of the preoperational self-tests or any of the CASTs fail an error message is returned, and the module transitions to the error state.

N/A N/A © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 N/A N/A N/A N/A AESCMAC AESCMAC © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 AESCMAC AESCMAC © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 HMACSHA2-256 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 HMACSHA2-512 HMACSHA2-512 HMACSHA2-512 HMACSHA2-512 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMACSHA2-512 HMACSHA3-224 HMACSHA3-224 HMACSHA3-224 HMACSHA3-256 HMACSHA3-256 HMACSHA3-256 HMACSHA3-384 HMACSHA3-384 HMACSHA3-384 HMACSHA3-512 HMACSHA3-512 HMACSHA3-512 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 HMACSHA-1 HMACSHA-1 HMACSHA-1 HMACSHA-1 HMACSHA-1 HMACSHA-1 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 22: Conditional Self-Tests

Table 23: Pre-Operational Periodic Information © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Table 24: Conditional Periodic Information This information can be found in Section 5.2.

Table 25: Error States application can obtain the module state by calling the gcry_control(GCRYCTL_OPERATIONAL_P) API function. The function returns FALSE if the module is in the Error state, TRUE if the module is in the Operational state. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 In the Error state, all data output is inhibited, and no cryptographic operation is allowed. The error can be recovered by a restart (i.e., powering off and powering on) of the module. If random numbers are requested while the module is in Error state, or if cipher operations are requested on a deallocated handle the module will transition to Fatal Error state, the module will abort and will not be available.

The software integrity tests and the CASTs can be invoked relying on the gcry_control(GCRYCTL_SELFTEST) API function call or by powering-off and reloading the module. The PCTs can be invoked on demand by requesting the Key Generation service. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

The Crypto Officer can install the libgcrypt-1.10.0-11.el9_2.tuxcare.1 RPM package of the Module using standard tools recommended for the installation of RPM packages on an Almalinux system (for example, DNF or RPM). The integrity of the RPM package is automatically verified during the installation, and the Crypto Officer shall not install the RPM package if there is any integrity error. Before the RPM package of the module is installed, the Almalinux 9 system must operate in Approved mode. This can be achieved by:

• Starting the installation in Approved mode. Add the fips=1 option to the kernel command line during the system installation. During the software selection stage, do not install any third-party software.
• Switching the system into Approved mode after the installation. Execute the fips-mode-setup --enable command. Restart the system. The Crypto Officer must verify the system operates in Approved mode by executing the fips-mode-setup -check command, which should output “FIPS mode is enabled.” After installation of the RPM package of the module, the operator needs to check the output of the gcry_get_config() API, which should include the following name and version: Libgcrypt cryptography module for AlmaLinux 9 1.10.0-9a1db72d64086a2f Once libgcrypt has been put into Approved mode, it is not possible to switch back to standard mode without terminating the process first. If the logging verbosity level of libgcrypt has been set to at least 2, the state transitions and the self-tests are logged.

All the functions, ports and logical interfaces described in this document are available to the Crypto Officer. The user must not call malloc/free to create/release space for keys, let libgcrypt manage space for keys, which will ensure that the key memory is overwritten before it is released. gcry_control(GCRYCTL_TERM_SECMEM) needs to be called before the process is terminated.

The module implements only the Crypto Officer. There are no requirements for non-administrator guidance.

For secure sanitization of the cryptographic module, the module must first to be powered off, which will zeroize all keys and CSPs in volatile memory. Then, for actual deprecation, the module shall be upgraded to a newer version that is FIPS 140-3 validated. The module does not possess persistent storage of SSPs, so further sanitization steps are not required. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9

RSA is vulnerable to timing attacks. In a setup where attackers can measure the time of RSA decryption or signature operations, blinding must be used to protect the RSA operation from that attack. By default, the module uses the following blinding technique: instead of using the RSA decryption directly, a blinded value y = x re mod n is decrypted and the unblinded value x' = y' r−1 mod n returned. The blinding value r is a random value with the size of the modulus n. © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Appendix A. Glossary and Abbreviations AES CAVP CBC CMAC CMVP CSP CTR DRBG ECB FIPS GCM HMAC KAT KW MAC NIST PAA PAI PR PSP PSS RNG RSA SHA SSP XTS Advanced Encryption Standard Cryptographic Algorithm Validation Program Cipher Block Chaining Cipher-based Message Authentication Code Cryptographic Module Validation Program Critical Security Parameter Counter Mode Deterministic Random Bit Generator Electronic Code Book Federal Information Processing Standards Publication Galois Counter Mode Hash Message Authentication Code Known Answer Test AES Key Wrap Message Authentication Code National Institute of Science and Technology Processor Algorithm Acceleration Processor Algorithm Implementation Prediction Resistance Public Security Parameter Probabilistic Signature Scheme Random Number Generator Rivest, Shamir, Adleman Secure Hash Algorithm Sensitive Security Parameter XEX-based Tweaked-codebook mode with cipher text Stealing © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 Appendix B. References FIPS140-3 FIPS140-3_IG FIPS180-4 FIPS186-2 FIPS186-4 FIPS186-5 FIPS197 FIPS198-1 SP800-38A SP800-38B SP800-38D SP800-38E SP800-38F SP800-52rev2 FIPS PUB 140-3 - Security Requirements For Cryptographic Modules March 2019 https://doi.org/10.6028/NIST.FIPS.140-3 Implementation Guidance for FIPS PUB 140-3 and the Cryptographic Module Validation Program January 2024 https://csrc.nist.gov/csrc/media/Projects/cryptographic-module-validationprogram/documents/fips%20140-3/FIPS%20140-3%20IG.pdf Secure Hash Standard (SHS) March 2012 https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf Digital Signature Standard (DSS) January 2000 https://csrc.nist.gov/files/pubs/fips/186-2/final/docs/fips186-2.pdf Digital Signature Standard (DSS) July 2013 https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf Digital Signature Standard (DSS) February 2023 https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-5.pdf Advanced Encryption Standard November 2001 https://csrc.nist.gov/publications/fips/fips197/fips-197.pdf The Keyed Hash Message Authentication Code (HMAC) July 2008 https://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf NIST Special Publication 800-38A - Recommendation for Block Cipher Modes of Operation Methods and Techniques December 2001 https://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf NIST Special Publication 800-38B - Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication May 2005 https://csrc.nist.gov/publications/detail/sp/800-38b/final NIST Special Publication 800-38D - Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC November 2007 https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf NIST Special Publication 800-38E - Recommendation for Block Cipher Modes of Operation: The XTS AES Mode for Confidentiality on Storage Devices January 2010 https://csrc.nist.gov/publications/nistpubs/800-38E/nist-sp-800-38E.pdf NIST Special Publication 800-38F - Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping December 2012 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-38F.pdf NIST Special Publication 800-52

• Revision 2 - Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Libgcrypt cryptography module for AlmaLinux 9 SP800-56Arev3 SP800-56Crev2 SP800-90Arev1 SP800-90B SP800-108rev1 SP800-132 SP800-133rev2 SP800-135rev1 SP800-140Br1 August 2019 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r2.pdf NIST Special Publication 800-56A

• Revision 3 - Recommendation for Pair-Wise KeyEstablishment Schemes Using Discrete Logarithm Cryptography April 2018 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf NIST Special Publication 800-56C
• Revision 2 - Recommendation for Key-Derivation Methods in Key-Establishment Schemes August 2020 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Cr2.pdf NIST Special Publication 800-90A
• Revision 1 - Recommendation for Random Number Generation Using Deterministic Random Bit Generators June 2015 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-90Ar1.pdf NIST Special Publication 800-90B - Recommendation for the Entropy Sources Used for Random Bit Generation January 2018 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-90B.pdf NIST Special Publication 800-108
• Revision 1 - Recommendation for Key Derivation Using Pseudorandom Functions August 2022 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-108r1-upd1.pdf NIST Special Publication 800-132 - Recommendation for Password-Based Key Derivation - Part 1: Storage Applications December 2010 https://csrc.nist.gov/publications/nistpubs/800-132/nist-sp800-132.pdf NIST Special Publication 800-133
• Revision 2 - Recommendation for Cryptographic Key Generation June 2020 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-133r2.pdf NIST Special Publication 800-135
• Revision 1
• Recommendation for Existing ApplicationSpecific Key Derivation Functions December 2011 https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-135r1.pdf NIST Special Publication 800-140B
• Revision 1 - CMVP Security Policy Requirements November 2023 https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-140Br1.pdf © 2026 Cloudlinux Inc., TuxCare division, atsec information security.

Referenced URLs

• www.atsec.com
• https://doi.org/10.6028/NIST.FIPS.140-3
• https://csrc.nist.gov/csrc/media/Projects/cryptographic-module-validation-
• https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf
• https://csrc.nist.gov/files/pubs/fips/186-2/final/docs/fips186-2.pdf
• https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf
• https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-5.pdf
• https://csrc.nist.gov/publications/fips/fips197/fips-197.pdf
• https://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf
• https://csrc.nist.gov/publications/nistpubs/800-38a/sp800-38a.pdf
• https://csrc.nist.gov/publications/detail/sp/800-38b/final
• https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf
• https://csrc.nist.gov/publications/nistpubs/800-38E/nist-sp-800-38E.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-38F.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52r2.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Cr2.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-90Ar1.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-90B.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-108r1-upd1.pdf
• https://csrc.nist.gov/publications/nistpubs/800-132/nist-sp800-132.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-133r2.pdf
• https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-135r1.pdf
• https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-140Br1.pdf