Okta access matches each person's current role
ZeroTB restores Okta accounts and privileges to your access rules through repairs your team approves.

Works with the stack you already run
ZeroTB has undergone an independent audit and operates this control lifecycle in its own compliance program. Its report is available under NDA.
ZeroTB's Okta integration follows access as people change
Okta integration checks accounts against policy as staff change. ZeroTB's software and team keep controls working for US software, AI, fintech and healthtech companies with 25 to 250 people.
Identity and access. This is one of the surfaces where ZeroTB keeps controls working
Identity provider connection. ZeroTB connects to Okta when a commitment concerns identity
Policies covering accounts. A policy applies to Okta-managed accounts even without naming Okta
People keep old Okta permissions, costing audit findings
An access review decision remains unfinished after a departure or role change. Old Okta permissions stay active, leaving a gap that can become a finding.
Role or employment changes
Access decision awaits action
Old permissions remain active
ZeroTB fixes leftover Okta access and rechecks it
When Okta access fails a rule, ZeroTB gives the gap an owner and response window and follows the repair through to verification.
Rule from your policy
We read the policy for the access rule, covered accounts and expected evidence.

Gap with an owner
We show the owner the failed rule beside the account's observed condition.

Repair you approve
We propose a fix for approval and a runbook for changes performed manually.

Access checked again
We check access after the change and close only when the rule holds.

Signed repair record
The Verified Control Record retains requirement, before-and-after state, action, approval and verification.

ZeroTB checks Okta accounts and privileges for SOC 2
ZeroTB reads account status, assigned privileges and the conditions below from Okta to assess your access requirements.
Reads
- Account status
- MFA conditions
- Assigned privileges
Controls
- SOC 2 CC6.1 · Logical access protections
- SOC 2 CC6.3 · Access changes and removal
- ISO 27001 A.5.18 · Access rights management
We compare accounts in scope with the requirement for approved work accounts.
We check access left after a departure against your removal requirement.
Assess the observed multi-factor authentication condition against what the policy requires for those accounts.
We compare the account's privileges with the access its responsibilities require.
Your team grants every Okta permission ZeroTB uses
We connect to Okta with read-only access first. You decide which action classes may receive write permission and can revoke each grant.
ZeroTB observes account conditions within the agreed scope.
Write permissions apply to the action classes your team has agreed to allow.
You can withdraw ZeroTB's access when you need to.
Direct API actions require your opt-in and limits on the resources affected.
An API change must allow reversal within the agreed limits.
Your team approves material changes before they happen.
Setup scopes the Okta accounts before observation starts
We identify the Okta accounts covered by the commitment before connecting, with an owner and expected evidence for each requirement.
Confirm the commitment
Your team confirms the meaning of the access clause we identify.
Establish the scope
We identify the covered accounts, responsible owner and expected evidence.
Begin observation
ZeroTB observes the agreed account conditions before any change is authorized.
Okta coverage follows departures, new duties and reviews
Okta permissions need attention when people leave or take on different duties. ZeroTB keeps those changes and access review decisions connected to corrective work.
Departing staff
ZeroTB sends unresolved access after a departure to its owner.

Changed responsibilities
The access owner assesses privileges against the person's current duties.

Access review follow-up
Each access review decision stays connected to the corrective work it requires.

Talk to our team
We can discuss the departures, changed privileges and unfinished access decisions your team needs help resolving.
FAQ
What does a stale or disconnected Okta observation mean?
A stale or disconnected Okta observation leaves current access unconfirmed. Unknown states remain visible too. The earlier result still shows what ZeroTB observed at that time.
Can the repair be a manual access change in Okta?
An owner can make a manual Okta change using ZeroTB's proposed runbook. Its record keeps the approval with the observation taken after the repair.
Who decides whether an access exception is legitimate?
Your team decides whether to allow an access exception. AI can investigate the gap and propose a response, but it cannot authorize the exception.
Can evidence from an Okta repair support more than one framework?
The same Okta repair can provide evidence for several frameworks. The control must meet each requirement, and its evidence must cover the accounts within each scope.
Where can we read and keep the repair record?
Your auditor can read the signed Verified Control Record in ZeroTB. Your team also receives a portable copy to retain.
What happens if the same access fails again later?
ZeroTB treats the repeated access failure as a new gap and assigns an owner. Checks continue after repair at the cadence set for that commitment.
Start with the Pilot
The eight-week Pilot maps up to 25 commitments and takes two real control gaps through verified restoration.