Home / SOC 2

SOC 2 CC2 information and communication

SOC 2 CC2 covers information quality and communication inside and outside the company. A control owner needs information that is accurate and current to make a decision. People affected by that control also need to know their responsibilities and where to report problems.

Updated 4 November 2026

The three CC2 criteria

CC2.1

Information quality

A report needs to cover the systems and activities being reviewed, with information current enough for the decision.

Read the CC2.1 guide

CC2.2

Internal communication

People inside the company need to understand their control duties, changes to them and ways to report concerns.

Read the CC2.2 guide

CC2.3

External communication

Customers and other outside parties need control information and a way to communicate issues back to the company.

Read the CC2.3 guide

Gaps in control information

A control decision can look sound when the information behind it is incomplete. For example, a report can keep running after its source loses access to one production account. The control owner then reviews an account list that leaves out part of the system.

  1. Source access changes

  2. One account disappears

  3. The review misses active accounts

Operating checks with ZeroTB

ZeroTB handles the work behind the control status an owner reviews. We read the commitment and check the system against it. When we find a gap, we draft a repair for approval, check the result and retain a signed Verified Control Record of the work.

  • Stale or disconnected sources stay visible

  • People approve material changes to controls

  • Records preserve the observed state and approval

See which results have been checked
Quillon's control observations: the restored report-role control passing with its approved record, a disconnected Workday check left unresolved and shown as such, and a stale backup read.

Talk to our team

Talk with our team about the reports and control updates you depend on, and where information goes missing between audits.

FAQ

What evidence helps explain how our CC2 controls operate?

Evidence can include the source and coverage of a report, or the content and recipients of a message. These details connect the information to the control it supports. For a repair, ZeroTB retains the before-and-after conditions, action, approval and verification in the Verified Control Record.

Who makes decisions when a CC2 control needs to change?

Your control and system owners approve material changes. They also decide how to interpret the requirement and handle legitimate exceptions. ZeroTB investigates the gap and drafts corrective work. The owners review that proposed response before we carry out the approved repair.

Does external communication include issues reported to us?

Yes. A customer's report of a control problem is an incoming communication. CC2.3 covers that direction as well as the information a company sends outside. The AICPA's Trust Services Criteria include channels through which customers, suppliers and other outside parties can raise concerns.

How do we distinguish an information gap from a monitoring gap?

CC2 addresses the inputs and communication used to run controls; CC4 addresses evaluations of those controls and reporting the gaps they reveal. For example, an evaluation may expose a report that omits part of the system. Its coverage is a CC2 concern. Both themes appear in the SOC 2 framework.

What happens when ZeroTB cannot observe a connected system?

ZeroTB shows the state as unknown, stale or disconnected. A control owner reviewing the record can see where an observation is missing. This matters when a report still exists but its source has stopped supplying current information about the system.

Can we keep our CC2 control records in ZeroTB?

Yes. ZeroTB keeps your commitments, checks, repairs and evidence together. ZeroTB does the operating work and leaves portable evidence of completed repairs for your records. The framework library shows the broader requirements that the controls in your program may support.

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. The repair records let you review what changed in your systems and the checks used to confirm the result.