STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 12 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to General Application (GAPP) Security Requirements Guide

V-288196

CAT II (Medium)

The application must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.

Rule ID

SV-288196r1252173_rule

STIG

General Application (GAPP) Security Requirements Guide

Version

V1R0.1

CCIs

CCI-002038

Discussion

Without reauthentication, 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 reauthenticate. In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication 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 DoW, the minimum circumstances requiring reauthentication are privilege escalation and role changes.

Check Content

Review the application documentation and deployed configuration to determine whether the application requires users to reauthenticate when organization-defined circumstances or situations require reauthentication.

If the application does not require users to reauthenticate when organization-defined circumstances or situations require reauthentication, this is a finding.

Fix Text

Configure the application to require users to reauthenticate when organization-defined circumstances or situations require reauthentication.