Home / Integrations

Okta access matches each person's current role

ZeroTB restores Okta accounts and privileges to your access rules through repairs your team approves.

Spot access that needs attention
Northam's sign-in commitment beside the current Okta condition: three contractor accounts signing in with SMS only, owned by the IT lead.

Works with the stack you already run

independently audited · zerotb · independently audited · zerotb · SOC 2

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.

  1. Role or employment changes

  2. Access decision awaits action

  3. 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.

Know which access rule applies
Four commitments from Northam's access policy, each with its source clause, Okta check and account scope: two passing, one waiting for its owner and one broken.

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
Checks
Approved accounts

We compare accounts in scope with the requirement for approved work accounts.

Leaver access

We check access left after a departure against your removal requirement.

MFA requirements

Assess the observed multi-factor authentication condition against what the policy requires for those accounts.

Privilege conditions

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.

Read-only connection

ZeroTB observes account conditions within the agreed scope.

Scoped writes

Write permissions apply to the action classes your team has agreed to allow.

Revocable permissions

You can withdraw ZeroTB's access when you need to.

Opt-in API actions

Direct API actions require your opt-in and limits on the resources affected.

Reversible API changes

An API change must allow reversal within the agreed limits.

Human decisions

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.

  1. Confirm the commitment

    Your team confirms the meaning of the access clause we identify.

  2. Establish the scope

    We identify the covered accounts, responsible owner and expected evidence.

  3. 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.

Follow unresolved access after departure
The accounts a departure at Northam covers: four removed, one GitHub membership still active and assigned to the engineering lead.

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.