Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that the Okta password policy meets minimum security requirements.

​
Why This Matters

Weak password policies enable brute force attacks and credential compromise. Industry standards require minimum length (12+ characters), complexity requirements, and expiration policies. SOC 2 and ISO 27001 both mandate documented password policies that meet minimum security thresholds.

​
What DSALTA Checks

DSALTA connects to your Okta environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Okta.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Sign in to the Okta Admin Console.
  2. Navigate to Security → Authentication → Password tab.
  3. Edit the default password policy or create a new one.
  4. Set Minimum length to at least 12 characters.
  5. Enable complexity requirements (uppercase, lowercase, number, symbol).
  6. Set Password age and Password history according to your policy.
  7. Under Account lockout, configure lockout after 5 failed attempts.
  8. Click Save.
  9. Once configured, DSALTA will detect the change on the next sync and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Okta integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in Okta.