SOC 2 ControlsVendor ManagementThird-Party RiskCC9SOC 2

Vendor Risk Management for SOC 2: CC9.2 in Practice

A practical approach to third-party vendor risk management that satisfies SOC 2 CC9.2 without drowning in spreadsheets.

SecureSpect Team··8 min read

What SOC 2 CC9.2 Requires

CC9.2 requires that you assess the risks posed by your vendors and business partners, and monitor those relationships over time. Your auditor will want to see:

  • An inventory of all vendors with access to your systems or customer data
  • A risk-based approach to vendor classification
  • Evidence of due diligence (security questionnaires or SOC 2 reports) for critical vendors
  • Ongoing monitoring — not just a one-time assessment
  • Building Your Vendor Inventory

    Start with a complete list. Pull vendors from:

    • Your billing systems (SaaS subscriptions)
    • Infrastructure providers (cloud, CDN, DNS)
    • HR systems (payroll, benefits, recruiting tools)
    • Any system with access to customer data or production infrastructure
    A typical growth-stage SaaS company has 30–80 relevant vendors. Focus due diligence effort on those that are critical: vendors whose compromise or outage would directly affect your customers.

    Vendor Tier Classification

    Tier 1 — Critical

    Access to production data, source code, or infrastructure. Examples: AWS, GitHub, Okta, your database vendor.

    Required due diligence: SOC 2 Type II report (or equivalent), annual security questionnaire, contract DPA/BAA.

    Tier 2 — Important

    Operational dependency, but no direct access to customer data. Examples: Slack, Jira, your ticketing system.

    Required due diligence: Security questionnaire or SOC 2 summary, review at contract renewal.

    Tier 3 — Standard

    Low-risk, no data access. Examples: Calendaring tools, expense management.

    Required due diligence: Standard contractual terms, no annual review required.

    The Security Questionnaire

    For Tier 1 vendors without a current SOC 2 report, send a security questionnaire. Key topics:

    • Do you have a SOC 2 report? (If yes, request it)
    • Do you encrypt data at rest and in transit?
    • How do you handle security incidents affecting customer data?
    • What is your SLA for security patches?
    • Do you conduct penetration testing? How often?

    SecureSpect's vendor management module includes a standard questionnaire template aligned with VSA (Vendor Security Alliance) that you can send to vendors and track responses within the platform.

    Using Vendor SOC 2 Reports

    When a vendor provides their SOC 2 report, review the complementary user entity controls (CUECs). These are controls that your vendors expect YOU to implement. Missing CUECs can generate audit findings for your own SOC 2.

    For example, a cloud infrastructure vendor's SOC 2 might require that you:

    • Use MFA for all console access
    • Monitor access logs
    • Encrypt data before storing it

    Ongoing Monitoring

    Annual reviews are the minimum. For Tier 1 vendors, also monitor:

    • Vendor security incident notifications (subscribe to status pages and security bulletins)
    • SOC 2 report renewals (request the new report when it's issued)
    • Changes in data processing agreements

    SecureSpect tracks vendor review due dates and sends reminders 30 days before expiry.

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles