How to Connect Okta to SecureSpect
Connect your Okta tenant to automate identity and access management evidence collection for SOC 2 CC6 controls.
Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.
Open Integrations →Overview
SecureSpect connects to Okta using a read-only API token to collect evidence on your identity governance posture: MFA enrollment rates, inactive user detection, sign-on policies, and password policy strength. This maps directly to SOC 2 CC6.1 (Logical Access Security) and CC6.2 (Authentication).
What Gets Monitored
- MFA enrollment — Percentage of users with MFA enrolled
- Password policies — Minimum complexity, lockout policy settings
- Sign-on policies — MFA required for admin roles
- Inactive users — Users with no login in 90+ days
- Admin roles — Count of super admin assignments
- Provisioning — Users without app assignments (potential orphaned accounts)
Step 1 — Create a Read-Only API Token
SecureSpect and click Create Token.Alternatively, use an OAuth service app (recommended for production):
SecureSpect and complete creation.okta.users.read
- okta.groups.read
- okta.policies.read
- okta.apps.read
Step 2 — Connect in SecureSpect
yourcompany.okta.com).Step 3 — Address Common Findings
| Finding | Target | Remediation |
| MFA enrollment < 95% | 100% for admins, 95% overall | Enroll remaining users or enable MFA requirement |
| Password policy: no lockout | Lockout after 10 attempts | Update in Security → Authentication → Password |
| Inactive users > 90 days | 0 (deactivate or justify) | Deactivate in Okta or document exception |
| Super admins > 2 | Minimize | Review and downscope admin assignments |
Access Review Integration
SecureSpect's Access Reviews module can import your Okta user-app assignments and turn them into a structured quarterly access review. Reviewers receive an email with a list of their direct reports' app access and approve/revoke directly in SecureSpect.