Oracle Database FIPS 140-2 Settings

E Oracle Database FIPS 140-2 Settings

Oracle supports the Federal Information Processing Standard (FIPS) standard for 140-2.

About the Oracle Database FIPS 140-2 Settings
The Federal Information Processing Standard (FIPS) standard, 140-2, is a U.S. government standard that defines cryptographic module security requirements.
Configuring FIPS 140-2 for Transparent Data Encryption and DBMS_CRYPTO
The DBFIPS_140 initialization parameter configures FIPS mode.
Configuration of FIPS 140-2 for Secure Sockets Layer
The SSLFIPS_140 parameter configures Secure Sockets Layer (SSL).
Postinstallation Checks for FIPS 140-2
After you configure the FIPS 140-2 settings, you must verify permissions in the operating system.
Verifying FIPS 140-2 Connections
To check if FIPS mode is enabled for SSL, you can enable tracing in the sqlnet.ora file.
Managing Deprecated Weaker Algorithm Keys
In Oracle Database release 21c, several algorithms for both FIPS and non-FIPS have been deprecated.

Parent topic: Appendixes

E.1 About the Oracle Database FIPS 140-2 Settings

The Federal Information Processing Standard (FIPS) standard, 140-2, is a U.S. government standard that defines cryptographic module security requirements.

The FIPS 140-2 cryptographic libraries are designed to protect data at rest and in transit over the network.

Oracle Database uses these cryptographic libraries for Secure Sockets Layer (SSL), Transparent Data Encryption (TDE), and DBMS_CRYPTO PL/SQL package.

To verify the current status of the certification, you can find information at the Computer Security Resource Center (CSRC) Web site address from the National Institute of Standards and Technology:

http://csrc.nist.gov/groups/STM/cmvp/validation.html

You can find information specific to FIPS by searching for Validated FIPS 140 Cryptographic Modules. The security policy, which is available on this site upon successful certification, includes requirements for secure configuration of the host operating system.

The Oracle Database FIPS settings are meant to enforce the use of FIPS-approved algorithms for the Oracle database only. The use of third-party vendor software with Oracle Database running in FIPS mode must use FIPS-approved algorithms or else the vendor software will encounter failures.

Parent topic: Oracle Database FIPS 140-2 Settings

E.2 Configuring FIPS 140-2 for Transparent Data Encryption and DBMS_CRYPTO

The DBFIPS_140 initialization parameter configures FIPS mode.

To configure Transparent Data Encryption and the DBMS_CRYPTO PL/SQL package program units to run in FIPS mode, set the DBFIPS_140 initialization parameter to TRUE.
The effect of this parameter depends on the platform.
Restart the database.

Table E-1 describes how the DBFIPS_140 parameter affects various platforms.

Table E-1 How the DBFIPS_140 Initialization Parameter Affects Platforms

Platform	Effect of Setting DBFIPS_140 to TRUE or FALSE
Linux or Windows on Intel x86_64	`TRUE`: TDE and `DBMS_CRYPTO` program units use Micro Edition Suite (MES) 4.5 FIPS mode, which uses RSA BSAFE Crypto-C Micro Edition (CCME) 4.1.4 `FALSE`: TDE and `DBMS_CRYPTO` program units use Intel Performance Primitives (IPP)
Solaris 11.1+ on either SPARC T-series or Intel x86_64	`TRUE`: TDE and `DBMS_CRYPTO` program units use Micro Edition Suite (MES) 4.5 FIPS mode, which uses RSA BSAFE Crypto-C Micro Edition (CCME) 4.1.4 `FALSE`: TDE and `DBMS_CRYPTO` program units use Solaris Cryptographic Framework (SCF)/UCrypto (separately validated for FIPS 140)
Other operating systems or hardware	`TRUE`: TDE and `DBMS_CRYPTO` program units use MES 4.5 FIPS mode, which uses RSA BSAFE Crypto-C Micro Edition (CCME) 4.1.4 `FALSE`: TDE and `DBMS_CRYPTO` program units use MES 4.5 non-FIPS mode

Be aware that setting DBFIPS_140 to TRUE and thus using the underlying library in FIPS mode incurs a certain amount of overhead when the library is first loaded. This is due to the verification of the signature and the execution of the self tests on the library. Once the library is loaded, then there is no other impact on performance.

Related Topics

Oracle Database Reference

Parent topic: Oracle Database FIPS 140-2 Settings

E.3 Configuration of FIPS 140-2 for Secure Sockets Layer

The SSLFIPS_140 parameter configures Secure Sockets Layer (SSL).

Configuring the SSLFIPS_140 and SSLFIPS_LIB Parameters for Secure Sockets Layer
To configure FIPS 140-2 for SSL, you must set the SSLFIPS_140 parameter. If you are using the Oracle Instant Client, then you must set the SSLFIPS_LIB parameter as well.
Approved SSL Cipher Suites for FIPS 140-2
A cipher suite is a set of authentication, encryption, and data integrity algorithms that exchange messages between network nodes.

Parent topic: Oracle Database FIPS 140-2 Settings

E.3.1 Configuring the SSLFIPS_140 and SSLFIPS_LIB Parameters for Secure Sockets Layer

To configure FIPS 140-2 for SSL, you must set the SSLFIPS_140 parameter. If you are using the Oracle Instant Client, then you must set the SSLFIPS_LIB parameter as well.

The SSLFIPS_140 parameter configures the Secure Sockets Layer (SSL) adapter to run in FIPS mode. SSLFIPS_LIB sets the location of the FIPS library.

Ensure that the fips.ora file is either located in the $ORACLE_HOME/ldap/admin directory, or is in a location pointed to by the FIPS_HOME environment variable.
In the fips.ora file, set the SSLFIPS_140 and SSLFIPS_LIB parameters.
- Set SSLFIPS_140 to TRUE so that the SSL adapter can run in FIPS mode. For example:
```
SSLFIPS_140=TRUE
```
  This parameter is FALSE by default.
- If you are using Oracle Instant Client, then set SSLFIPS_LIB to the location of the FIPS library. For example:
```
SSLFIPS_LIB=$ORACLE_HOME/lib
```
Repeat this procedure in any Oracle Database home for any database server or client.

When you set SSLFIPS_140 to TRUE, Secure Sockets Layer cryptographic operations take place in the embedded RSA/Micro Edition Suite (MES) library in FIPS mode. These cryptographic operations are accelerated by the CPU when hardware acceleration is available and properly configured in the host hardware and software.

If you set SSLFIPS_140 to FALSE, then Secure Sockets Layer cryptographic operations take place in the embedded RSA/Micro Edition Suite (MES) library in non-FIPS mode, and as with the TRUE setting, the operations are accelerated if possible.

For native encryption, this behavior of cryptographic operations landing in RSA/Micro Edition Suite (MES) and being accelerated is similar to the above, except that it is determined by the FIPS_140 setting in sqlnet.ora (instead of the SSL_FIPS140 setting in fips.ora).

Note:

The SSLFIPS_140 parameter replaces the SQLNET.SSLFIPS_140 parameter used in Oracle Database 10g release 2 (10.2). You must set the parameter in the fips.ora file, and not the sqlnet.ora file.

Parent topic: Configuration of FIPS 140-2 for Secure Sockets Layer

E.3.2 Approved SSL Cipher Suites for FIPS 140-2

A cipher suite is a set of authentication, encryption, and data integrity algorithms that exchange messages between network nodes.

During an SSL handshake, for example, the two nodes negotiate to see as to which cipher suite they will use when transmitting messages back and forth.

Configuring Specific Cipher Suites

Oracle Database SSL cipher suites are automatically set to FIPS approved cipher suites. If you want to configure specific cipher suites, then you can do so by setting the SSL_CIPHER_SUITES parameter in the sqlnet.ora or the listener.ora file.

SSL_CIPHER_SUITES=(SSL_cipher_suite1[,SSL_cipher_suite2[,..]])

You can also use Oracle Net Manager to set this parameter on the server and the client.

If a specific cipher suite is not specified, then Oracle Database will use the strongest cipher suite common to both the database server and client. The priority order of cipher suites to be selected are in order as they are listed in the preferred and less preferred cipher lists below. Oracle Database will not select 3DES cipher suites automatically due to their weakness; they must be configured explicitly.

Preferred Cipher Suites

The following cipher suites are approved for FIPS validation if you are using Transport Layer Security (TLS) version 1.2:

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

The following cipher suites are approved for FIPS validation if you are using Transport Layer Security (TLS) version 1, 1.1, or 1.2:

TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

Less Preferred Cipher Suites

With configuring version TLS 1.2:

TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256

When configuring version 1.0, 1.1, or 1.2:

TLS_RSA_WITH_AES_256_CBC_SHA

3DES-Based Cipher Suites

Oracle does not recommend 3DES-based cipher suites because of a weakness in their design. Oracle Database release 21c and later contains support for the following 3DES-based cipher suites. However, they are not enabled by default and must be explicitly configured through the SSL_CIPHER_SUITES parameter in the sqlnet.ora or the listener.ora file.

TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA

E.4 Postinstallation Checks for FIPS 140-2

After you configure the FIPS 140-2 settings, you must verify permissions in the operating system.

The permissions are as follows:

Set execute permissions on all Oracle executable files to prevent the execution of Oracle Cryptographic Libraries by users who are unauthorized to do so, in accordance with the system security policy.
Set read and write permissions on all Oracle executable files to prevent accidental or deliberate reading or modification of Oracle Cryptographic Libraries by any user.

To comply with FIPS 140-2 Level 2 requirements, in the security policy, include procedures to prevent unauthorized users from reading, modifying or executing Oracle Cryptographic Libraries processes and the memory they are using in the operating system.

Parent topic: Oracle Database FIPS 140-2 Settings

E.5 Verifying FIPS 140-2 Connections

To check if FIPS mode is enabled for SSL, you can enable tracing in the sqlnet.ora file.

You can find FIPS self-test messages in the trace file.

Add the following lines to sqlnet.ora to enable tracing:

trace_directory_server=trace_directory
trace_file_server=trace_file
trace_level_server=trace_level

For example:

trace_directory=/private/oracle/owm
trace_file_server=fips_trace.trc
trace_level_server=6

To check if FIPS mode is enabled for TDE and DBMS_CRYPTO, log into SQL*Plus and run the following command:
```
SHOW PARAMETER DBFIPS_140
```

Trace level 6 is the minimum trace level required to check the results of the FIPS self-tests.

Parent topic: Oracle Database FIPS 140-2 Settings

E.6 Managing Deprecated Weaker Algorithm Keys

In Oracle Database release 21c, several algorithms for both FIPS and non-FIPS have been deprecated.

The security strength of the cipher algorithms have been changed in Oracle Database 21c with the introduction of the newest RSA BSAFE Micro Edition Suite (MES) v 4.5. The following cipher algorithms are deprecated:

For FIPS mode
- The FIPS default protect strength of 80 has been deprecated. This strength is still available, but will not be the default protect strength in the future. The new default protect strength for FIPS mode will be 112.
  - When the default FIPS protect strength changes from 80 to 112 with a later release, you can still revert to using the older, less secure FIPS protect strength 80 by setting a parameter.
- Diffie Hellman and Digital Signature Algorithm (DH/DSA) with 1024 key size is deprecated. The new minimum supported key size will be 2048. The 1024 key size support will remain available when the default protect strength will be changed to 112 bits of security strength (equivalent to 2048 key size), the process strength remains at 80 bits of security strength (equivalent to 1024 key size).
For non-FIPS mode
- Both protect and process strength 0 (RSA key length 512) are deprecated. By default, both protect and process strength are now 80. Protect and process strength 0 (RSA key 512 and equivalent) is still available, but not recommended for use.

Oracle recommends that you find existing use of RSA 512 /1024 key sizes (along with ECC/DH/DSA equivalents) and replace these with RSA 2048 key size and equivalents.

You can find more information about supported key sizes and lengths and their equivalent RSA, ECC and DH/DSA key lengths and named curves here:

The following tables describe protect strength and process strength of various encryption keys.

Protect strength refers to the key size that is required for following the operations:
- Encryption
- Key agreement
- Key wrapping
- Signing
Process strength refers to the key size that is required for the following operations:
- Decryption
- Key unwrapping
- Verifying a signature

You can use the orapki command line utility to create signed certificates, manage Oracle wallets, and manage certificate revocation lists. It has the same default key sizes as listed in the following tables.

FIPS Default Setting (Starting with Oracle Database 21c)

Table E-2 FIPS Default Setting (Starting with Oracle Database 21c)

Algorithm Key Type	Protect Strength	Process Strength
-	Default Protect strength: 80 (was 0)* Protect strength: 0 not available	Default Process strength: 80 (was 0) Process strength: 0 not available
Default RSA	1024 key size (512 not available)	1024 key size (512 not available)
Default ECC (Elliptic Curve Cryptography)	ECC curves with minimum ECC curve key length 160, ECC names curves P192, K163 and B163 and above (lower protect strength not available)	ECC curves with minimum ECC curve key length 160, ECC names curves P192, K163 and B163 and above (lower protect strength not available)
Default DH/DSA (Diffie Hellman, Digital Signature Algorithm)	1024 key size (512 not available)	1024 key size (512 not available)

* The default FIPS protect strength of 80 is deprecated and will be strengthened to 112. To revert the protect strength back to 80, set the ORACLE_MIN_KEY_STRENGTH_SUPPORT_FIPS parameter in the fips.ora file to 80. This file is either in $ORACLE_HOME/ldap/admin or in a location pointed to by the environment variable FIPS_HOME.

Non-FIPS Default Setting (Starting with Oracle Database 21c)

Table E-3 Non-FIPS Default Setting (Starting with Oracle Database 21c)

Algorithm Key Type	Protect Strength	Process Strength
-	Default protect strength: 80 (was 0) Protect strength: 80 (default), 0 (available)	Default process strength: 80 (was 0) Process strength: 80 (default), 0 (available)
Default RSA	1024 key size (was 512, which is still available)	1024 key size (was 512, which is still available)
Default ECC (Elliptic Curve Cryptography)	ECC curves with minimum ECC curve key length 160, ECC names curves P192, K163 and B163 and above (lower protect strength available)	ECC curves with minimum ECC curve key length 160, ECC names curves P192, K163 and B163 and above (lower process strength available)
Default DH/DSA (Diffie Hellman, Digital Signature Algorithm)	1024 key size (was 512 which is still available)	1024 key size (was 512 which is still available

Parent topic: Oracle Database FIPS 140-2 Settings