CC9.2 is one of the most consistently underprepared areas in SOC 2 readiness. It's not that organizations don't have vendors — they do. It's that their vendor management program, if it exists at all, doesn't have the documentation structure that auditors are looking for. The result is a criterion that should be straightforward to satisfy but routinely produces findings.
What CC9.2 Requires
CC9.2 sits in the Risk Mitigation grouping of the Common Criteria. The full criterion states: "The entity assesses and manages risks associated with vendors and business partners."
Unpacked, this means:
- You have a documented inventory of vendors who could affect the achievement of your security objectives
- You assess the risk those vendors represent — and your assessment is risk-based, not flat
- You conduct due diligence at vendor onboarding and at defined intervals thereafter
- You have contractual requirements that bind vendors to appropriate security standards
- You monitor the relationship over time, not just at the point of contracting
Each of these has an evidence component. "We manage our vendors responsibly" isn't evidence of CC9.2 compliance. A vendor inventory, risk ratings, security questionnaires, reviewed SOC 2 reports, and contract provisions are.
Vendors vs. Subservice Organizations
SOC 2 distinguishes between vendors who are "subservice organizations" and vendors who are simply vendors.
Subservice organizations provide components of your service that your customers depend on — your cloud provider (AWS, Azure, GCP), your CDN, your payment processor, your authentication provider. These are addressed in your System Description through the carve-out or inclusive method. They're a separate conversation from CC9.2.
Vendors under CC9.2 are the broader universe of third parties who touch your data, systems, or operations — your IT managed service provider, your software development contractors, your HR platform if it stores employee data, your CRM, your email service. These don't appear in your System Description but are subject to CC9.2.
The distinction matters because auditors expect different treatment for each category. Confusing a subservice organization (addressed in scope) with a CC9.2 vendor creates gaps in both directions.
Building the Vendor Inventory
Your vendor inventory needs to cover every third party who:
- Has access to systems in scope for your SOC 2
- Processes, stores, or transmits data (customer data, employee data, confidential business data) on your behalf
- Provides a service where their failure would materially affect your service delivery
For most SMBs and mid-market companies, this list is between 15 and 40 vendors. Start by going through your expense records and subscription list — you'll find vendors that aren't on anyone's mental inventory.
For each vendor, document: vendor name, service provided, data they access or process, criticality to your service, and the current status of your risk assessment.
Risk Tiering
A flat vendor management program — treating every vendor with the same level of scrutiny — is both impractical and not what auditors are looking for. CC9.2 expects a risk-based approach.
A practical three-tier model:
Tier 1 — Critical vendors: Vendors whose compromise or failure would materially affect the confidentiality, availability, or integrity of your service. They have direct access to customer data or production systems. Examples: your cloud provider, database vendor, identity provider, key SaaS tools with customer data access.
Tier 1 vendors should be assessed annually. Evidence of assessment: their current SOC 2 Type 2 report (reviewed, not just received), a completed security questionnaire if they don't have a SOC 2, contract with security addendum.
Tier 2 — Important vendors: Vendors with some access to business data or operational systems, but whose compromise would have limited direct impact on customer data. Examples: collaboration tools, internal IT management systems, HR software.
Tier 2 vendors warrant security questionnaire completion at onboarding and review on an 18-24 month cycle.
Tier 3 — Standard vendors: Vendors with no access to customer data or production systems. Routine business tools. Assessed at contracting and reviewed only on significant changes.
Auditors don't expect Tier 1 rigor for every vendor. They do expect that your highest-risk vendors receive meaningful scrutiny and that the distinction between tiers is documented and rational.
What "Reviewing a SOC 2 Report" Actually Means
The most common mistake in SOC 2 vendor management programs: collecting vendor SOC 2 reports and filing them without reading them. Having a vendor's SOC 2 report on file is not the same as having reviewed it.
When you receive a vendor's SOC 2 Type 2 report, the review involves three things:
1. Check the coverage period and opinion type: Is the report current? A SOC 2 report issued 18 months ago has limited value. Is it a Type 2 (operating effectiveness over a period) or Type 1 (design at a point in time)? Type 2 provides more assurance.
2. Read the exceptions section: The auditor's report will list any exceptions — controls that were tested and found not to be operating effectively during the period. An exception doesn't automatically disqualify a vendor, but you need to evaluate whether it affects your use of their service and what compensating controls you have.
3. Read the complementary user entity controls: Every SOC 2 report includes a section describing controls that the user entity (you) is expected to implement for the vendor's controls to be effective. These are the controls your vendor assumes you have in place. If you don't have them, their controls don't cover what you thought they did.
Example: An identity provider's SOC 2 might note that user entity controls include enforcing MFA in the user entity's tenant configuration and reviewing access permissions at defined intervals. If you haven't enforced MFA in your tenant, that complementary control gap is your problem, not theirs.
Document your review: date reviewed, period covered, exceptions noted and your assessment of their impact, complementary user entity controls and your status on each. This is what "vendor SOC 2 review" looks like in an audit file.
Contract Requirements
CC9.2 expects that your contracts with Tier 1 and Tier 2 vendors include appropriate security provisions. These don't need to be elaborate, but they need to exist and be specific:
- Confidentiality obligations covering the data you share
- Requirement to maintain appropriate security safeguards (or comply with a named standard like SOC 2, ISO 27001)
- Breach notification obligation with a defined timeline (typically 24-72 hours, or 30 days for confirmed breaches)
- Right to audit or require security questionnaire completion
- Data handling and destruction requirements on contract termination
Contracts that predate your SOC 2 program are a common gap. If you have critical vendors on agreements that don't include security provisions, adding a security addendum is worth pursuing before your audit.
Monitoring Over Time
CC9.2 isn't satisfied by doing the work once at onboarding. Auditors look for evidence of ongoing monitoring:
- Annual review of Tier 1 vendor SOC 2 reports as new ones are issued
- Follow-up when a vendor has a security incident that could affect your environment
- Process for evaluating new vendors before they're onboarded
- Process for offboarding vendors — access revocation, data return or destruction, contract termination
Monitoring is where most programs fall apart. The onboarding process is usually documented. The annual review cycle and the offboarding process frequently aren't.
SOURCES
- AICPA, Trust Services Criteria (2017, updated 2022), CC9.2: aicpa-cima.com
- AICPA, SOC 2 Vendor Management Guidance: aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services
- NIST SP 800-161 Rev. 1, Cybersecurity Supply Chain Risk Management Practices: csrc.nist.gov/publications/detail/sp/800-161/rev-1/final
Building a vendor management program for SOC 2 or want a review of what you have? Schedule a consultation to walk through your vendor inventory and what CC9.2 evidence looks like at audit time.
