Control work and records in ZeroTB
ZeroTB restores controls and keeps your commitments, checks, repairs and audit evidence together. Our team and software help compliance, IT and engineering resolve failures. You can see what changed, whether the control works and the evidence that supports the result.

Works with the stack you already run
Control repairs across teams
A GRC finding can pass between teams while the control continues to fail. Compliance understands the requirement, but the repair may depend on IT or engineering. Someone has to connect those responsibilities and check the system once the repair is complete.
A check identifies drift
The repair passes between teams
The control still fails
Restoring controls in practice
ZeroTB reads the requirement in your report or policy and checks systems against the commitment you approve.
ZeroTB drafts a fix for the failed control. People approve material changes, and ZeroTB executes within scoped permissions.
ZeroTB verifies the repaired state before closing the work. A signed record preserves the result and its evidence.
Evidence for the existing program
The Verified Control Record lets compliance review proof of a repair in ZeroTB. The signed record is portable and contains the commitment, before-and-after state, action, approval and verification. Auditors can also read it directly in ZeroTB when reviewing the work.

Talk to our team
We can talk through the findings your teams keep handling and how ZeroTB would carry the repairs through and retain the evidence.
FAQ
Does adding ZeroTB require write access from the start?
No. The starting point is read-only access. You can authorize write access by action class and revoke it. Pull requests are the default for material changes. Any direct API action must be opt-in, reversible and limited in scope.
Can ZeroTB cover controls outside our cloud infrastructure?
Yes. ZeroTB also covers endpoints, identity and access, development, and people and process. A requirement may depend on a device setting, repository rule or completed access review. ZeroTB checks the system or activity where that requirement applies.
Can one repair support evidence for several frameworks?
Yes. A control can serve requirements in SOC 2, ISO 27001 and HIPAA. Where those requirements share a control, the evidence of its verified restoration can support several frameworks.
Who decides whether a control gap is an acceptable exception?
That decision stays with people in your company. AI interprets the requirement and helps diagnose a gap. AI cannot declare a control healthy or close the work itself.
How does the record distinguish missing observations from a healthy control?
ZeroTB marks observations as unknown, stale or disconnected when appropriate. Those states remain visible. A control needs supporting evidence before ZeroTB can establish that it is healthy.
Can ZeroTB keep operating our controls after the Pilot?
Yes. With Control operations, ZeroTB continues checking and repairing controls as your systems change. ZeroTB keeps the commitments, checks, repairs and evidence together throughout that continuing work.
Start with the Pilot
The Pilot gives your team eight weeks of work on its own controls. ZeroTB maps up to 25 commitments from your report and takes two real control gaps through verified restoration. Portable records document the repairs.