The DBMS must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.

From Database Security Requirements Guide

Part of SRG-APP-000389-DB-000372

Associated with: CCI-002038

SV-72577r1_rule The DBMS must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.

Vulnerability discussion

The DoD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, current, DoD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification Number (PIN) to be entered by the user at the beginning of each session and whenever re-authentication is required.Without re-authentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user re-authenticate.In addition to the re-authentication requirements associated with session locks, organizations may require re-authentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances:(i) When authenticators change; (ii) When roles change; (iii) When security categories of information systems change; (iv) When the execution of privileged functions occurs; (v) After a fixed period of time; or(vi) Periodically.Within the DoD, the minimum circumstances requiring re-authentication are privilege escalation and role changes.

Check content

Review the system documentation and the configuration of the DBMS and related applications and tools. If there are any circumstances under which a user is not required to re-authenticate when changing role or escalating privileges, this is a finding. If the information owner has identified additional cases where re-authentication is needed, but there are circumstances where the system does not ask the user to re-authenticate when those cases occur, this is a finding.

Fix text

Modify and/or configure the DBMS and related applications and tools so that users are always required to re-authenticate when changing role or escalating privileges. Modify and/or configure the DBMS and related applications and tools so that users are always required to re-authenticate when the specified cases needing reauthorization occur.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer