Oracle Database 19c STIG Version Comparison

There are 13 differences between versions v1 r2 (July 2, 2025) (the "left" version) and v1 r4 (Jan. 5, 2026) (the "right" version).

Check O19C-00-000100 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

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

Check Content

Retrieve the settings for concurrent sessions for each profile with the query: SELECT query: SELECT * con_id, inherited, limit FROM SYS.DBA_PROFILES sys.cdb_profiles WHERE RESOURCE_NAME 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, sessions (or the database maximum number of sessions) for the user type, this is a finding. 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.

Discussion

Database management includes the ability to control the number of users and user sessions using a database management system (DBMS). Unlimited concurrent connections to the DBMS could allow a successful denial-of-service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks. This requirement addresses concurrent session control for a single account. It does not address concurrent sessions by a single user via multiple system accounts; and it does not deal with the total number of sessions across all accounts. The capability to limit the number of concurrent sessions per user must be configured in or added to the DBMS (for example, by modifying use user database profiles. Note of a logon trigger), when this is technically feasible. Note that it is not sufficient to limit sessions via a web server or application server alone, because legitimate users and adversaries can potentially connect to the DBMS by other means. The organization must will need to define the maximum number of concurrent sessions by account user type, by account, or a combination thereof. In deciding on the appropriate number, it is important to consider the work requirements of the various types of users. For example, two might be an acceptable limit for general users accessing the database via an application; but 10 three might be too few for a database administrator using a database management GUI tool, where each query tab and navigation pane may count as a separate session. (Sessions session: An account associated with a connection pool might require hundreds or thousands. (Sessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.)

Fix

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 the profile parameters. Oracle recommends that this profile be customized with any site-specific requirements and assigned to all users through the creation of user type specific profiles such as (Single-Session, Administrators, Application Connection Pool) where applicable. applicable. Note: Note: If it remains necessary to create 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 customized replacement container database for CDB$ROOT and, potentially, the password validation function, ORA12C_STIG_VERIFY_FUNCTION can be used as a starting point to verify password complexity. The defaults for each PDB. Set ORA_STIG_PROFILE are set as follows: Resource Name Limit --------------------------- ----------------------- COMPOSITE_LIMIT DEFAULT SESSIONS_PER_USER DEFAULT CPU_PER_SESSION DEFAULT CPU_PER_CALL DEFAULT LOGICAL_READS_PER_SESSION DEFAULT LOGICAL_READS_PER_CALL DEFAULT IDLE_TIME 15 CONNECT_TIME DEFAULT PRIVATE_SGA DEFAULT FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LIFE_TIME 60 PASSWORD_REUSE_TIME 365 PASSWORD_REUSE_MAX 10 PASSWORD_VERIFY_FUNCTION ORA12C_STIG_VERIFY_FUNCTION PASSWORD_LOCK_TIME UNLIMITED PASSWORD_GRACE_TIME 5 The recommended value for the SESSIONS_PER_USER setting in Oracle 19c is 10 or less. Limiting the number of concurrent sessions for each profile can help prevent memory resource exhaustion from poorly formed requests, denial-of-service attacks, and a single user tying up all resources. Change the value of SESSIONS_PER_USER (along with the following SQL statement, as required. ALTER PROFILE <profile_name> LIMIT SESSIONS_PER_USER <integer>; other parameters, where relevant) from UNLIMITED to DOD-compliant, site-specific requirements for the ORA_STIG_PROFILE and then assign users to the ORA_STIG_PROFILE profile.