Encryption
Transport Layer Security (TLS) 1.3 Now Supported in Oracle Database
Transport Layer Security (TLS) version 1.3 is supported in Database 23ai. TLS 1.3 is the latest and most secure TLS protocol to protect network connections to and from an Oracle database.
Because TLS 1.3 handles initial session setup more efficiently than prior TLS versions, users moving to TLS 1.3 should see improvements in TLS performance, particularly for applications that frequently connect and reconnect to the database. TLS 1.3 also implements newer, more secure cipher suites that improve confidentiality of data in transit.
Strict DN Matching with Both Listener and Server Certificates
The behavior of the SSL_SERVER_DN_MATCH parameter has changed. Previously, Oracle Database performed the DN check only with the database server certificate, and both the HOSTNAME and the SERVICE_NAME setting in the connect string could be used for a partial DN match.
With Oracle Database 23ai, Oracle Database checks both the listener and server certificates. In addition, the SERVICE_NAME setting in the connect string is not used to check during a partial DN match. The HOSTNAME setting can still be used for partial DN matching with the certificate DN and subject alternative name (SAN), on both the listener and server certificates.
When set to TRUE, the SSL_ALLOW_WEAK_DN_MATCH parameter reverts SSL_SERVER_DN_MATCH to the behavior earlier than release 23ai and enables DN matching to only check the database server certificate (but not the listener) and enable the service name to be used for partial DN matching.
DN matching with both the listener and server certificates provides better security to ensure that the client is connecting to the correct database server. The service name setting is also removed from SSL_SERVER_DN_MATCH for better security and partial DN matching can still be performed with the HOSTNAME connect string parameter with the he certificate DN and subject alternative name (SAN) matching.
The SSL_ALLOW_WEAK_DN_MATCH, though new to this release, is marked as deprecated because it is considered a temporary solution to enable the behavior of SSL_SERVER_DN_MATCH prior to release 23ai.
Simplified Transport Layer Security Configuration
The Transport Layer Security (TLS) configuration between the database client and server has been simplified with streamlined parameters, performance improvements, and an additional parameter to find a wallet. Older TLS protocols have also been removed.
These changes improve security and make it easier to implement TLS.
Ability to Configure Transport Layer Security Connections Without Client Wallets
An Oracle Database client is no longer required to provide a wallet to hold well-known CA root certificates if they are available in the local system. The Oracle Database wallet search order determines the location (Windows (Microsoft Certificate Store) or Linux) of these certificates in the local system.
Transport Layer Security (TLS) requires either one-way authentication or two-way authentication. In one-way TLS authentication, which is commonly used for HTTPS connections, you will no longer need to install and configure a client wallet to hold the server's CA certificate as long as it is already available in the local system. If the server's CA certificate is not installed in the local systems, client wallet is still required. Starting in this release, you no longer need to install and configure a wallet to hold a well-known root certificate if it is already available in the local system.
This feature greatly simplifies the Oracle Database client installation and the use of TLS protocol to encrypt Oracle Database client-server communications.
New sqlnet.ora Parameter to Prevent the Use of Deprecated Cipher Suites
You can block the use of deprecated cipher suites by setting the SSL_ENABLE_WEAK_CIPHERS sqlnet.ora parameter to FALSE.
Removing the ability to use older, less secure cipher suites improves protection for data in-motion between the database.
AES-XTS Encryption Mode Support for TDE Tablespace Encryption
Transparent Database Encryption (TDE) tablespace encryption now supports Advanced Encryption Standard (AES) XTS (XEX-based mode with ciphertext stealing mode) in CREATE TABLESPACE statements. Earlier versions of Oracle Database TDE used AES-CFB cipher mode.
AES-XTS provides improved security and better performance, especially on platforms where TDE can take advantage of parallel processing and specialized instructions built into processor hardware.
Changes for TDE Encryption Algorithms and Modes
The default encryption algorithm for both TDE column encryption and TDE tablespace encryption is now AES256. The previous default for TDE column encryption was AES192. For TDE tablespace encryption, the default was AES128.
The decryption libraries for the GOST and SEED algorithms are deprecated. New keys cannot use these algorithms. The encryption libraries for both of these libraries are desupported.
The column encryption mode is now Galois/Counter mode (GCM) instead of cipher block chaining (CBC), and the tablespace keys are now used in tweakable block ciphertext stealing (XTS) operating mode instead of cipher feedback (CFB).
The Oracle Recovery Manager (RMAN) integrity check for column encryption keys now uses SHA512 instead of SHA1.
The keys for Oracle RMAN and column keys are now derived from SHA512/AES for key generation. In previous releases, they used SHA-1/3DES as a pseudo-random function.
These enhancements enable your Oracle Database environment to use the latest, most secure algorithms and encryption modes.
Improved and More Secure Local Auto-Login Wallets
A local auto-login wallet is now more tightly bound to the host where it was created or modified (both bare metal and virtual). The local auto-login process is also more secure, does not require additional deployment requirements, and does not require root access.
Local auto-login wallets are more secure now and support both bare metal and virtual environments.
This enhancement also applies to Transparent Data Encryption (TDE) local auto-login keystores.
Changes to DBMS_CRYPTO
The following updates have been made to the DBMS_CRYPTO package:
- Added XTS mode to AES algorithms and set it as the default mode
- Added SHA-3
- Added SM2/3/4
Customers can use the latest cryptographic features with Oracle Database.
New Parameter to Control the TDE Rekey Operations for Oracle Data Guard
You now can use the DB_RECOVERY_AUTO_REKEY initialization parameter for Oracle Data Guard environments. DB_RECOVERY_AUTO_REKEY controls whether an Oracle Data Guard standby database recovery operation automatically performs the corresponding tablespace rekey when it encounters a redo that says the primary database has performed a tablespace rekey operation.
This feature is useful for standby deployments with large tablespaces whose users must perform an online TDE conversion.