STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Okta Identity as a Service (IDaaS) Security Technical Implementation Guide

V-273189

CAT II (Medium)

Okta must enforce the limit of three consecutive invalid login attempts by a user during a 15-minute time period.

Rule ID

SV-273189r1098834_rule

STIG

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

Version

V1R2

CCIs

CCI-000044CCI-002238

Discussion

By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. Satisfies: SRG-APP-000065, SRG-APP-000345

Check Content

If Okta Services rely on external directory services for user sourcing, this check is not applicable, and the connected directory services must perform this function.

From the Admin Console:
1. Go to Security >> Authenticators. 
2. Click the "Actions" button next to "Password" and select "Edit".
3. For each Password Policy, verify the "Lock Out" section has the following values:
    - "Lock out after 3 unsuccessful attempts" is checked.
    - The value is set to "3".

If Okta Services are not configured to automatically lock user accounts after three consecutive invalid login attempts, this is a finding.

Fix Text

From the Admin Console:
1. Go to Security >> Authenticators.
2. Click the "Actions" button next to "Password" and select "Edit".
3. For each Password Policy, ensure the "Lock Out" section has the following values:
    - "Lock out after 3 unsuccessful attempts" is checked.
    - The value is set to "3".