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-273201

CAT II (Medium)

Okta must enforce a 60-day maximum password lifetime restriction.

Rule ID

SV-273201r1098870_rule

STIG

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

Version

V1R2

CCIs

CCI-004066

Discussion

Any password, no matter how complex, can eventually be cracked. Therefore, passwords must be changed at specific intervals. One method of minimizing this risk is to use complex passwords and periodically change them. If the application does not limit the lifetime of passwords and force users to change their passwords, there is the risk that the system and/or application passwords could be compromised. This requirement does not include emergency administration accounts, which are meant for access to the application in case of failure. These accounts are not required to have maximum password lifetime restrictions.

Check Content

From the Admin Console:
1. Select Security >> Authenticators.
2. Click the "Actions" button next to the "Password" row and select "Edit".
3. For each listed policy, verify "Password expires after XX days" is set to "60".

For each policy, if "Password expires after XX days" is not set to "60", this is a finding.

Fix Text

From the Admin Console:
1. Select Security >> Authenticators.
2. Click the "Actions" button next to the "Password" row and select "Edit".
3. For each listed policy:
    - Click "Edit".
    - Set "Password expires after XX days" to "60".