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 users with access to critical systems are authorized in Okta.

​
Why This Matters

Unauthorized or excessive access to critical systems increases your attack surface and violates the principle of least privilege. Users with access beyond what their role requires can inadvertently or maliciously access sensitive data. Regular access validation is a core requirement of SOC 2 (CC6.1, CC6.2) and ISO 27001 (A.9.2.5).

​
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. Navigate to DSALTA → Data Library → Access to view all users with access to Okta.
  2. Review each user’s role and permissions against their current job function.
  3. For any user whose access is no longer valid, either remove their access entirely or adjust their role to match their current responsibilities.
  4. In DSALTA, mark each reviewed user as In Scope (valid access) or Not in Scope (access to be revoked).
  5. Document the review decision and the reviewer’s name.
  6. Set up a recurring access review schedule (quarterly recommended) in DSALTA.
  7. Once all users have valid, documented access, DSALTA will 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.