Evidence from the fix

ZeroTB gives compliance teams evidence that a repaired control works. Each Verified Control Record connects the original requirement to the repair and the check that established its result. Your team can answer questions about completed work, and an auditor can inspect the evidence directly in ZeroTB.

Show what the repair achieved
A completed backup repair: the policy line, the database missing from the backup plan, the approved action and the next day's check showing a backup kept 30 days.

Works with the stack you already run

Missing proof after a repair

Compliance needs to know whether a repair restored the control. A task can be marked complete while that answer is still missing. If nobody checked the system after the change, a reviewer has no observed result to compare with the requirement.

Spot the missing result
A repair ticket marked closed with no system observation attached, so the control's result stays unknown.
  1. Someone changes a system

  2. The repair task closes

  3. The control result remains unproven

Evidence captured during restoration

ZeroTB records the work from the first check through to restoration. It reads the commitment, checks the system and drafts a repair for human approval. ZeroTB checks the approved repair's result before closure and signs the record of the requirement, observations, action and approval.

  • The source clause explains the requirement

  • The approval identifies who authorized the action

  • The final observation establishes the result

Evidence for compliance reviews

Requirement traceability

Compliance can refer to the source clause when explaining the reason for a completed repair.

Auditor access

Auditors read the record in ZeroTB, where they can inspect the approval and the observed result.

Framework coverage

A repair to a shared control can supply evidence for SOC 2, ISO 27001 and HIPAA requirements.

Example of restricting access to approved work accounts

This access example shows how the record accounts for the whole requirement. Closing the personal account path is one part of the repair. The final check also establishes that approved work access remains available and that the device meets its required baseline.

Confirm safe work access
An access record covering the whole requirement: the managed-device policy, the approved restriction and device hardening, and the check that work access works and the laptop passes its baseline.
  1. Source requirement. The access policy ties the use of company information to approved accounts and managed devices.

  2. Approved repair. The action and approval explain the restriction of personal access and the completed device hardening.

  3. Checked result. The observation confirms that work access remains available and the device passes its baseline check.

Portable records for audit review

The Verified Control Record gives you a portable copy of the repair evidence. ZeroTB keeps the record with the commitment, checks and repair history. A folder the auditor can open is another place to retain the signed evidence.

  • Portable evidence supports auditor review

  • Signatures support checks of record integrity

  • ZeroTB keeps the control record

Talk to our team

Talk with our team about the evidence you need when a control repair reaches compliance or audit review.

FAQ

How can a reviewer check the record's integrity?

The record carries an ed25519 signature and a sha256 manifest for integrity checks. It also preserves who approved the repair and when ZeroTB verified the result. A reviewer can examine those details with the evidence of the change.

Does ZeroTB need permission to change systems before it can inspect them?

No. Initial access is read-only. Your team can later grant scoped, revocable write permissions by action class. Material changes normally go through pull requests for review. A direct API action requires explicit opt-in, must stay within its permitted scope and must be reversible.

What happens when ZeroTB cannot observe the repaired system?

It shows the observation gap as unknown, stale or disconnected. Those states remain visible because ZeroTB needs an observation to establish that the control works. A reviewer can see where that evidence is missing.

Does a completed record prove that the control still works after another change?

It shows what ZeroTB observed when it checked that repair. A later change can affect the control again. ZeroTB continues to check the system against the commitment and responds when the control drifts.

Can AI decide that the evidence is sufficient to close a finding?

AI can propose a conclusion, but it cannot declare a control healthy or close the work on its own. ZeroTB checks the resulting system state before closure, and people retain authority over material decisions and legitimate exceptions.

Can a repair include work that a person performs?

Yes. A runbook that a person executes is one of ZeroTB's supported responses to a control gap. ZeroTB checks the resulting state before closing the work, including when the repair requires a person to act.

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 records that show the repairs and their results in your own systems.