Control restoration layer

ZeroTB restores compliance controls that have stopped working as your company changes. Our team and software investigate the failure and carry the repair through to a verified result. This gives compliance and engineering support for ongoing control work without building a dedicated compliance engineering team.

Keep controls working after changes
A logging control observed failing at 30 days of retention, then restored to 365 days after an approved pull request and read again as passing.

Works with the stack you already run

Control failures between audits

A control can stop working while its requirement remains unchanged. An account stays active after a contractor leaves, or a new repository allows changes without review. These failures need attention in the systems where they occur, often between scheduled audits.

  1. The company changes

  2. A safeguard stops working

  3. The commitment goes unmet

Approved control repairs

Check the requirement

ZeroTB reads reports and policies, then checks systems against the commitments your team approves.

Prepare the repair

ZeroTB proposes a runbook, pull request, API action or guardrail. People authorize material changes.

Verify the result

ZeroTB checks the repaired state before closing the work and records the change, approval and result.

Example of blocking unauthorized account access

The Verified Control Record connects an access repair to the original policy requirement. This example follows a requirement for approved work accounts on managed devices. A reviewer can see both the unauthorized access that was removed and the approved access that remained available.

See the result of the repair
An access restoration record: the managed-device requirement, the failed check, the authorized repair with hardening assigned to its owner, and the passing check that kept work access available.
  1. Required access. The commitment limits company information to approved work accounts on managed devices.

  2. Failed condition. The observation identifies a personal account with access and an incomplete device baseline.

  3. Authorized repair. The recorded action blocks the unauthorized path and assigns device hardening to its owner.

  4. Verified state. The final check confirms approved access remains available and the required device protections pass.

Control work and evidence in ZeroTB

ZeroTB keeps commitments, checks, repairs and evidence in one place. ZeroTB handles control restoration and produces a signed Verified Control Record for each completed repair. Your auditor can inspect that record in ZeroTB; your team can also retain a portable copy.

  • Keep commitments and repair evidence together

  • Give auditors access to completed repair evidence

  • Retain signed records outside ZeroTB

Talk to our team

We can discuss where control failures keep recurring and how ZeroTB could help with the repairs between audits.

FAQ

Can restoration cover work beyond cloud configuration?

Yes. Device protections, account access, development practices and scheduled reviews are also within ZeroTB's scope. An overdue review needs different work from a cloud configuration repair. ZeroTB uses the approved requirement to determine what must happen and who owns it.

Can one repair address requirements in several frameworks?

Yes. Where SOC 2, ISO 27001 and HIPAA requirements overlap, one operating control can meet several commitments. ZeroTB links the control to those requirements. Restoring it can therefore address gaps in more than one framework at the same time.

How much permission do we grant for repair work?

ZeroTB begins with read-only access. Your team can then grant and revoke write permissions for specific classes of action. Pull requests are the default for material changes. An API action needs separate opt-in, a way to reverse it and limits on the systems it affects.

Can a control count as restored when its connection is stale?

No. An old observation cannot establish the system's present condition. ZeroTB makes stale, unknown and disconnected states visible to the reviewer. The finding needs evidence that the required condition holds before ZeroTB can treat the control as restored.

How is the time to restoration measured?

Mean Time to Verified Restoration starts when drift is detected and ends when the repaired condition is verified. A repair marked complete in a ticket still needs that final check. This measures the time taken to restore the control in the affected system.

What support is available after the Pilot?

Control operations provides ongoing checks and repairs. As accounts, repositories and other systems change, ZeroTB continues the work required to maintain the controls. People still approve material decisions and determine which exceptions to the requirements are legitimate.

Start with the Pilot

The eight-week Pilot maps up to 25 commitments from your report and takes two real control gaps through verified restoration. You receive working controls and portable evidence records from the work completed in your own systems.