SOC 2 CC5 concerns the controls a company chooses to address risk, the technology supporting them, and the procedures people follow. CC3 establishes which risks need attention. CC5 turns those decisions into work, while CC4 evaluates whether that work achieves its purpose.
The three CC5 criteria
CC5.1
Control selection
Choose activities that address identified risks and reduce the likelihood of failing to meet business objectives.
CC5.2
Technology controls
Establish controls over the technology that business activities depend on, including the systems supporting automated checks.
CC5.3
Policies and procedures
Put policy requirements into practice through procedures that define the work and responsibility for carrying it out.
Gaps in control execution
A scheduled check can run successfully and still miss part of its job. If it loses access to a source, it may continue using incomplete information. The written procedure has stayed the same, while the activity now leaves one system unexamined.
Source access changes
Check loses an input
System coverage becomes incomplete
Control restoration with ZeroTB
ZeroTB handles the repair when a control fails its check. We read the commitment and compare it with the system, then draft the fix for approval. After the change, we check the result and save the evidence in a signed Verified Control Record.
Daily checks follow the approved commitment
People authorize material changes to systems
Completed repairs produce evidence for review
Talk to our team
Talk with us about control activities that have become difficult to maintain and where the work needs attention.
FAQ
Who needs to be involved in CC5 control work?
CC5 involves both control owners and the people who operate the supporting systems. Control owners decide which risks an activity addresses. Technology and operational owners assess changes that affect it. ZeroTB carries the agreed control work through with those owners, who retain decisions about commitments, material changes and exceptions.
What evidence helps explain whether a control activity works?
The control's rationale, procedure, relevant settings and operating records explain what it should do and what actually happened. When ZeroTB restores a control, its Verified Control Record connects the commitment, before-and-after state, action, approval and verification. A reviewer can follow the repair from the original requirement to the verified result.
When does a control activity need reconsideration?
Changes to risks, systems or procedures can require a different activity. For example, a check configured before a new system arrived may never examine that system. The owner decides whether its coverage needs to change. ZeroTB works against the agreed commitments for those systems.
How does ZeroTB handle a check that cannot read its source?
Unknown, stale and disconnected states remain visible in ZeroTB. If a check cannot reach its source, it cannot confirm the current state of that system. The people responsible for the control can see where information is missing and where the check has established a result.
Can ZeroTB keep records of our control activities?
Yes. ZeroTB keeps the commitments, checks and repair evidence for the controls in your compliance program. ZeroTB operates alongside that program. We handle the work needed to restore failing controls in the affected systems and keep evidence of each completed repair.
Can the same control activity support another framework?
Yes, if the activity meets the requirements of each framework. A technology control or procedure can support commitments under SOC 2, ISO 27001 and HIPAA. ZeroTB maintains shared controls against those commitments. The activity, its purpose and the systems it covers determine which requirements it can satisfy.
Start with the Pilot
The eight-week Pilot maps up to 25 commitments from your SOC 2 report and takes two real control gaps through verified restoration. You receive working controls and portable evidence records that document the completed repairs.