Home / Integrations

Keeping GitHub controls working between audits

ZeroTB checks GitHub compliance commitments against branch protection, required reviews and CI gates, then prepares repairs.

Spot missing reviews across code
Five GitHub repositories under a change-review commitment at 09:00 today: four passing, and the new fernway/worker broken because main has no required review, while its CI gates pass.

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.

GitHub compliance depends on your repository settings

GitHub reports on its platform. Your team keeps repository settings compliant. ZeroTB's software and team keep those controls working after audits for US software, AI, fintech and healthtech companies.

  • GitHub covers GitHub. GitHub reports cover its platform's controls. Your team remains responsible for repository settings

  • Auditors sample merges. Auditors examine pull request approvals and the branch protection rules behind them

  • The period counts. Required reviews and CI gates must hold across the whole audit period

New repositories skip reviews and cost audit findings

Missing branch protection rules let new repositories ship without required reviews or tests. The unmet policy can return as an audit finding.

Two GitHub repositories under the same review requirement: fernway/api requires an approving review on main, the new fernway/worker has no review rule; CI passes in both.
  1. A new repository is created

  2. Branch protection is never applied

  3. Unreviewed code reaches production

ZeroTB restores missing GitHub protections and rechecks them

ZeroTB repairs gaps in GitHub protections and checks them again. Daily checks show whether the agreed conditions still hold as repositories change.

Daily commitment checks

We check approved commitments daily against repositories within the agreed scope and evidence requirements.

Know which requirements still hold
A change-review commitment's daily checks for 2026 and the five GitHub repositories it covers: four passing at 09:00 today, and the new fernway/worker broken, with no review rule on main.

ZeroTB checks GitHub rules for SOC 2 CC8.1

ZeroTB checks GitHub branch protection rules, required reviews and CI gates against the route your company approved for code changes.

Reads

  • Branch protection rules
  • Required review settings
  • CI gate conditions

Controls

  • SOC 2 CC8.1 · Control changes to systems
  • ISO 27001 A.8.4 · Control access to source code
  • ISO 27001 A.8.32 · Manage system changes

A.8.4 coverage concerns only the controlled route for code changes. Wider access decisions remain part of that control. See SOC 2 change management.

Checks
Branch protection

We compare each repository's branch rules with the approved development commitment.

Required reviews

We check that required reviews are still in place across the agreed repositories.

CI gates

We check that CI gates still enforce the testing requirements your team approved.

Approved change route

We examine whether reviews and tests support the route your commitment describes.

Your team scopes ZeroTB's GitHub write access

Read-only access lets ZeroTB observe GitHub. Your team decides which writes to allow and can revoke the permissions it grants.

Read-only start

The initial connection observes repositories before your team grants any write access.

Action-class permissions

Each permission grant covers specific action classes your team has authorized.

Revocable access

Your team can withdraw write permissions granted for a repair.

Opt-in API actions

Direct API actions require an explicit choice to use that repair method.

Reversible changes

API actions must be reversible and stay within policy limits.

Legitimate exceptions

Your team decides when a repository needs an exception to the commitment.

ZeroTB connects read-only to repositories you approve

Before connecting to GitHub, we establish which repositories the commitment covers and what their settings must show.

  1. Agree the requirement

    We identify the development commitment and prepare its required repository conditions for approval.

  2. Define the scope

    We identify the repositories, owners, check cadence and evidence each commitment needs.

  3. Connect read-only

    ZeroTB observes GitHub settings within the approved scope before any write action.

New repositories and agent-written code stay covered

GitHub checks follow where your team ships code, including new repositories, changed release routes and routes for agent-written contributions.

New repositories

We include new repositories where the same review and testing requirements apply.

Catch missing reviews in new code projects
The new fernway/worker repository picked up by the daily read under the change-review commitment: its required review missing, its CI and secret scanning passing.

Talk to our team

Talk with our team about GitHub review and testing gaps and where your engineers need support.

FAQ

Does GitHub's SOC 2 report cover our repositories?

GitHub's SOC 2 report covers its platform. Your team must show that branch protection, required reviews and CI gates hold in your own repositories.

What evidence does an auditor want for GitHub change management?

Auditors examine pull request approvals and protection settings across the period. Each repair adds a signed, portable Verified Control Record that auditors can read directly in ZeroTB.

Does a stale observation mean a branch protection rule has failed?

A stale observation means ZeroTB lacks current evidence about the rule. Unknown, stale or disconnected states remain visible until a fresh check establishes the condition.

What if production changes through a route outside GitHub?

A route outside GitHub needs its own place in the change-control scope. A repository rule does not cover a separate deployment path.

What if a GitHub repair needs manual work?

A GitHub repair needing manual work gets a proposed runbook for the owner. ZeroTB checks the repository again after the work.

What happens if the same repository requirement fails again?

A repeated repository failure becomes a new gap for its owner. Checks continue at the agreed cadence, so a restored review rule can be checked again after removal.

Start with the Pilot

In eight weeks, the Pilot maps up to 25 commitments and takes two real control gaps through verified restoration.