The information customers need to use a service safely
A customer enables your new integration. They assume you monitor every administrative action made through it. Your team assumes their administrator reviews those actions. The gap only becomes visible when someone asks about an unexpected configuration change.
It is an uncomfortable conversation, especially when both teams have been acting in good faith. You need a shared understanding of where your responsibilities meet.
SOC 2 CC2.3 addresses communication with external parties about matters that affect internal control. The AICPA Trust Services Criteria provide the authoritative wording. Information needs to move both ways: your customers and suppliers need usable instructions, and your management team needs to hear about problems they discover.
This article in our SOC 2 Guide follows communication beyond your organization, including relevant exchanges with customers, suppliers, auditors, regulators, and other stakeholders. CC2.2 covered the internal side. You still need that internal clarity to decide who approves an external message and acts on the reply. The company scenarios below are fictional.
Start where responsibilities meet
Choose a point where your service depends on someone outside your team: customer account administration, supplier incident notification, outsourced support, or a partner’s access to information. Ask what each side needs to know to do its part safely.
Explain what your service does, its boundaries, and the relevant objectives people rely on. If confidentiality or privacy is in scope, communicate the protection objectives and changes that affect the other party’s work. A customer administrator may need offboarding instructions; a hosting provider may need your current emergency contact.
Put those responsibilities where the intended reader will use them, such as onboarding guidance, service documentation, agreements, and support instructions. Compare those sources. An old setup guide and an enthusiastic sales answer can quietly create expectations that differ from the agreement.
For the integration in our opening example, explain who reviews administrative activity and where the customer gets the records. Ask someone unfamiliar with the setup to follow the instructions. If they cannot find the information or explain the division of work, you have found something worth fixing before the next customer handoff.
Give incoming reports an owner
Look beyond whether your support address receives mail. Who checks it? Who covers an absence? What happens to an urgent report outside normal hours? Give that route an owner, coverage, and instructions for sensitive or time-critical messages.
Make it easy for customers to report a suspected service problem and for suppliers to tell you about an event affecting your service. Give vulnerability researchers a suitable way to send sensitive details rather than pushing them into an ordinary support conversation.
Provide a credible alternative when the normal channel fails or the concern involves its usual recipient. Be honest about confidentiality. Another address forwarding to the same unavailable person leaves the original problem in place.
Periodically send a clearly identified test message through the relevant route and verify its handling. Keep actual reports, assessments, and resulting actions. Significant external assessment findings should reach management and the board or appropriate governing body, with sensitive details limited to authorized recipients.
Plan for difficult communications
During an incident, you may have incomplete facts and several contractual obligations to interpret. Work out the approval process before that pressure arrives. Name who approves customer notices and who checks agreements and legal requirements.
Record the decision, approver, audience, channel, and timing. Separate confirmed facts from what you are still investigating. When facts change, correct earlier messages through the approved process and keep the history.
Choose a channel that fits the audience and urgency. A public status page may suit a broad interruption; a confidential issue affecting one customer may need a verified direct contact. Keep customer-specific details out of public updates.
There is no universal notification deadline you can safely apply to every event. Have qualified advisers assess the applicable agreements, law, and facts, then build the resulting obligations into your response process.
A five-person company with two founders
Imagine you handle customers and operations at a bootstrapped software company with two founders and three employees. Your cofounder runs the service, and one employee handles most support. A customer contacts that employee about access that looks inappropriate.
You have already agreed a simple route: the employee records the report and alerts the technical founder to assess it. You verify the customer contact and check communication obligations. You preserve what was communicated, when, and why, without circulating investigation details more widely than necessary.
To make that work consistently, the founders review a short customer guide against the service as operated. It explains account administration, supported data uses, and reporting routes. Your support employee checks that a new customer can follow it. You establish backup coverage and test both the general support address and the sensitive-reporting route.
Vanta’s Documents area can hold dated guidance and reporting-channel checks, with an owner responsible for current evidence. Keep the support ticket as the working record of the issue. An uploaded guide tells you what was available; delivery records tell you what a customer received.
Keep: guidance versions, verified contacts, reporting instructions, routing tests, real tickets, approved notices, and follow-up. Protect sensitive material and check that your coverage suits the service. A five-person business with consequential customer commitments may need more formal support than this example.
Coordinating communication in a 100-person company
At a fictional 100-person provider, a migration changes how customers export records. Engineering knows the technical steps, customer success knows the affected administrators, and security knows the access precautions. You need those pieces to become one usable message.
You assign an owner to coordinate the notice. The teams reconcile instructions, check contacts, record the recipients, and track unresolved questions before the migration proceeds. Owners also maintain standard security responses, implementation guidance, and supplier contacts so service changes trigger updates wherever customers may look.
A Vanta Trust Center can provide a consistent place for approved security documents and customer access requests. Review visibility, access conditions, and the accuracy of the published material. Features depend on your plan and configuration. Send any direct notices your agreements or time-sensitive changes require through the appropriate channel as well.
Keep the incoming side visible too. If procurement receives a critical supplier warning, route it into a tracked issue for the service owner. Make sure that warning remains findable after the original recipient leaves.
Keep: approved guidance, publication history, relevant customer and supplier populations, notices, delivery failures, escalations, and decisions about open questions. Where versions differ, retain the one each affected audience received.
Reaching the right audience across a 1,000-person company
Now imagine a significant outage at a 1,000-person company operating several services across regions. Your incident team prepares the common factual summary. Regional and account teams need to get it to the right contacts while respecting different agreements and language needs.
Give one owner responsibility for reconciling those audiences. Otherwise, two capable teams may each assume the other contacted an important customer. Keep the significant updates, corrections, and reasons for decisions made while facts were incomplete.
Afterward, review whether recipients got useful information in time and whether their questions reached the response team. Apply the same coordination to suppliers. An alert about a subcontractor supporting several services needs to reach every affected service owner, even if only one business unit received it.
For the examination, your compliance team could organize communication evidence and follow-up in Vanta’s audit workspace. Check auditor visibility and place clarifications on the engagement’s evidence rather than assuming internal notes are visible externally. Management decides what can be disclosed and ensures significant findings reach the right leaders.
Keep: communication responsibilities, service and regional contacts, approved messages, recipient and delivery records, supplier alerts, and post-incident actions. Give leadership useful summaries while protecting detailed case files.
What evidence should show during the period
For a SOC 2 Type 2 examination, retain records of relevant activity throughout the period. A current website screenshot shows today’s reporting instructions. Historical publication records and dated channel tests help explain what was available earlier. Actual tickets and notices show how the process operated when used.
Keep delivery failures and their resolution. A sent message may have reached a former employee or an unattended mailbox. Review contacts as relationships change, especially where a notice is time-sensitive.
If no reportable events occurred, keep evidence of the controls that did operate, such as contact reviews and channel checks. Do not invent incidents to populate a folder. Your auditor determines the evidence and testing needed for the engagement.
Use a relationship to test the process
Choose one customer and one critical supplier. Can both sides explain their responsibilities and reach the right person? Look at a recent exchange together for conflicting instructions or unanswered questions.
Build your review intervals and escalation arrangements around service complexity, data sensitivity, and contractual obligations. Headcount provides context, but your actual exposure should guide the design. Tools can help organize the records; your team makes the communication and disclosure decisions.
If you would like help working through those responsibilities, schedule a free consultation. Genius GRC helps you develop practical SOC 2 controls and organize supporting evidence.
Explore the SOC 2 Guide for the full series. Next is CC3.1, Specifying Suitable Objectives. This article provides general guidance; evaluate the examples with your advisers and auditor in the context of your examination scope and obligations.