System of action for compliance

ZeroTB takes compliance findings through to working controls, reducing the time your teams spend coordinating repairs. Our team and software handle the control work between audits. Compliance and engineering can see which gaps still need attention and which repairs have restored the required protections.

See which repairs still need attention
A control operations view: an open MFA gap with its owner and fix, a backup control restored with a verified record, one passing control and one gone stale.

Works with the stack you already run

Compliance work between teams

A compliance finding can pass between compliance, IT and engineering while the affected control stays broken. Someone still needs to connect the requirement to the repair, assign responsibility and establish whether the work restored the expected state.

  1. A control fails

  2. Teams exchange repair tasks

  3. The finding stays unresolved

Control restoration

Read and check

We read the requirement in your report or policy, confirm its meaning with you and check the relevant systems.

Complete the repair

ZeroTB gives the gap an owner and proposes a fix. With approval, we execute or coordinate the repair.

Verify the result

We check the repaired control against the requirement. Once it passes, ZeroTB closes the gap and signs the evidence record.

Evidence behind a closed finding

The Verified Control Record gives an auditor the evidence behind a closed finding. It contains the commitment, the system state before and after the repair, the action, approval and verification. Auditors read it directly in ZeroTB. Your team can also keep a portable copy.

See why a finding can close
A signed record that closes a backup finding: the commitment, retention before and after, the action and its approval.

Control records in ZeroTB

ZeroTB holds the record of your control work. We operate the controls recorded in ZeroTB and keep their commitments, checks, repairs and evidence together. Your team can review the signed repair evidence with the commitment and checks in ZeroTB.

  • Keep commitments and evidence in ZeroTB

  • Give control gaps an owner and deadline

  • Retain portable evidence of completed repairs

Talk to our team

Tell us about the compliance work that keeps returning to your team. We can discuss where ZeroTB would help.

FAQ

How much access would ZeroTB need to act on our findings?

The first checks use read-only access. You grant write access separately for each kind of action and can revoke it. We use pull requests for material changes by default. Direct API actions require opt-in, limited scope and a way to reverse the change.

What if a repair leaves the control below its required state?

The finding stays open. ZeroTB checks the result against the requirement, so an attempted fix alone cannot close the gap. AI helps with diagnosis and proposals; it has no authority to declare a control healthy or close the work.

Can one requirement involve several kinds of system?

Yes. Requiring approved work accounts on managed devices connects identity to endpoint protection. ZeroTB can follow a commitment across those systems. Its coverage also includes change and development, cloud infrastructure, and people and process.

Can ZeroTB handle controls that depend on people completing scheduled work?

Yes. ZeroTB schedules work such as training, vendor reviews and incident exercises from the commitment, assigns an owner and escalates overdue tasks. It checks that the owner completed the work, so recurring obligations have a responsible person and evidence of completion.

How would we know that an observation is too old to support closure?

ZeroTB makes unknown, stale and disconnected states visible. Missing or outdated observations cannot establish that a control works. The resulting state needs a supporting check before ZeroTB treats the repair as verified.

Can the same repair support commitments in several frameworks?

Yes. ZeroTB operates controls beneath SOC 2, ISO 27001 and HIPAA requirements. Where those requirements depend on the same control, one verified restoration can support several of them. The relevant commitments determine how the repair applies to each framework.

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 operating controls and portable evidence from work on your own systems.