STIGQter: STIG Summary: Oracle Database 19c Security Technical Implementation Guide Version: 1 Release: 5 Benchmark Date: 01 Apr 2026:

Oracle Database must include only approved trust anchors in trust stores or certificate stores managed by the organization.

DISA Rule

SV-270589r1136927_rule

Vulnerability Number

V-270589

Group Title

SRG-APP-000910-DB-000300

Rule Version

O19C-00-020400

Severity

CAT II

CCI(s)

• CCI-004909 - Include only approved trust anchors in trust stores or certificate stores managed by the organization.

Weight

10

Fix Recommendation

Configure the DBMS to include only approved trust anchors in trust stores or certificate stores managed by the organization.

Configure the database to support TLS protocols and the Oracle Wallet to store authentication and signing credentials, including private keys.

Check Contents

If all accounts are authenticated by the OS or an enterprise-level authentication/access mechanism and not by Oracle, this is not a finding.

Verify the database management system (DBMS) is configured to include only approved trust anchors in trust stores or certificate stores managed by the organization.

If trust stores or certification paths are not being validated back to a trust anchor, this is a finding.

The database supports PKI-based authentication by using digital certificates over Transport Layer Security (TLS) in addition to the native encryption and data integrity capabilities of these protocols.

Oracle provides a complete PKI that is based on RSA Security, Inc., Public-Key Cryptography Standards, and interoperates with Oracle servers and clients. The database uses a wallet that is a container to store authentication and signing credentials, including private keys, certificates, and trusted certificates needed by TLS. In an Oracle environment, every entity that communicates over TLS must have a wallet containing an X.509 version 3 certificate, private key, and list of trusted certificates.

If the $ORACLE_HOME/network/admin/sqlnet.ora contains the following entries, TLS is installed.

WALLET_LOCATION = (SOURCE=
(METHOD = FILE)
(METHOD_DATA =
DIRECTORY=/wallet)

SSL_CIPHER_SUITES=(SSL_cipher_suiteExample)
SSL_VERSION = 1.1 or 1.2
SSL_CLIENT_AUTHENTICATION=TRUE

Vulnerability Number

V-270589

Documentable

False

Rule Version

O19C-00-020400

Severity Override Guidance

If all accounts are authenticated by the OS or an enterprise-level authentication/access mechanism and not by Oracle, this is not a finding.

Verify the database management system (DBMS) is configured to include only approved trust anchors in trust stores or certificate stores managed by the organization.

If trust stores or certification paths are not being validated back to a trust anchor, this is a finding.

The database supports PKI-based authentication by using digital certificates over Transport Layer Security (TLS) in addition to the native encryption and data integrity capabilities of these protocols.

Oracle provides a complete PKI that is based on RSA Security, Inc., Public-Key Cryptography Standards, and interoperates with Oracle servers and clients. The database uses a wallet that is a container to store authentication and signing credentials, including private keys, certificates, and trusted certificates needed by TLS. In an Oracle environment, every entity that communicates over TLS must have a wallet containing an X.509 version 3 certificate, private key, and list of trusted certificates.

If the $ORACLE_HOME/network/admin/sqlnet.ora contains the following entries, TLS is installed.

WALLET_LOCATION = (SOURCE=
(METHOD = FILE)
(METHOD_DATA =
DIRECTORY=/wallet)

SSL_CIPHER_SUITES=(SSL_cipher_suiteExample)
SSL_VERSION = 1.1 or 1.2
SSL_CLIENT_AUTHENTICATION=TRUE

Check Content Reference

M

Target Key

5672