Home / SOC 2

SOC 2 CC8 change management

CC8 is the change-management part of SOC 2, with one criterion: CC8.1. It covers the process for making changes to systems. Reviews and tests help teams release changes that meet their commitments, even as they add repositories or revise the way they deploy software.

The CC8 change criterion

CC8.1

Change management

Follow the requirement from a proposed system change through its review, testing and release.

Read the criterion

Review gaps after workflow changes

Required reviews can disappear as the development setup changes. An existing repository may enforce them while a newly created one allows changes through. The team still has a review policy, but releases from the new repository can proceed without meeting it.

  1. A repository is added

  2. Required review is missing

  3. Unreviewed changes reach production

Change control repairs with ZeroTB

ZeroTB takes the change commitments from your report and policies and checks them against your systems. For a failed control, we prepare a repair that your team approves. We check the repaired state and put the evidence into a signed Verified Control Record.

  • Branch rules enforce the required reviews

  • Release checks follow the approved commitments

  • Repair evidence stays linked to the requirement

Talk to our team

We can discuss the reviews and release checks your team maintains, where they fail and how the repairs get done.

FAQ

Does CC8 apply beyond our code repositories?

Yes. CC8 covers changes to infrastructure, data and procedures too. That means a team can have change-control work outside its repositories. Revising an operating procedure is one instance: the change still needs an appropriate review, although there may be no pull request.

How do emergency changes fit our CC8 controls?

Urgent work belongs in a defined emergency-change process. Testing and approval remain part of the AICPA's Trust Services Criteria for these changes. The company's procedure determines the follow-up review, and the records need to show both the emergency decision and that review.

What records help us explain a production change?

Records help when they identify the same change across the request, approval, tests and deployment. Otherwise, a reviewer has to establish those connections afterwards. The CC8.1 guide explains how the evidence relates to the change and the process used to release it.

What changes when a coding agent writes the code?

The approved process still applies. An agent may have permissions or use a workflow that differs from the one engineers normally use. Those differences can let changes bypass a review. ZeroTB's change and development work addresses the rules and checks involved.

Does ZeroTB need write access to begin checking change controls?

Read-only access comes first. Repair permissions are granted by class of action, with material changes normally presented as pull requests. Your system owner can review the proposed change before it runs. The security overview gives the details of this access model.

Where does ZeroTB keep our change-control evidence?

ZeroTB keeps the change-control commitments, checks, repairs and evidence together. ZeroTB produces portable, signed evidence of completed repairs for audit review. The Verified Control Record connects the commitment, before-and-after state, action, approval and verification.

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 signed records of the repairs, approvals and checks completed in your own systems.