Home / Solutions

Stop the same finding from coming back

A Control review finds why a repaired control keeps failing and what continuing work it needs.

Works with the stack you already run

independently audited · zerotb · independently audited · zerotb · SOC 2

ZeroTB has undergone an independent audit and operates this control lifecycle in its own compliance program. Its report is available under NDA.

A Control review examines one returning gap

A Control review is ZeroTB's examination of one returning gap and why its repair failed to hold. Our team works with US companies of 25 to 250 people past their first audit.

  • Cover any recurring gap. We examine repositories, accounts, devices, missing evidence and recurring manual tasks

  • Bring audit experience. Our security and IT experience includes taking companies through SOC 2 and ISO 27001

  • Start read-only. Agreeing a review authorizes no production change

Undone repairs cost repeat audit findings and rework

A recurring finding means investigating the same control again and gathering evidence for work your team thought was complete.

Systems keep changing after repair. The recurring SOC 2 findings guide examines what earlier repairs miss and why findings return at the next audit.

  1. The repair is completed

  2. The system changes again

  3. The same finding returns

The review finds what the earlier repair missed

The earlier repair may leave the requirement unclear, the control without an owner or the checking schedule unable to catch later changes.

Clarify the requirement

We identify the condition the commitment requires so the team maintains the right control.

Find the continuing owner

We examine who owns the control once the repair task ends.

Match checks to change

We compare the checking schedule with how often the system changes.

Confirm the closure

We examine whether a check confirmed the control worked after the repair.

Our team turns the finding into a proposal

The Control review starts with the recurring concern and ends with a proposal for work in the Pilot.

  1. Discuss the recurrence

    We discuss repeated control work or suspected recurrence before another audit finding.

  2. Agree the focus

    We identify one control that addresses the recurring concern.

  3. Prepare the proposal

    We propose the work, responsible team and checks that show the control operates.

  4. Continue in the Pilot

    The Pilot carries the proposed work through to a first repair record.

The control owner leaves with a defined repair

From you

Confirm the focus

You decide whether the proposed control addresses the recurring concern.

Decide on the Pilot

You decide whether to take the proposed work into the Pilot.

You receive

A defined gap

We identify where the observed condition falls short of the commitment.

A repair approach

We specify the work, responsible team and checks the control needs.

A completion condition

We define the check that shows the control is restored.

Example of catching repeated changes to review rules

This example follows a GitHub review rule removed again after restoration. The review identifies the continuing check needed to catch another recurrence.

Explore the control lifecycle

See when a repair stops working
A review rule in larkfield/billing restored on 21 Oct and its ticket closed, removed again on 2 Nov, and the owner and daily check proposed to catch the next change.
  1. Earlier repair. Required reviews were restored in GitHub, and the repair ticket was closed.

  2. Later change. A rule change removed required reviews while the ticket still appeared complete.

  3. Continuing check. The proposed owner and checking schedule address recurrence after the repair ends.

Talk to our team

We can discuss the control that keeps coming back and the checks it needs to stay fixed.

FAQ

Can we request a review before the finding appears in another audit?

A Control review can start before another audit finding. Repeated repairs or doubts about a control after system changes are enough to begin the conversation.

Does a recent successful check rule out a recurring problem?

A successful check shows how the control worked then. A later system change can undo the repair, which is why the review examines the checking schedule.

Can we discuss a repeated gap caused by coding-agent changes?

Coding-agent changes can be reviewed when they affect a commitment. We examine the requirement and the code, configuration or access where the changes occurred.

Can the review cover a finding about incomplete evidence?

Incomplete evidence can be the recurring finding. We examine the observations used to assess the control and identify where proof of its operation is missing.

Can we discuss a recurring task that someone performs manually?

A Control review can cover training, vendor reviews, incident exercises and policy reviews. Our team examines the task's schedule, owner and completion evidence.

Does agreeing a review authorize changes to production?

Agreeing a review authorizes no production changes. ZeroTB starts read-only, material changes require human approval, and write access is scoped per action class and revocable.

Start with the Pilot

The eight-week Pilot maps up to 25 commitments and restores two real control gaps, delivering working controls and portable evidence records.