Your vendors are an extension of your attack surface. A structured third-party risk management program is no longer optional — it is a compliance requirement and a business necessity.
The SolarWinds attack. The MOVEit breach. The Change Healthcare incident. The most consequential security events of the past several years share a common thread: they did not originate inside the victim organization. They came through a trusted third party.
Your vendors, partners, and subprocessors are an extension of your attack surface. The data you share with them, the access you grant them, and the systems they connect to your environment all represent risk that your security program must account for.
Third-party risk management (TPRM) is the discipline of identifying, assessing, and managing that risk. It is also increasingly a compliance requirement — SOC 2, ISO 27001, NYDFS, HIPAA, and CMMC all include explicit third-party risk management obligations.
Why Third-Party Risk Is Undermanaged
Most organizations significantly underestimate their third-party exposure. The reasons are predictable:
Vendor sprawl. The average small and mid-sized company uses hundreds of SaaS applications. Many were adopted by individual teams without security review. The security team often does not have a complete picture of what vendors have access to what data.
Questionnaire fatigue. The standard approach to vendor assessment — sending a security questionnaire and reviewing the response — is time-consuming, inconsistent, and often produces responses that are more aspirational than accurate.
No ongoing monitoring. Even organizations that assess vendors at onboarding rarely reassess them over time. A vendor that was low-risk two years ago may have been acquired, had a breach, or changed their security practices significantly.
Unclear ownership. Who is responsible for vendor security? Procurement? Legal? IT? Security? The answer varies by organization, and unclear ownership means gaps.
Building a TPRM Program That Works
An effective third-party risk management program has five components:
1. Vendor Inventory
You cannot manage risk you cannot see. The first step is building a complete inventory of your vendors and the nature of each relationship.
For each vendor, document:
- What data they access or process
- What systems they connect to
- What level of access they have
- What contractual security obligations they have
- Who internally owns the relationship
This inventory is the foundation of everything else. It also tends to surface surprises — vendors with access to sensitive data that no one in security knew about.
2. Risk Tiering
Not all vendors represent the same level of risk. A vendor with access to your production database is not the same risk as a vendor who provides your office coffee service.
Tier your vendors based on the sensitivity of the data they access, the criticality of the systems they connect to, and the nature of their access. A common approach is three tiers:
Tier 1 (Critical): Vendors with access to sensitive data or critical systems. Full security assessment required, including questionnaire review, evidence review, and potentially on-site or virtual assessment.
Tier 2 (High): Vendors with limited access to sensitive data or non-critical systems. Streamlined assessment with questionnaire and evidence review.
Tier 3 (Standard): Vendors with no access to sensitive data or systems. Lightweight assessment or self-attestation.
3. Assessment Process
For Tier 1 and Tier 2 vendors, your assessment should go beyond a questionnaire. Request and review:
- SOC 2 Type II report (or equivalent)
- Penetration test results (executive summary at minimum)
- Security policies relevant to their service
- Incident response procedures
- Subprocessor list and their security obligations
For vendors without SOC 2 or equivalent, your questionnaire needs to be more rigorous and your evidence review more thorough.
4. Contractual Controls
Security assessments identify risk. Contracts allocate it. Your vendor agreements should include:
- Data processing agreements (DPAs) with clear security obligations
- Right to audit provisions
- Breach notification requirements (timing, scope, process)
- Subprocessor restrictions and approval requirements
- Data return and deletion obligations at contract termination
Many organizations have vendor contracts that are silent on security. That silence is a risk.
5. Ongoing Monitoring
Vendor risk is not static. Your TPRM program needs a monitoring cadence:
- Annual reassessment for Tier 1 vendors
- Biennial reassessment for Tier 2 vendors
- Continuous monitoring for critical vendors using threat intelligence feeds and breach notification services
- Triggered reassessment when a vendor has a security incident, is acquired, or significantly changes their service
TPRM and Compliance
Third-party risk management is explicitly required by most major compliance frameworks:
SOC 2: The Common Criteria include requirements for vendor management, including assessing vendor security and including security obligations in contracts.
ISO 27001: Annex A includes a dedicated control domain for supplier relationships, covering security requirements in supplier agreements and monitoring of supplier service delivery.
NYDFS (23 NYCRR 500): Requires covered entities to assess the cybersecurity practices of third-party service providers and include security requirements in contracts.
HIPAA: Business Associate Agreements (BAAs) are required for all vendors who handle protected health information, and covered entities must ensure BAAs include appropriate security obligations.
CMMC: Requires contractors to flow down CMMC requirements to subcontractors who handle Controlled Unclassified Information (CUI).
The GRC2 Approach
We help organizations build TPRM programs that are practical, scalable, and aligned to their compliance obligations. We start with the vendor inventory — which is almost always more complex than the organization expects — and build a tiering and assessment process that is proportionate to the actual risk.
The goal is not a perfect program on day one. It is a program that meaningfully reduces third-party risk, satisfies your compliance requirements, and can be sustained by your team over time.
Related reading: AI supply chain risk — what your vendors aren't telling you | SOC 2 compliance guide | GRC2 vendor and AI supply chain risk services
Explore Topics
Written by
GRC2 Advisory Team
Content creator and writer sharing insights and stories.