Red Hat Enterprise Linux 9 libgcrypt

Certificate

Approved Algorithms (229)

Security Levels (Table 1)

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

flowchart LR
  %% Deterministic review-risk graph for Red Hat Enterprise Linux 9 libgcrypt
  %% 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>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 Red Hat Enterprise Linux 9 libgcrypt
  %% 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>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

Red Hat, Inc. Red Hat Enterprise Linux 9 libgcrypt Prepared by: atsec information security corporation

Austin, TX 78759 Document version: 1.0 www.atsec.com Last update: 2024-07-30

Red Hat Enterprise Linux 9 libgcrypt Table of Contents © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt List of Tables Table 2: Tested Module Identification

• Software, Firmware, Hybrid (Executable Code Sets)..8 List of Figures © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

This document is the non-proprietary FIPS 140-3 Security Policy for version 1.10.08b6840b590cedd43 of the Red Hat Enterprise Linux 9 libgcrypt. 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 Red Hat Enterprise Linux 9 libgcrypt 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. intact and 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 supply additional documentation, which the laboratory formatted into the existing Security Policy, and resubmitted to the vendor for their final editing. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

Purpose and Use: The Red Hat Enterprise Linux 9 libgcrypt (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: MultiChipStand Module Characteristics: 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 © 2024 Red Hat, Inc., atsec information security.

Identification Tested Module Identification

• Hardware: N/A for this module. Tested Module Identification
• Software, Firmware, Hybrid (Executable Code Sets): N/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: 1.10.0Enterprise N/A 1.10.0Enterprise N/A IBM 9080IBM 1.10.0PowerVM N/A 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. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

Modes List and Description: Nonapproved NonApproved Table 5: Modes List and Description 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 Non-Approved 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 when an approved service is called. The module does not implement a degraded mode of operation.

Approved Algorithms: © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2224 HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2512 HMAC-SHA3224 HMAC-SHA3256 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA3384 HMAC-SHA3512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2224 HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2224 HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2224 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2512 HMAC-SHA3224 HMAC-SHA3256 HMAC-SHA3384 HMAC-SHA3512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA3384 HMAC-SHA3512 HMAC-SHA3224 HMAC-SHA3256 HMAC-SHA2224 HMAC-SHA2256 HMAC-SHA2384 HMAC-SHA2512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt 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: SP 800133Rev2 SP 800133Rev2 Table 7: Vendor-Affirmed Algorithms 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: 4.8 4.8 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. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

© 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt AsymKeyPairKeyVer © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 HMAC-SHA2224 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA2256 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 HMAC-SHA3224 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMAC-SHA3224 HMAC-SHA3256 HMAC-SHA3256 HMAC-SHA3256 HMAC-SHA3384 HMAC-SHA3384 HMAC-SHA3384 HMAC-SHA3512 HMAC-SHA3512 HMAC-SHA3512 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt 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. © 2024 Red Hat, Inc., atsec information security.

The AES-XTS mode shall only be used for the cryptographic protection of data on storage devices. The AES-XTS 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 SP800-90A 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 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].

Table 10: Entropy Certificates NonPhysical © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt 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 module supports the Hash_DRBG, HMAC_DRBG and CTR_DRBG. 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, respectivly corresponding to 337 bits of entropy for seeding and 225 bits for reseeding, which is not full entropy. Therefore, the module generates SSPs (e.g., keys) whose strengths are modified by available entropy. The module performs the DRBG health tests as defined in Section 11.3 of [SP800-90A].

KeyGenerationSubTable From Web Cryptik KeyGenerationSubTable The module provides an [SP800-90Arev1]-compliant Deterministic Random Bit Generator (DRBG) for the creation of key components of asymmetric keys, and random number generation. The Cryptographic Key Generation (CKG) methods implemented in the module for Approved services in approved mode are compliant with section 5.1 of [SP800-133rev2] and with IG D.H. For generating RSA and ECDSA keys the module implements asymmetric key © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt generation services compliant with [FIPS186-4]. A seed (i.e., the random value) used in asymmetric key generation is directly obtained from the [SP800-90Arev1] DRBG. Intermediate key generation values are not output from the module and are explicitly zeroized after processing the service

KeyAgreementSubTable From Web Cryptik KeyAgreementSubTable KeyTransportSubTable From Web Cryptik KeyTransportSubTable The module provides the following key transport mechanisms:

• AES key wrapping using AES-KW.
• AES key wrapping using AES-CCM. According to Table 2: Comparable strengths in [SP 800-57rev5], the key sizes of AES provide the following security strength in approved mode of operation:
• AES key wrapping in KW mode provides 128, 192, 256-bit keys with key strength between 128-256 bits in compliance with SP800-38F and IG D.G.
• AES key wrapping using AES-CCM provides 128, 192, 256-bit keys with key strength between 128-256 bits in compliance with SP800-38F and IG D.G. Additionally, the module supports password-based key derivation (PBKDF2). The implementation is compliant with option 1a of [SP-800-132]. Keys derived from passwords or passphrases using this method can only be used in storage applications

The module does not implement industry protocols, therefore this section is not applicable.

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

N/A N/A N/A N/A Table 12: Ports and Interfaces 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 preoperational test or zeroization or when the module enters error state. The module does not implement a control output interface.

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

N/A for this module. 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.

y ) s W,E © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt y A A e s G,R G,R G,E,Z G,R G,R G,E,Z W,E © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt y s e W,E e e W,E e W,E © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt (), (), y m m s W,E y W,E G,E (V G,W,E y W,E G,E (V C G,W,E © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt y e e AESCMAC s W,E W,E W,E W,E Perform ondemand N/A W,E G,R N/A e © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt y N/A N/A e N/A N/A N/A N/A N/A e n Perform selftests N/A s 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. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

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(). 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.

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

Information. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt Table 15: Non-Approved Services

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: d e n q r s © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

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.

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

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. fips-mode-setup --check command to verify that the system is operating in Approved mode 2. check the output of the gcry_get_config() API, which should output Red Hat Enterprise Linux 9 libgcrypt 1.10.0-8b6840b590cedd43 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. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

The module is comprised of software only and therefore this section is not applicable.

Not Applicable. N/A for this module.

Not Applicable. Number: Placement: Surface Preparation: Operator Responsible for Securing Unused Seals: Part Numbers:

Not Applicable. Not Applicable. Table 16: EFP/EFT Information

Not Applicable. Table 17: Hardness Testing Temperatures © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

This module does not implement any non-invasive security mechanism, and therefore this Section is not applicable.

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

Table 18: Storage Areas destroyed when released by the appropriate zeroization function calls. s s t c t c m Table 19: SSP Input-Output Methods API output parameters in plaintext 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. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt N/A Table 20: 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 memory deallocation 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. n, with AESCMAC © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt n n n n © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt e (SP 800133r2 5.2) D.L ) ) bits - 112256 bits G G G G © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt ) D.L ) G G G G G G Table 21: SSP Table 1 s s t t n © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt s s s s s s s s n t t t t t © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt s s t t t t t t n Table 22: SSP Table 2 The tables above summarizes the Sensitive Security Parameters (SSPs) that are used by the cryptographic services implemented in the module. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

The SHA-1 algorithm as implemented by the module will be non-approved for all purposes, starting January 1, 2030.

Not Applicable. © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt

HMACSHA2-256 s n y .0 Table 23: 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 preoperational self-tests and the CASTs succeed, the module becomes operational. If any of the pre-operational self-tests or any of the CASTs fail an error message is returned, and the module transitions to the error state.

© 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt (FIPS1864) (A3757) (FIPS1864) (A3759) (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) (FIPS1864) (A3757) (FIPS1864) (A3759) © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) (FIPS1864) (A3757) (FIPS1864) (A3759) (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 HMACSHA2-224 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-256 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 HMACSHA2-384 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMACSHA2-512 HMACSHA2-512 HMACSHA2-512 HMACSHA2-512 HMACSHA2-512 HMACSHA3-224 HMACSHA3-224 HMACSHA3-224 HMACSHA3-256 © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt HMACSHA3-256 HMACSHA3-256 HMACSHA3-384 HMACSHA3-384 HMACSHA3-384 HMACSHA3-512 HMACSHA3-512 HMACSHA3-512 (FIPS1864) (A3757) © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt (FIPS1864) (A3759) (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) (FIPS1864) (A3757) (FIPS1864) (A3759) (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt Passwordbased key Passwordbased key Passwordbased key Passwordbased key Passwordbased key © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt Passwordbased key Passwordbased key Passwordbased key Passwordbased key © 2024 Red Hat, Inc., atsec information security.

Red Hat Enterprise Linux 9 libgcrypt (FIPS1864) (A3757) (FIPS1864) (A3759) (FIPS1864) (A3760) (FIPS1864) (A3761) (FIPS1864) (A3762) (FIPS1864) (A3757) (FIPS1864) (A3759) (FIPS1864) (A3760) Passwordbased key with SHA2256 with SHA2256 with SHA2256 with SHA2256 with SHA2256 © 2024 Red Hat, Inc., atsec information security.