Skip to main content
Checks that the Okta password policy meets minimum security requirements.

​
About

When you connect Okta to DSALTA, the platform syncs your users, roles, and access settings using read-only API access. DSALTA evaluates this control on every sync. If the requirement is not met, DSALTA activates this check.

​
Why This Matters

Weak passwords are easy to brute-force or guess. A strong policy — length, complexity, expiration, and lockout — raises the cost of an attack significantly and is a documented requirement in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure you have administrator access to Okta.
Strengthen the password policy
  1. Sign in to your Okta admin console and open the password policy settings.
  2. Set a minimum length of at least 12 characters.
  3. Require complexity (uppercase, lowercase, number, and symbol).
  4. Configure password expiration and history per your policy, and enable account lockout after repeated failed attempts.
  5. Save the policy.
Once the policy meets the minimum requirements, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Okta integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Okta.