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

Oracle Database must limit the number of concurrent sessions for each system account to an organization-defined number of sessions.

DISA Rule

SV-270495r1167748_rule

Vulnerability Number

V-270495

Group Title

SRG-APP-000001-DB-000031

Rule Version

O19C-00-000100

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Limit concurrent connections for each system account to a number less than or equal to the organization-defined number of sessions using the following SQL. Create profiles that conform to the requirements. Assign users to the appropriate profile.

The user profile, ORA_STIG_PROFILE, has been provided with Oracle 19c to satisfy the STIG requirements pertaining to profile parameters. Oracle recommends that this profile be customized with requirements and assigned to all users through the creation of user type specific profiles such as (Single-Session, Administrators, Application Connection Pool) where applicable.

Note: The ORA_STIG_PROFILE limit for SESSIONS_PER_USER is DEFAULT which is, on installation, not compliant and must be configured for each database and in a container database for CDB$ROOT and, potentially, for each PDB.

Set concurrent sessions for each profile with the following SQL statement, as required.

ALTER PROFILE <profile_name> LIMIT SESSIONS_PER_USER <integer>;

Check Contents

Retrieve the settings for concurrent sessions for each profile with the query:

SELECT con_id, inherited, limit FROM sys.cdb_profiles WHERE resource_name = 'SESSIONS_PER_USER';

If the DBMS settings for concurrent sessions for each profile are greater than the site-specific maximum number of sessions (or the database maximum number of sessions) for the user type, this is a finding.

The reason for "site-specific" is because two different databases at different "sites" could have very different requirements.
Also, two different databases at the same "site" (data center) could have very different requirements.

Vulnerability Number

V-270495

Documentable

False

Rule Version

O19C-00-000100

Severity Override Guidance

Retrieve the settings for concurrent sessions for each profile with the query:

SELECT con_id, inherited, limit FROM sys.cdb_profiles WHERE resource_name = 'SESSIONS_PER_USER';

If the DBMS settings for concurrent sessions for each profile are greater than the site-specific maximum number of sessions (or the database maximum number of sessions) for the user type, this is a finding.

The reason for "site-specific" is because two different databases at different "sites" could have very different requirements.
Also, two different databases at the same "site" (data center) could have very different requirements.

Check Content Reference

M

Target Key

5672