STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Okta Identity as a Service (IDaaS) Security Technical Implementation Guide

V-273187

CAT II (Medium)

The Okta Admin Console must log out a session after a 15-minute period of inactivity.

Rule ID

SV-273187r1098828_rule

STIG

Okta Identity as a Service (IDaaS) Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000057

Discussion

A session timeout lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application session prior to vacating the vicinity, applications must be able to identify when a user's application session has idled and take action to initiate the session lock. The session lock is implemented at the point where session activity can be determined and/or controlled. This is typically at the operating system level and results in a system lock. However, it may be at the application level where the application interface window is secured instead.

Check Content

From the Admin Console:
1. Select Applications >> Applications >> Okta Admin Console.
2. In the Sign On tab, under "Okta Admin Console session", verify the "Maximum app session idle time" is set to 15 minutes.

If the "Maximum app session idle time" is not set to 15 minutes, this is a finding.

Fix Text

From the Admin Console:
1. Select Applications >> Applications >> Okta Admin Console.
2. In the Sign On tab, under "Okta Admin Console session", set the "Maximum app session idle time" to 15 minutes.