Continuous control monitoring that fixes

ZeroTB helps your team keep controls working by carrying failed checks through to verified repairs. Our team and software investigate gaps and coordinate repairs across the systems your commitments cover. Compliance, IT and engineering spend less time coordinating the response and receive evidence of the completed work.

See which repairs are complete
One Saltmere control gap: a review rule turned off on saltmere/payments, assigned to the engineering lead, repaired by an approved pull request and verified against the change-review requirement.

Works with the stack you already run

Unfinished work after an alert

A failed check leaves compliance, IT and engineering with a repair to coordinate. Someone must investigate the gap, agree on a response and establish whether the change worked. Closing the ticket can leave the control's actual condition untested.

  1. A control check fails

  2. Teams exchange repair tasks

  3. Control condition stays unknown

Control repair and verification

Check the requirement

ZeroTB turns approved policy commitments into checks against the systems where those requirements apply.

Arrange the repair

Each gap gets an owner and a proposed fix. Your team authorizes material changes within agreed permissions.

Confirm the result

ZeroTB checks the changed state before closing the gap and preserves the action, approval and verification as evidence.

Example of blocking unauthorized access while preserving work access

A completed access repair can show that company data remains available through approved accounts while the unauthorized path is closed. The Verified Control Record connects that result to the access requirement and the device protections checked during the repair.

Keep approved access working
A Saltmere access restoration record: the managed-device requirement, a personal account active on an unencrypted laptop, the approved block and hardening, and checks confirming the work account and device protections.
  1. Access requirement. Company information must be accessed through approved work accounts on managed devices.

  2. Failed condition. The personal account is active and the device lacks required protections.

  3. Approved action. The record retains approval for restricting the account path and completing device hardening.

  4. Verified result. The final checks confirm that approved access works and required device protections are in place.

Measuring the time to restoration

Mean Time to Verified Restoration measures how long it takes to confirm that a failed control works again. ZeroTB gives each gap an owner, a service-level agreement and a clock. Compliance can assess the time spent restoring controls alongside evidence of the completed repairs.

  • Each gap has a responsible owner

  • Agreed service levels govern the response

  • A verified result completes the measurement

Talk to our team

Talk with our team about failed checks, recurring repairs and the coordination your compliance and engineering teams handle today.

FAQ

Can ZeroTB keep the records for the controls it operates?

Yes. ZeroTB keeps commitments, checks, repairs and evidence together. ZeroTB operates the controls recorded there and produces signed, portable evidence. Your auditor can inspect the Verified Control Record in ZeroTB, and your team can retain a copy with its compliance records.

Does the work extend beyond cloud configuration?

Yes. ZeroTB covers controls across endpoints, identity and access, change and development, cloud infrastructure, and people and processes. The requirements in your reports and policies determine which systems and activities need checks.

Can a repair support more than one framework?

Yes. SOC 2, ISO 27001 and HIPAA can rely on shared operational controls. When the same control supports several requirements, one verified restoration can supply evidence for each applicable requirement.

How much permission does ZeroTB need to begin monitoring?

ZeroTB starts with read-only access. Write permissions are scoped by action class and can be revoked. Material changes use reviewed pull requests by default. Direct API actions require opt-in, a way to reverse the change and limits on what it can affect.

Who decides when an exception is acceptable?

People in your company decide which exceptions are legitimate and confirm what a commitment means. AI helps interpret requirements and investigate gaps. It cannot declare a control healthy or close the work on its own.

How are gaps in monitoring coverage shown?

ZeroTB displays unknown, stale and disconnected states when observations are missing or no longer current. These states keep missing evidence visible. A control needs a supporting check before ZeroTB can report it as healthy.

Can ZeroTB keep operating the controls after the Pilot?

Yes. Control operations provides continuing checks and repairs after the initial engagement. ZeroTB keeps working across the systems where your commitments apply as accounts, devices, code and configurations change.

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 to evaluate the work in your own systems.