Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic
Module
version rhel8.20210302
FIPS 140-2 Non-Proprietary Security Policy
Version 1.1
Last update: 2022-02-16
Prepared by:
atsec information security corporation
9130 Jollyville Road, Suite 260
Austin, TX 78759
www.atsec.com
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 1 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Table of Contents
1 Cryptographic Module Specification.......................................................................................4
1.1 Module Overview..........................................................................................................4
1.2 FIPS 140-2 validation....................................................................................................6
1.3 Modes of Operations.....................................................................................................7
2 Cryptographic Module Ports and Interfaces............................................................................8
3 Roles, Services and Authentication........................................................................................9
3.1 Roles.............................................................................................................................9
3.2 Services........................................................................................................................9
3.3 Authentication............................................................................................................13
4 Physical Security..................................................................................................................14
5 Operational Environment.....................................................................................................15
5.1 Applicability................................................................................................................15
5.2 Policy..........................................................................................................................15
6 Cryptographic Key Management..........................................................................................16
6.1 Random Number Generation......................................................................................16
6.2 Key Generation...........................................................................................................16
6.3 Key establishment / Key Transport..............................................................................18
6.4 Key / Critical Security Parameter (CSP) Access...........................................................18
6.5 Key / CSP Storage.......................................................................................................18
6.6 Key / CSP Zeroization..................................................................................................19
7 Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC)..............................20
8 Self-Tests..............................................................................................................................21
8.1 Power-Up Self-Tests.....................................................................................................21
8.1.1 Integrity Tests....................................................................................................21
8.2 Conditional Tests.........................................................................................................22
9 Guidance..............................................................................................................................23
9.1 Cryptographic Officer Guidance..................................................................................23
9.1.1 Secure Installation and Startup.........................................................................23
9.1.2 FIPS module installation instructions:................................................................23
9.1.2.1 Recommended method..................................................................................23
9.1.2.2 Manual method..............................................................................................23
9.2 User Guidance............................................................................................................24
9.2.1 XTS Usage.........................................................................................................24
9.2.2 GCM Usage........................................................................................................24
9.2.3 Triple-DES Usage...............................................................................................24
9.3 Handling Self Test Errors.............................................................................................25
10 Mitigation of Other Attacks................................................................................................26
Appendix A Glossary and Abbreviations..................................................................................27
Appendix B References...........................................................................................................28
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 2 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Introduction
This document is the non-proprietary Security Policy for the Red Hat Enterprise Linux 8 Kernel
Crypto API Cryptographic Module version rhel8.20210302. 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-2 (Federal Information Processing Standards Publication 140-2) for a
Security Level 1 module.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 3 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
1 Cryptographic Module Specification
1.1 Module Overview
The Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module (hereafter referred to
as the “Module”) is a software only cryptographic module that provides general-purpose
cryptographic services to the remainder of the Linux kernel. The Red Hat Enterprise Linux 8
Kernel Crypto API Cryptographic Module is software only, security level 1 cryptographic
module, running on a multi-chip standalone platform.
The module is implemented as a set of shared libraries / binary files.
Figure 1: Cryptographic Module Logical Boundary
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 4 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
The module is aimed to run on a general purpose computer; the physical boundary is the
surface of the case of the target platform, as shown in the diagram below:
The following list of packages is required for the module to operate:
• the kernel-4.18.0-240.15.1.el8_3 package, which contains the binary files, integrity
check HMAC files and Man Pages for the kernel
• the libkcapi-1.2.0-2.el8.x86_64 package
• the libkcapi-hmaccalc-1.2.0-2.el8.x86_64 package.
The module is made of the following files:
• kernel loadable components /lib/modules/$(uname -r)/kernel/crypto/*.ko
• kernel loadable components /lib/modules/$(uname -r)/kernel/arch/x86/crypto/*.ko
• static kernel binary (vmlinuz): /boot/vmlinuz-$(uname -r)
• static kernel binary (vmlinuz) HMAC file: /boot/.vmlinuz-$(uname -r).hmac
• sha512hmac binary file for performing the integrity checks: usr/bin/sha512hmac
• sha512hmac binary HMAC file: /usr/lib64/hmaccalc/sha512hmac.hmac
• libkcapi library: /usr/lib64/libkcapi.so.1.2.0
• libkcapi library HMAC file: /usr/lib64/fipscheck/libkcapi.so.1.2.0.hmac
The kernel provides the HMAC-SHA-512 algorithm used by the sha512hmac binary file to
verify the integrity of both the sha512hmac file and the vmlinuz (static kernel binary) file.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 5 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Figure 2: Cryptographic Module Physical Boundary
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
1.2 FIPS 140-2 validation
For the purpose of the FIPS 140-2 validation, the module is a software-only, multi-chip
standalone cryptographic module validated at security level 1. The table below shows the
security level claimed for each of the eleven sections that comprise the FIPS 140-2 standard:
FIPS 140-2 Section Security Level
1 Cryptographic Module Specification 1
2 Cryptographic Module Ports and Interfaces 1
3 Roles, Services and Authentication 1
4 Finite State Model 1
5 Physical Security N/A
6 Operational Environment 1
7 Cryptographic Key Management 1
8 EMI/EMC 1
9 Self Tests 1
10 Design Assurance 1
11 Mitigation of Other Attacks N/A
Table 1: Security Levels
The module has been tested on the following platforms with the following configuration:
Hardware Platform Processor Operating System Tested
With PAA (AES-
NI)
Without PAA
(AES-NI)
Dell PowerEdge R440 Intel(R) Xeon(R)
Silver 4216
Red Hat
Enterprise Linux 8
yes yes
Table 2: Tested Platforms
The following platform has not been tested as part of the FIPS 140-2 level 1 certification
however Red Hat “vendor affirms” that this platform is equivalent to the tested and validated
platform. Additionally, Red Hat affirms that the module will function the same way and
provide the same security services on any of the systems listed below.
Hardware Platform Processor Operating System
Dell PowerEdge R430 Intel(R) Xeon(R) E5 Red Hat Enterprise Linux 8
Table 2A: Vendor Affirmed Platforms
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.
NOTE: This validation is only for the tested platform listed in Table 2 of this document. It does not cover
other derivatives of the Operating Systems (I.e, Centos or Fedora).
The physical boundary is the surface of the case of the target platform. The logical boundary
is depicted in Figure 1.
The module also includes algorithm implementations using Processor Algorithm Acceleration
(PAA) functions provided by the different processors supported, as shown in the following
table:
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 6 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Processor Processor Algorithm Acceleration (PAA)
function
Algorithm
Intel Xeon Silver 4216 AES-NI AES
Table 3: PAA function implementations
1.3 Modes of Operations
The module supports two modes of operation: the FIPS approved and non-approved modes.
Section 9.1.1 describes the Secure Installation and Startup to correctly install and configure
the module. The module turns to FIPS approved mode after correct initialization, successful
completion of power-on self-tests.
Invoking a non-Approved algorithm or a non-Approved key size with an Approved algorithm as
listed in Table 6 will result in the module implicitly entering the non-FIPS mode of operation.
The critical security parameters (CSPs) used or stored in approved mode are not used in non-
approved mode and vice versa.
Once the module is operational, the mode of operation is implicitly assumed depending on
the security function invoked and the security strength of the cryptographic keys.
The approved services available in FIPS mode can be found in section 3.2, Table 5.
The non-approved services not available in FIPS mode can be found in section 3.2, Table 6.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 7 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
2 Cryptographic Module Ports and Interfaces
As a software-only module, the module does not have physical ports. For the purpose of the
FIPS 140-2 validation, the physical ports are interpreted to be the physical ports of the
hardware platform on which it runs.
The logical interfaces are the application program interface (API) through which applications
request services. The following table summarizes the four logical interfaces:
Logical
interfaces
Description Physical ports mapping the
logical interfaces
Control In API function calls, kernel command
line
Keyboard
Status Out API return codes, kernel logs Display
Data In API input parameters Keyboard
Data Out API output parameters Display
Power Input PC Power Port Physical Power Connector
Table 4: Ports and Logical Interfaces
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 8 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
3 Roles, Services and Authentication
3.1 Roles
The module supports the following roles:
⚫ User role: performs symmetric encryption/decryption, keyed hash, message digest,
random number generation, show status
⚫ Crypto Officer role: performs the module installation and configuration, module's
initialization, self-tests, zeroization and signature verification
The User and Crypto Officer roles are implicitly assumed by the entity accessing the module
services.
3.2 Services
The module supports services available to users in the available roles. All services are
described in detail in the user documentation.
The following table shows the available services, the roles allowed, the Critical Security
Parameters involved and how they are accessed in the FIPS mode. 'R' stands for Read
permission, 'W' stands for write permission and 'EX' stands for executable permission of the
module:
Service Algorithms Note(s) /
Mode(s)
CAVP
Cert(s).
Role CSPs Access
Symmetric
encryption/
decryption
Triple-DES CBC, CTR, ECB, A1264
A1278
A1283
User 192 bits
Triple-DES
keys
The security
strength of
the keys is
112 bits
R, EX
CMAC A1264
A1278
CFB64 A1266
A1281
AES CBC, CCM, CMAC,
CTR, ECB, GCM
(external IV,
decryption only),
GMAC, XTS
A1264
A1273
A1278
128, 192 and
256 bits AES
keys
Note: XTS
mode only
with 128 and
256 bits
keys.
ECB A1262
A1263
128, 192 and
256 bits AES
keys
CBC-CS3 A1267
A1277
A1282
128, 192 and
256 bits AES
keys
ECB, GCM
(internal IV,
A1268
A1271
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 9 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Service Algorithms Note(s) /
Mode(s)
CAVP
Cert(s).
Role CSPs Access
encryption only) A1274
A1279
ECB, GCM
(external IV,
decryption only)
A1269
A1272
A1275
A1280
CFB128 A1266
A1276
A1281
CBC, CTR, ECB,
GCM (external IV,
decryption only),
XTS
A1270
Keyed hash
(HMAC)
HMAC SHA-1,
HMAC SHA-224,
HMAC SHA-256,
HMAC SHA-384,
HMAC SHA-512
BS < KS, KS =
BS, KS > BS
A1262
A1263
A1264
A1284
A1285
A1286
User at least 112
bits HMAC
keys
R, EX
HMAC-SHA3-224,
HMAC-SHA3-256,
HMAC-SHA3-384
HMAC-SHA3-512
A1265
Message digest
(SHS)
SHA-1, SHA-224,
SHA-256, SHA-384
SHA-512
N/A A1262
A1263
A1264
A1284
A1285
A1286
User N/A N/A
SHA3-224,
SHA3-256,
SHA3-384
SHA3-512
A1265
Authenticated
encryption
(KTS)
AES-CBC and HMAC-
SHA-1, SHA-224 SHA-
256, SHA-384 and SHA-
512
CBC and HMAC
used with
encrypt-then-
MAC cipher
(authenc) used
for IPsec
See AES,
Triple-
DES and
HMAC
certs
User 128, 192 and
256 bits AES
keys, HMAC
keys
192 bits
Triple-DES
keys
R, EX
Triple-DES-CBC and
HMAC-SHA-1, SHA-224
SHA-256, SHA-384 and
SHA-512
AES GCM
AES CCM
Random CTR DRBG With derivation A1262 User Entropy input R, W,
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 10 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Service Algorithms Note(s) /
Mode(s)
CAVP
Cert(s).
Role CSPs Access
number
generation (SP
800-90A DRBG)
function, with
and without
prediction
resistance
function using
AES-128, AES-
192 and AES-256
A1263
A1264
A1268
A1269
A1270
A1271
A1272
A1273
A1274
A1275
A1278
A1279
A1280
string, seed,
V, C values
and Key (K)
EX
Hash DRBG With and without
prediction
resistance
function using
SHA-1, SHA-256,
SHA_384 and
SHA-512
A1262
A1263
A1264
A1268
A1269
A1270
A1271
A1272
A1273
A1274
A1275
A1278
A1279
A1280
A1283
A1284
A1285
A1286
HMAC DRBG With and without
prediction
resistance
function using
SHA-1, SHA-256,
SHA-384 and
SHA-512
Entropy
(SP 800-90B)
ENT (NP) N/A N/A User N/A N/A
Signature
verification
RSA 2048, 3072 and
4096 bits
signature
verification
according to
PKCS#1 v1.5,
using SHA-1,
SHA-224, SHA-
256, SHA-384,
SHA-512
A1264
A1284
A1285
A1286
User RSA public
key
R
Signature
Generation
RSA According to
PKCS#1 v1.5
A1264 User 2048, 3072,
4096-bit RSA
R, EX
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 11 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Service Algorithms Note(s) /
Mode(s)
CAVP
Cert(s).
Role CSPs Access
SHA-224, SHA-
256, SHA-384,
SHA-512
A1284
A1285
A1286
private key
KAS-ECC-SSC
SP 800-
56Arev3
Ephemeral Unified P-256 A1263 User EC Diffie-
Hellman
public/private
keys
R
Shared
secret
R, W, X
ECDSA Key
generation for
EC Diffie-
Hellman shared
secret
computation1
Generation per section
5.6.1.2 of SP800-
56Arev3 exclusively for
EC Diffie-Hellman
P-256 A1263 User EC Diffie-
Hellman
public/private
keys
W
Module
initialization
N/A N/A N/A Crypto
officer
N/A N/A
Self-tests HMAC-SHA-512,
RSA Signature
Verification
Integrity test of
the kernel static
binary performed
by the
sha512hmac
binary
RSA signature
verification
performs the
signature
verification of the
kernel loadable
components
Crypto
officer
N/A R, EX
Show status N/A Via verbose
mode, exit codes
and kernel logs
(dmesg)
N/A User N/A N/A
Zeroize N/A N/A N/A Crypto
officer
All CSPs N/A
Installation and
configuration
N/A N/A N/A Crypto
officer
N/A N/A
Table 5: Available Cryptographic Module's Services in FIPS mode
The module claims SP 800-38F compliant key wrapping with the following modes (using any
available implementation specified in Table 5):
• AES-GCM
• AES-CCM
• AES-CBC with HMAC-SHA1, HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384 and
HMAC-SHA-512
• Triple-DES-CBC with HMAC-SHA1, HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384 and
HMAC-SHA-512.
1 The EC key generation service does not perform a pairwise consistency test on the
generated keys. This service is for exclusive use of EC Diffie-Hellman shared secret
computation service, and only under this context. This service is approved without the
pairwise consistency test as allowed per the additional comments in IG 9.4.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 12 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Therefore, the following caveats apply:
KTS (AES Certs. #A1264, #A1268, #A1269, #A1270, #A1271, #A1272,
#A1273, #A1274, #A1275, #A1278, #A1279 and #A1280; key establishment
methodology provides between 128 and 256 bits of encryption strength)
KTS (AES Certs. #A1264, #A1270, #A1273 and #A1278 and HMAC Certs.
#A1262, #A1263, #A1264, #A1284, #A1285 and #A1286; key establishment
methodology provides between 128 and 256 bits of encryption strength)
KTS (Triple-DES Certs. #A1264, #A1278 and #A1283 and HMAC Certs. #A1262,
#A1263, #A1264, #A1284, #A1285 and #A1286; key establishment
methodology provides 112 bits of encryption strength).
Note: There are algorithms, modes, and keys that have been CAVP tested but not used by the
module in FIPS approved mode. Only the algorithms, modes/methods, and key
lengths/curves/moduli shown in table 5 are used by the module in FIPS approved mode.
In non-Approved mode the Module supports the following non-FIPS Approved algorithms,
which shall not be used in the FIPS Approved mode of operation:
Service Algorithms Note(s) / Mode(s) Role Key(s) Access
Symmetric
encryption/
decryption
AES XTS with 192-bit keys User 192 bits AES keys R, EX
GCM encryption with
external IV
128, 192, 256-bit
AES keys
DES ECB 56 bits DES keys
Message
digest
SHA-1 (multiple-
buffer
implementation)
N/A User N/A R, EX
Keyed hash HMAC Keys smaller than 112 bits User HMAC keys with size
less than 112 bits
R, EX
Random
number
generation
ansi_cprng N/A User seed R, W, EX
Signature
Generation
RSA Using SHA-1 User RSA private key R, EX
Shared
secret
computation
Diffie-Hellman Shared secret
computation
User Diffie-Hellman
private keys
shared secret
R, W, EX
Table 6: Service Details for the non-FIPS mode
3.3 Authentication
The module is a Level 1 software-only cryptographic module and does not implement
authentication. The role is implicitly assumed based on the service requested.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 13 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
4 Physical Security
The module is comprised of software only and thus does not claim any physical security.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 14 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
5 Operational Environment
5.1 Applicability
The Red Hat Enterprise Linux operating system is used as the basis of other products which
include but are not limited to:
• Red Hat Enterprise Linux CoreOS
• Red Hat Virtualization (RHV)
• Red Hat OpenStack Platform
• OpenShift Container Platform
• Red Hat Gluster Storage
• Red Hat Ceph Storage
• Red Hat CloudForms
• Red Hat Satellite.
Compliance is maintained for these products whenever the binary is found unchanged.
The module operates in a modifiable operational environment per FIPS 140-2 level 1
specifications. The module runs on a commercially available general-purpose operating
system executing on the hardware specified in section 1.2.
5.2 Policy
The operating system is restricted to a single operator (concurrent operators are explicitly
excluded). The application that request cryptographic services is the single user of the
module, even when the application is serving multiple clients.
In FIPS Approved mode, the ptrace(2) system call, the debugger (gdb(1)), and strace(1) shall
be not used.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 15 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
6 Cryptographic Key Management
6.1 Random Number Generation
The module employs a SP 800-90A DRBG based on [SP800-90A] as a random number
generator for the creation of random numbers. In addition, the module provides a Random
Number Generation service to applications.
The DRBG supports the Hash_DRBG, HMAC_DRBG and CTR_DRBG mechanisms. The module
performs the DRBG health tests as defined in section 11.3 of [SP800-90A]. The module uses
CPU jitter as an entropy source for seeding the DRBG. The entropy source is compliant with
[SP 800-90B] and marked as ENT (NP) on the certificate. The entropy source is tested with
RCT and APT Health tests as required by section 4 of [SP 800-90B].
The DRBG is seeded with (DRBG_security_strength * 1.5) bits of random data from the CPU
jitter RNG containing at least DRBG_security_strength bits of entropy. (e.g. 384 bits for the
CTR_DRBG using AES-256). Therefore, the module ensures that during initialization (seed)
and reseeding, the entropy source provides the required amount of entropy to meet the
security strength of the respective DRBG methods.
The module performs conditional self-tests on the output of the entropy source to ensure that
consecutive random numbers do not repeat.
6.2 Key Generation
Here are listed the CSPs/keys details concerning storage, input, output, generation and
zeroization:
Type Keys/CSPs Generation Key Storage Key
Entry/Output
Key Zeroization
Symmetric
keys
AES N/A Protected
kernel memory
API allows caller
on the same GPC
to supply key
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
-crypto_free_cipher()
key zeroization for
single raw cipher
handle
-
crypto_free_ablkciph
er key zeroization
method for
asynchronous raw
cipher handle
-
crypto_free_blkcipher
() key zeroization
method for
synchronous raw
cipher handle
-
crypto_free_skcipher(
) key zeroization
method for
symmetric ciphers
Triple-DES N/A Protected
kernel memory
API allows caller
on the same GPC
to supply key
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 16 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
-crypto_free_cipher()
key zeroization for
single raw cipher
handle
-
crypto_free_ablkciph
er key zeroization
method for
asynchronous raw
cipher handle
-
crypto_free_skcipher(
) key zeroization
method for
symmetric ciphers
DRBG SP800-
90A entropy
string
SP 800-90A
DRBG
Entropy
string
Obtained from
entropy source
Module’s
application
memory
N/A Automatic zeroization
when seeding
operation completes
SP 800-90A
DRBG C, V
and K values
(internal
state) and
seed
SP 800-90A
DRBG seed
and
internal
state
values V, C
and K
Generated
during DRBG
initialization
Protected
kernel memory
N/A Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
-crypto_free_rng()
key zeroization
method for DRBG
CSPs
HMAC keys HMAC N/A Protected
kernel memory
HMAC key can be
supplied by calling
application
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
-crypto_free_shash()
key zeroization
method for
synchronous
message digest
handle.
RSA private
key
Private key N/A Protected
kernel memory
Key is passed in to
module via API
input parameters
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
-crypto_free_kpp()
RSA public
key
Public key N/A Protected
kernel memory
Key is passed in to
module via API
input parameters
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
-crypto_free_kpp()
EC Diffie-
Hellman
public and
private keys
public key
private key
Generated using
the FIPS 186-4
EC key
generation
service;random
values are
Protected
kernel memory
key is passed in to
module via API
input parameters
Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
crypto_free_kpp()
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 17 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
obtained from
the SP800-90A
DRBG
Shared
secret
shared
secret
Computed
during EC Diffie-
Hellman shared
secret
computation
Protected
kernel memory
N/A Memory is
automatically
overwritten by zeroes
when freeing the
cipher handler
crypto_free_kpp()
Table 7: Keys/CSPs
The public and private keys used in the EC Diffie-Hellman shared secret computation portion
of the key agreement scheme are generated internally by the module using the ECDSA key
generation method compliant with [SP800-133], [FIPS186-4] and [SP800-56Arev3]. the
random value used in asymmetric key generation is directly obtained from the [SP800-90A]
DRBG. This key generation method is used exclusively by the EC Diffie-Hellman algorithm and
provides support for the required assurances of [SP800-56Arev3].
1. In accordance with IG D.12, the cryptographic module performs Cryptographic Key
Generation (CKG) for asymmetric keys per SP800-133 (vendor affirmed).
2. As defined in SP800-90A, the DRBG obtains the entropy string and nonce from the Linux
kernel non-deterministic random number generator during:
a. initialization of a DRBG instance
b. after 2⁴⁸ requests for random numbers.
6.3 Key establishment / Key Transport
The module supports EC Diffie-Hellman shared secret primitive computation:
• EC Diffie-Hellman: shared secret computation provides 128 bits of encryption strength.
The module provides SP 800-38F compliant key wrapping using AES with GCM and CCM block
chaining modes, as well as a combination of AES-CBC for encryption/decryption and HMAC for
authentication. The module also provides SP 800-38F compliant key wrapping using a
combination of Triple-DES-CBC for encryption/decryption and HMAC for authentication.
According to “Table 2: Comparable strengths” in [SP 800-57], the key sizes of AES provides
the following security strength in FIPS mode of operation:
• AES: key wrapping with 128, 192 and 256 bits keys provides between 128 and 256 bits
of encryption strength.
• Triple-DES: key wrapping with 168 bits keys provides 112 bits of encryption strength.
6.4 Key / Critical Security Parameter (CSP) Access
An authorized application as user (the User role) has access to all key data generated during
the operation of the module. Moreover, the module does not support the output of
intermediate key generation values during the key generation process.
6.5 Key / CSP Storage
Symmetric keys are provided to the module by the calling process, and are destroyed when
released by the appropriate API function calls. The module does not perform persistent
storage of keys. The RSA public key used for signature verification of the kernel loadable
components is stored outside of the module’s boundary, in a keyring file in /proc/keys/. The
Diffie-Hellman and EC Diffie-Hellman public keys are stored in protected kernel memory.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 18 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
6.6 Key / CSP Zeroization
The application that uses the module is responsible for appropriate destruction and
zeroization of the key material. The library provides functions for key allocation and
destruction, which overwrites the memory that is occupied by the key information with
“zeros” before it is deallocated.
When a calling kernel components calls the appropriate API function that operation overwrites
memory with 0s and then frees that memory (please see the API document for full details).
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 19 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
7 Electromagnetic Interference/Electromagnetic
Compatibility (EMI/EMC)
MARKETING NAME......................….PowerEdge R440
REGULATORY MODEL................…..E45S
REGULATORY TYPE.....................….E45S001
EFFECTIVE DATE..........................…March 01, 2020
EMC EMISSIONS CLASS...............…Class A
This product has been determined to be compliant with the applicable standards, regulations,
and directives for the countries where the product is marketed. The product is affixed with
regulatory marking and text as necessary for the country/agency. Generally, Information
Technology Equipment (ITE) product compliance is based on IEC and CISPR standards and
their national equivalent such as Product Safety, IEC 60950-1 and European Norm EN 60950-1
or EMC, CISPR 22/CISPR 24 and EN 55022/55024. Dell products have been verified to comply
with the EU RoHS Directive 2011/65/EU. Dell products do not contain any of the restricted
substances in concentrations and applications not permitted by the RoHS Directive.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 20 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
8 Self-Tests
FIPS 140-2 requires that the Module perform self-tests to ensure the integrity of the Module
and the correctness of the cryptographic functionality at start up.
A failure of any of the self-tests panics the Module. The only recovery is to reboot. For
persistent failures, you must reinstall the kernel. See section 9.1 for details.
No operator intervention is required during the running of the self-tests.
8.1 Power-Up Self-Tests
The module performs power-up self-tests at module initialization to ensure that the module is
not corrupted and that the cryptographic algorithms work as expected. The self-tests are
performed without any user intervention.
While the module is performing the power-up tests, services are not available and input or
output is not possible: the module is single-threaded and will not return to the calling
application until the self-tests are completed successfully.
8.1.1 Integrity Tests
The Module performs power-up self tests (at module initialization). Input, output, and
cryptographic functions cannot be performed while the Module is in a self test or error state.
The Module is single-threaded during the self tests and will stop the boot procedure, and
therefore any subsequent operation before any other kernel component can request services
from the Module.
The Crypto Officer with physical or logical access to the Module can run the POST (Power-On
Self-Tests) on demand by power cycling the Module or by rebooting the operating system.
An HMAC SHA-512 calculation is performed on the sha512hmac utility, static Linux kernel
binary and libkcapi library to verify their integrity. The Linux kernel crypto API kernel
components, and any additional code components loaded into the Linux kernel are checked
with the RSA signature verification implementation of the Linux kernel when loading them
into the kernel to confirm their integrity.
NOTE: The fact that the kernel integrity check passed, which requires the loading of
sha512hmac with the self tests implies a successful execution of the integrity and self tests of
sha512hmac (the HMAC is stored in /usr/lib/hmaccalc/sha512hmac.hmac).
With respect to the integrity check of kernel loadable components providing the
cryptographic functionality, the fact that the self test of these cryptographic components are
displayed implies that the integrity checks of each kernel component passed successfully.
The table below summarizes the power-on self tests performed by the module, which includes
the Integrity Test of the module itself as stated above and the Known Answer Test for each
approved cryptographic algorithm.
Algorithm Test
AES KAT, encryption and decryption are tested
separately:
• ECB (128, 192 and 256-bit keys)
• CBC (128, 192 and 256-bit keys)
• CTR (128, 192 and 256-bit keys)
• GCM (128, 192 and 256-bit keys)
• CCM (128-bit keys)
• XTS (128 and 256 bit keys)
CMAC (128 and 256-bit keys)
Triple-DES KAT, encryption and decryption are tested
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 21 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
separately:
• ECB
• CBC
• CTR
CMAC
RSA signature verification KAT (tested as part of the integrity test)
DRBG KAT:
• CTR
• Hash
HMAC
DRBG DRBG health tests as specified in section 11.3 of
NIST SP 800-90Ar1
HMAC SHA-1, -224, -256, -384, -512 KAT
HMAC SHA3-224, -256, -384, -512 KAT
SHA-1, -224, -256, -384, -512 KAT
SHA3-224, -256, -384, -512 KAT
EC Diffie-Hellman primitive "Z"
computation with P-256 curve
KAT
Integrity check HMAC SHA-512, RSA signature verification
Entropy source start up test The module performs SP 800-90B health test as
specified on section 4.2
Table 8: Module Self-Tests
8.2 Conditional Tests
The module performs conditional tests on the cryptographic algorithms shown in the following
table:
Algorithm Test
ENT (NP) The module performs SP 800-90B health tests of RCT and APT as
specified in section 4.4.1 and 4.4.2 of SP 800-90B.
Table 9: Module Conditional Tests
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 22 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
9 Guidance
9.1 Cryptographic Officer Guidance
To operate the Kernel Crypto API module, the operating system must be restricted to a single
operator mode of operation. (This should not be confused with single user mode which is
runlevel 1 on RHEL. This refers to processes having access to the same cryptographic
instance which RHEL ensures cannot happen by the memory management hardware.)
9.1.1 Secure Installation and Startup
Crypto Officers use the Installation instructions to install the Module in their environment.
The version of the RPM containing the FIPS validated module is stated in section 1.1 above.
The integrity of the RPM is automatically verified during the installation and the Crypto Officer
shall not install the RPM file if the RPM tool indicates an integrity error.
9.1.2 FIPS module installation instructions:
9.1.2.1 Recommended method
The system-wide cryptographic policies package (crypto-policies) contains a tool that
completes the installation of cryptographic modules and enables self-checks in accordance
with the requirements of Federal Information Processing Standard (FIPS) Publication 140-2.
We call this step “FIPS enablement”. The tool named fips-mode-setup installs and enables or
disables all the validated FIPS modules and it is the recommended method to install and
configure a RHEL-8 system.
1. To switch the system to FIPS enablement in RHEL 8:
# fips-mode-setup --enable
Setting system policy to FIPS
FIPS mode will be enabled.
Please reboot the system for the setting to take effect.
2. Restart your system:
# reboot
3. After the restart, you can check the current state:
# fips-mode-setup --check
FIPS mode is enabled.
Note: As a side effect of the enablement procedure the fips-mode-enable tool also changes
the system-wide cryptographic policy level to a level named “FIPS”, this level helps
applications by changing configuration defaults to approved algorithms.
9.1.2.2 Manual method
The recommended method automatically performs all the necessary steps.
The following steps can be done manually but are not recommended and are not required if
the systems has been installed with the fips-mode-setup tool:
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 23 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
- create a file named /etc/system-fips, the contents of this file are never checked
- ensure to invoke the command ‘fips-finish-install --complete’ on the installed
system.
- ensure that the kernel boot line is configured with the fips=1 parameter set
- Reboot the system
NOTE: If /boot or /boot/efi resides on a separate partition, the kernel parameter
boot=<boot partition> must be supplied. The partition can be identified with the command
"df | grep boot". For example:
$ df |grep boot
/dev/sda1 233191 30454 190296 14% /boot
The partition of the /boot file system is located on /dev/sda1 in this example.
Therefore the parameter boot=/dev/sda1 needs to be appended to the kernel command line
in addition to the parameter fips=1
9.2 User Guidance
CTR and RFC3686 mode must only be used for IPsec. It must not be used otherwise.
There are three implementations of AES: aes-generic, aesni-intel, and aes-x86_64 on x86_64
machines. The additional specific implementations of AES for the x86 architecture are
disallowed and not available on the test platforms.
When using the Module, the user shall utilize the Linux Kernel Crypto API provided memory
allocation mechanisms. In addition, the user shall not use the function copy_to_user() on any
portion of the data structures used to communicate with the Linux Kernel Crypto API.
Only the cryptographic mechanisms provided with the Linux Kernel Crypto API are considered
for use.
9.2.1 XTS Usage
The XTS mode must only be used for the disk encryption functionality offered by dm-crypt.
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.
9.2.2 GCM Usage
In case the module’s power is lost and then restored, the key used for the AES-GCM
encryption or decryption shall be redistributed.
The module generates the IV internally randomly with an approved SP 800-90B DRBG, which
is compliant with provision 2) of IG A.5.
When a GCM IV is used for decryption, the responsibility for the IV generation lies with the
party that performs the AES-GCM encryption.
9.2.3 Triple-DES Usage
According to IG A.13, the same Triple-DES key shall not be used to encrypt more than 2^16
64-bit blocks of data. It is the user’s responsibility to make sure that the module complies
with this requirement and that the module does not exceed this limit.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 24 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
9.3 Handling Self Test Errors
Self test failure within the Kernel Crypto API module or the dm-crypt kernel component will
panic the kernel and the operating system will not load.
Recover from this error by trying to reboot the system. If the failure continues, you must
reinstall the software package being sure to follow all instructions. If you downloaded the
software verify the package hash to confirm a proper download. Contact Red Hat if these
steps do not resolve the problem.
The Kernel Crypto API module performs a power-on self test that includes an integrity check
and known answer tests for the available cryptographic algorithms.
The kernel dumps self test success and failure messages into the kernel message ring buffer.
Post boot, the messages are moved to /var/log/messages.
Use dmesg to read the contents of the kernel ring buffer. The format of the ringbuffer
(dmesg) output is:
alg: self-tests for %s (%s) passed
Typical messages are similar to "alg: self-tests for xts(aes) (xts(aes-x86_64)) passed" for each
algorithm/sub-algorithm type.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 25 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
10 Mitigation of Other Attacks
The Mitigation of Other attacks security section of FIPS 140-2 is not applicable to the Kernel
Crypto API cryptographic module.
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 26 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Appendix A Glossary and Abbreviations
AES Advanced Encryption Standard
AES-NI Advanced Encryption Standard New Instructions
CAVP Cryptographic Algorithm Validation Program
CBC Cipher Block Chaining
CCM Counter with Cipher Block Chaining Message Authentication Code
CFB Cipher Feedback
CMAC Cipher-based Message Authentication Code
CMVP Cryptographic Module Validation Program
CSP Critical Security Parameter
CTR Counter Mode
DES Data Encryption Standard
DSA Digital Signature Algorithm
DRBG Deterministic Random Bit Generator
ECB Electronic Code Book
ECC Elliptic Curve Cryptography
ENT SP 800-90B compliant entropy
FFC Finite Field Cryptography
FIPS Federal Information Processing Standards Publication
FSM Finite State Model
GCM Galois Counter Mode
HMAC Hash Message Authentication Code
KAS Key Agreement Schema
KAT Known Answer Test
MAC Message Authentication Code
NIST National Institute of Science and Technology
OFB Output Feedback
O/S Operating System
PAA Processor Algorithm Acceleration
PR Prediction Resistance
RNG Random Number Generator
RSA Rivest, Shamir, Addleman
SHA Secure Hash Algorithm
SHS Secure Hash Standard
XTS XEX-based Tweaked-codebook mode with ciphertext Stealing
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 27 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Appendix B References
FIPS180-4 Secure Hash Standard (SHS)
August 2015
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-90Ar1.pdf
FIPS186-4 Digital Signature Standard (DSS)
July 2013
https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf
FIPS197 Advanced Encryption Standard
November 2001
https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.197.pdf
FIPS198-1 The Keyed Hash Message Authentication Code (HMAC)
July 2008
https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.198-1.pdf
RFC3394 Advanced Encryption Standard (AES) Key Wrap Algorithm
September 2002
http://www.ietf.org/rfc/rfc3394.txt
RFC5649 Advanced Encryption Standard (AES) Key Wrap with Padding
Algorithm
September 2009
http://www.ietf.org/rfc/rfc5649.txt
SP800-38A NIST Special Publication 800-38A - Recommendation for Block
Cipher Modes of Operation Methods and Techniques
December 2001
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-
38a.pdf
SP800-38B NIST Special Publication 800-38B - Recommendation for Block
Cipher Modes of Operation: The CMAC Mode for Authentication
May 2005
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-38b.pdf
SP800-38C NIST Special Publication 800-38C - Recommendation for Block
Cipher Modes of Operation: the CCM Mode for Authentication and
Confidentiality
July 2007
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-
38c.pdf
SP800-38D 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
SP800-38E NIST Special Publication 800-38E - Recommendation for Block
Cipher Modes of Operation: The XTS AES Mode for Confidentiality on
Storage Devices
January 2010
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-
38e.pdf
SP800-38F NIST Special Publication 800-38F - Recommendation for Block
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 28 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.
Red Hat Enterprise Linux 8 Kernel Crypto API Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy
Cipher Modes of Operation: Methods for Key Wrapping
December 2012
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-38F.pdf
SP800-56A NIST Special Publication 800-56A Revision 3 - Recommendation for
Pair Wise Key Establishment Schemes Using Discrete Logarithm
Cryptography
April 2018
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf
SP800-56C NIST Special Publication 800-56A Revision 1 - Recommendation for
Key Derivation in Key-Establishment Schemes
April 2018
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Cr1.pdf
SP800-67 NIST Special Publication 800-67 Revision 2 - Recommendation for
the Triple Data Encryption Algorithm (TDEA) Block Cipher
November 2017
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-67r2.pdf
SP800-90A 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
SP800-90B 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
SP800-108 NIST Special Publication 800-108 - Recommendation for Key
Derivation Using Pseudorandom Functions
October 2009
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-
108.pdf
SP800-131A NIST Special Publication 800-131A Revision 2 - Transitions:
Recommendation for Transitioning the Use of Cryptographic
Algorithms and Key Lengths
March 2019
https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar2.pdf
© 4/12/22 Red Hat(R), Inc. / atsec information security corporation Page 29 of 29
This document can be reproduced and distributed only whole and intact, including this copyright notice.