Title

The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user. (Cat II impact)

Discussion

If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session. Such logout may be explicit or implicit. Examples of explicit are: clicking on a "Log Out" link or button in the application window; clicking the Windows Start button and selecting "Log Out" or "Shut Down." Examples of implicit logout are: closing the application's (main) window; powering off the workstation without invoking the OS shutdown. Both the explicit and implicit logouts must be detected by the DBMS. In all cases, the DBMS must ensure that the user's DBMS session and all processes owned by the session are terminated. This should not, however, interfere with batch processes/jobs initiated by the user during his/her online session: these should be permitted to run to completion.

Check Content

Determine, by reviewing DBMS documentation and/or inquiring of the vendor's technical support staff, whether the DBMS satisfies this requirement; and, if it does, determine whether this is inherent, unchangeable behavior, or a configurable feature. If the DBMS does not satisfy the requirement, this is a permanent finding. If the behavior is inherent, this is permanently not a finding. If the behavior is configurable, and the current configuration does not enforce it, this is a finding.

Fix Text

Where relevant, modify the configuration to allow the user to manually terminate a session initiated by that user.

Additional Identifiers

Rule ID: SV-206581r879674_rule

Vulnerability ID: V-206581

Group Title: SRG-APP-000296

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.