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

Oracle Database must ensure users are authenticated with an individual authenticator prior to using a shared authenticator.

DISA Rule

SV-270559r1068298_rule

Vulnerability Number

V-270559

Group Title

SRG-APP-000148-DB-000103

Rule Version

O19C-00-013700

Severity

CAT II

CCI(s)

• CCI-000764 - Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.

Weight

10

Fix Recommendation

Configure the DBMS, OS, and/or enterprise-level authentication/access mechanism to require individual authentication prior to authentication for shared account access.

If appropriate, install Oracle Access Manager to provide multifactor authentication of applications front-ending Oracle Databases and using shared accounts. After installation, use x509 Authentication modules provided out of the box.

Check Contents

Review database management system (DBMS) settings, OS settings, and/or enterprise-level authentication/access mechanism settings to determine whether shared accounts exist. If shared accounts do not exist, this is Not Applicable.

Review DBMS settings to determine if individual authentication is required before shared authentication.

If shared authentication does not require prior individual authentication, this is a finding.

If using Oracle Access Manager:
Verify the Authentication Module is set up properly:
1. Go to the Oracle Access Manager Home Screen and click the Policy Configuration tab. Select the X509Scheme.
2. Ensure the Authentication Module option is set to X509Plugin.

Verify the Authentication policy is using the x509Scheme:
1. Go to Oracle Access Manager Home Screen and click the Policy Configuration tab.
2. Select Application Domains. Select Search.
3. Select the application domain protecting the Oracle Database.
4. Select the Authentication Policies tab and click Protected Resource Policy.
5. Make sure the Authentication Scheme is set to x509Scheme.

Vulnerability Number

V-270559

Documentable

False

Rule Version

O19C-00-013700

Severity Override Guidance

Review database management system (DBMS) settings, OS settings, and/or enterprise-level authentication/access mechanism settings to determine whether shared accounts exist. If shared accounts do not exist, this is Not Applicable.

Review DBMS settings to determine if individual authentication is required before shared authentication.

If shared authentication does not require prior individual authentication, this is a finding.

If using Oracle Access Manager:
Verify the Authentication Module is set up properly:
1. Go to the Oracle Access Manager Home Screen and click the Policy Configuration tab. Select the X509Scheme.
2. Ensure the Authentication Module option is set to X509Plugin.

Verify the Authentication policy is using the x509Scheme:
1. Go to Oracle Access Manager Home Screen and click the Policy Configuration tab.
2. Select Application Domains. Select Search.
3. Select the application domain protecting the Oracle Database.
4. Select the Authentication Policies tab and click Protected Resource Policy.
5. Make sure the Authentication Scheme is set to x509Scheme.

Check Content Reference

M

Target Key

5672