← All integrations
Identity · integration
Okta
MFA, password policy, stale accounts and deprovisioning for an Okta org.
ISO 27001SOC 2PCI DSSDPDPARBISEBI CSCRFIRDAI
What ProofLayer proves
Read-only evidence, evaluated against versioned rules.
- Users and admins are MFA-enrolled and an MFA sign-on policy applies to everyone
- The password policy meets baseline; dormant accounts are removed; departed people are deprovisioned
Configure in ProofLayer
Live in minutes.
- Connections → New connection → pick this provider and name the account.
- Paste a read-only API token (stored write-only).
- Click Test connection — ProofLayer verifies read access from the control plane and reports a clear reason if anything is off.
- Set the scan schedule; every run appends to the evidence chain for this account.
- Choose the framework mapping(s) and, optionally, a push target (CISO Assistant, a Jira/ServiceNow ticket on failure, or a scheduled auditor pack).
Grant access from your side
Read-only, least-privilege, revocable.
You create the access in your own console and paste a credential ProofLayer stores sealed — it never writes to your systems.
- Create a dedicated user with the Read-only Administrator role (tokens inherit their creator’s permissions).
- Signed in as that user: Security → API → Tokens → Create token, and paste it.
In-account agent option. Provide the token to the agent as SNYK-style env (OKTA token); it stays on your host. The collector posts evidence outbound-only, so ProofLayer holds no credential into your environment.