Detections
Analytics

O19C-00-000300 - Oracle Database must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions.

Session termination ends all processes associated with a user's logical session except those batch processes/jobs that are specifically created by the user (i.e., session owner) to continue after the session is terminated.

Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use.

This capability is typically reserved for specific cases where the system owner, data owner, or organization requires additional assurance.

Satisfies: SRG-APP-000295-DB-000305, SRG-APP-000296-DB-000306

Solution

Configure the database management system (DBMS) to automatically terminate a user session after organization-defined conditions, 15 minutes, or a trigger event requiring session termination.

To terminate a session after a certain amount of time independent of the consumed resources needed by other users, then set the MAX_IDLE_TIME initialization parameter. The MAX_IDLE_TIME parameter specifies the maximum number of minutes a session can be idle. After the specified amount of time, MAX_IDLE_TIME kills sessions.

ALTER SYSTEM SET max_idle_time = 15
COMMENT = 'Altered <date> for STIG compliance' -- self documenting
SID = '*' -- required for RAC
SCOPE = BOTH;

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_Database_19c_V1R4_STIG.zip

Item Details

References: CAT|II, CCI|CCI-002361, CCI|CCI-002363, Rule-ID|SV-270497r1167730_rule, STIG-ID|O19C-00-000300, Vuln-ID|V-270497

Plugin: OracleDB

Control ID: d9fca02ae340d721da5baf7e403e112b3bbb22285f68b2cfbcad054e2fa6c6bb