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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-270497	SRG-APP-000295-DB-000305	O19C-00-000300	SV-270497r1064769_rule	2025-02-14	1

Description
This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are 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

Description

This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are 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

ℹ️ Check
Review system documentation to obtain the organization's definition of circumstances requiring automatic session termination. If the documentation explicitly states that such termination is not required or is prohibited, this is not a finding. If no documentation exists or an automatic session termination time is not explicitly defined, assume a time of 15 minutes. To check the max_idle_time set, run the following query: SELECT VALUE FROM V$PARAMETER WHERE NAME = 'max_idle_time'; If the value returned does not match the documented requirement (or 15 when none is specified), this is a finding.

ℹ️ Check

Review system documentation to obtain the organization's definition of circumstances requiring automatic session termination. If the documentation explicitly states that such termination is not required or is prohibited, this is not a finding. If no documentation exists or an automatic session termination time is not explicitly defined, assume a time of 15 minutes. To check the max_idle_time set, run the following query: SELECT VALUE FROM V$PARAMETER WHERE NAME = 'max_idle_time'; If the value returned does not match the documented requirement (or 15 when none is specified), this is a finding.

✔️ Fix
Configure the database management system (DBMS) to automatically terminate a user session after organization-defined conditions or trigger events requiring session termination. To terminate 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 that a session can be idle. After the specified amount of time, MAX_IDLE_TIME kills sessions. ALTER SYSTEM SET max_idle_time=15;

✔️ Fix

Configure the database management system (DBMS) to automatically terminate a user session after organization-defined conditions or trigger events requiring session termination. To terminate 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 that a session can be idle. After the specified amount of time, MAX_IDLE_TIME kills sessions. ALTER SYSTEM SET max_idle_time=15;