Home / Resources

Keep mapped controls working across frameworks

Controls mapping connects a control with matching SOC 2, ISO 27001 and HIPAA requirements.

Controls mapping reuses one control across frameworks

Mapped controls share work and evidence. ZeroTB's software and team run SOC 2, ISO 27001 and HIPAA controls for US software, AI, fintech and healthtech companies with 25 to 250 people.

  • Share control work. A common controls framework, or unified control framework, lets programs share an access review

  • Keep each scope. An access review must include all accounts and applications required by each program

  • Maintain the mapping. Each control and owner needs a requirement link, updated when systems or requirements change

Every framework you run has its own guide

SOC 2

Browse the nine Common Criteria series that hold 33 SOC 2 criteria.

Browse report controls

ISO 27001

Find 93 ISO 27001 Annex A controls grouped into four themes.

Browse Annex A controls

HIPAA

Browse 18 HIPAA Security Rule standards organized into three safeguard groups.

Browse Security Rule safeguards

NIST

Read the six NIST CSF functions and 20 SP 800-53 control families.

Read the framework guide

One missed offboarding fails every mapped framework

A retained contractor account leaves company systems open and creates the same gap in SOC 2, ISO 27001 and HIPAA reviews.

Each program's records still show the requirement met, so the gap reaches the next audit without an owner.

  1. A contractor leaves

  2. An account stays active

  3. Several programs share the gap

ZeroTB checks your systems against your report daily

ZeroTB reads commitments from your SOC 2 report and policies. Your team approves each clause, scope, owner, cadence and expected evidence line by line.

  • Check systems daily. ZeroTB begins read-only, comparing what systems do with what the commitments require

  • Prepare each repair. We draft the fix for your approval and recheck the control after repair

  • Keep the record. The signed Verified Control Record stays in ZeroTB. Reviewers read it and retain copies

The Secure Controls Framework links controls to standards

The Secure Controls Framework is a free, volunteer-maintained, Creative Commons-licensed metaframework.

Three-letter domains group controls mapped to SOC 2, ISO 27001, HIPAA, NIST SP 800-53 and others. Evaluate an SCF control's live check: conditions observed, frequency and who handles failures.

Talk to our team

Talk with us about controls that cause problems across your programs and the work it takes to keep them running.

FAQ

Which frameworks does ZeroTB work with?

ZeroTB works with SOC 2, ISO 27001 and HIPAA commitments. Shared controls can support NIST outcomes where the scope matches.

Does a shared mapping cover everything when we add another framework?

A shared mapping can leave requirements uncovered when a new framework needs controls you do not have. That framework may also require its own assessment.

Does one restored control count for every framework at once?

A restored control can satisfy several frameworks when it covers each program's scope. Each auditor decides what the evidence supports.

What happens when our policy commitments change?

Changed commitments need your team's confirmation before they become enforced rules. That confirmation covers the commitment's meaning, the systems included and any exceptions.

Who approves a change to a shared control?

Your team authorizes material changes to shared controls, through pull requests by default. ZeroTB starts read-only and acts within the permissions granted.

Does ZeroTB audit or certify any framework?

ZeroTB does not audit, certify or promise audit success. Auditors and assessors can read the Verified Control Record directly in ZeroTB.

Start with the Pilot

The eight-week Pilot maps up to 25 report commitments and verifies repairs to two real gaps, providing working controls and portable evidence.