Skip to content
    Back to Insights
    GRC & Compliance

    Building a Vendor Risk Management Programme That Actually Works

    Jaouhar Mosbahi15 December 20257 min read

    Third-party risk management is one of those domains where the gap between theory and practice is enormous. In theory, every vendor that accesses your data or connects to your systems should be assessed, monitored, and governed with the same rigour as your internal controls. In practice, most organisations have a shared spreadsheet that was last updated six months ago, a vendor questionnaire that nobody enjoys sending or receiving, and a process that ranges from inconsistent to non-existent. When you are managing 48 or more suppliers, and most organisations underestimate their count, the spreadsheet approach does not just struggle. It fails.

    The fundamental problem with unstructured vendor risk management is that it treats all vendors equally. Your cloud infrastructure provider, which hosts all of your customer data and has privileged access to your production environment, receives the same assessment as the office supplies vendor. This wastes effort on low-risk vendors while under-scrutinising critical ones. The solution is a risk-tiering methodology that categorises vendors based on the actual risk they present to your organisation and applies proportionate assessment and monitoring based on that tier.

    An effective risk-tiering methodology considers several factors: the type and sensitivity of data the vendor accesses or processes, the criticality of the service to your operations, the degree of system integration or network access, the vendor's access to your customer data specifically, regulatory implications such as cross-border data transfer, and the availability of alternative providers. Using these factors, vendors are classified into tiers. Critical tier includes vendors whose failure or compromise would directly impact customer data or core operations. High tier covers vendors with significant access to sensitive internal data or systems. Medium tier applies to vendors with limited data access but meaningful operational relevance. Low tier is reserved for vendors with no data access and minimal operational dependency.

    Assessment depth and frequency should map directly to the tier. Critical vendors warrant a comprehensive initial assessment including security questionnaire, SOC 2 or ISO 27001 report review, data processing agreement review, and potentially an on-site or virtual assessment. These vendors should be reassessed annually at minimum, with continuous monitoring of their security posture between assessments. High-tier vendors should receive a detailed questionnaire and certification review, with annual reassessment. Medium-tier vendors can be assessed with a lighter-touch questionnaire and biennial review. Low-tier vendors may require only basic due diligence at onboarding.

    The vendor questionnaire itself deserves attention. Most organisations use a generic questionnaire pulled from the internet, running to hundreds of questions that take weeks to complete. This creates friction with vendors who deprioritise responding, delays onboarding of business-critical tools, and generates data that nobody has the capacity to properly analyse. A better approach is a tiered questionnaire that matches the assessment depth to the vendor tier. For critical vendors, a comprehensive questionnaire covering information security governance, access management, encryption, incident response, business continuity, data handling, and subprocessor management is appropriate. For medium-tier vendors, a focused questionnaire on the specific risk areas relevant to the engagement is sufficient.

    Continuous monitoring represents a paradigm shift from the traditional point-in-time assessment model. A vendor may pass your annual assessment in January and suffer a significant breach in March. Without continuous monitoring, you would not know until the next annual review, by which time your data may have been compromised for months. Continuous monitoring tools and services can provide ongoing visibility into vendor security posture through external attack surface scanning, breach notification databases, financial stability indicators, regulatory action monitoring, and dark web monitoring for exposed credentials. These tools do not replace periodic assessments, but they close the gap between them.

    Integration with your Information Security Management System is essential for vendor risk management to be sustainable. If vendor risk exists as a standalone programme disconnected from your ISMS, it becomes an isolated compliance exercise. Within an ISO 27001 framework, vendor risk management maps to Annex A control 5.19 (Information security in supplier relationships) and related controls covering the supply chain. Your vendor risk register should feed into your overall risk register. Vendor-related incidents should flow through your incident management process. Vendor assessments should be included in your internal audit programme. This integration ensures that vendor risk is treated as an integral part of your security posture, not an afterthought.

    Managing 48 or more suppliers effectively requires some degree of tooling and automation. At a minimum, you need a centralised vendor register that records key information: vendor name, business owner, tier classification, services provided, data accessed, contract terms, assessment status, and next review date. Many organisations start with a structured spreadsheet and this is acceptable initially, but the limitations become apparent quickly as the vendor count grows. GRC platforms such as Vanta, Drata, or ServiceNow GRC can automate vendor inventory management, questionnaire distribution, response tracking, and review scheduling. The investment in tooling pays for itself in reduced manual effort and improved consistency.

    Contract management is the often-overlooked foundation of vendor risk management. Your ability to enforce security requirements, conduct audits, require breach notification, and terminate for cause all depend on your contractual arrangements. Every vendor that accesses personal data should have a Data Processing Agreement in place. Every vendor in your critical and high tiers should have contractual clauses covering minimum security requirements, right to audit, breach notification timelines, data return and destruction upon termination, and subprocessor approval requirements. Reviewing and negotiating these terms should be part of the vendor onboarding process, not a retroactive exercise.

    One of the most effective practices we have implemented across client engagements is the vendor risk review meeting. This is a monthly or quarterly meeting where the security team, procurement, and relevant business owners review the vendor register, discuss upcoming renewals and new vendor requests, review any vendor-related incidents or findings, and make decisions about vendor risk acceptance or remediation requirements. This meeting creates accountability, ensures business context informs risk decisions, and prevents vendor risk management from becoming a purely administrative exercise that happens in isolation.

    Handling vendor incidents and breaches requires a defined process that is separate from but connected to your overall incident response plan. When a vendor discloses a breach, your team needs to rapidly assess whether your data was affected, determine notification obligations to your own customers and regulators, document the timeline and your response actions, evaluate whether the vendor's response meets your expectations, and decide on any remediation requirements or relationship changes. This process should be documented, tested, and understood by the relevant stakeholders before a vendor incident occurs.

    Subprocessor management adds another layer of complexity. Your critical vendors likely use their own third-party services to deliver their product, and some of those subprocessors may process your data. The EU GDPR and similar regulations require visibility and control over this chain. Your contracts should require vendors to disclose their subprocessors, notify you of changes, and ensure subprocessors meet equivalent security standards. In practice, most SaaS vendors publish a subprocessor list and provide change notifications. Reviewing these notifications and assessing the impact should be part of your ongoing vendor monitoring process.

    Metrics and reporting bring the programme together and demonstrate value to leadership. Key metrics for a vendor risk management programme include total vendor count by tier, percentage of vendors with current assessments, average time to complete vendor assessments, number of overdue assessments, vendor-related risk findings by severity, time to remediation for vendor risk findings, and the number of vendors with expired or missing contracts. Reporting these metrics to management quarterly provides visibility into programme health and helps justify resource allocation. When leadership can see that 15 percent of critical vendors have overdue assessments, the conversation about resources becomes much more productive.

    Building a vendor risk management programme that actually works is not about creating a perfect system on day one. It is about establishing a risk-proportionate, operationally sustainable process that improves over time. Start with your critical vendors: identify them, assess them, establish contracts, and monitor them. Then extend the programme tier by tier. Accept that the programme will mature incrementally and that your first-year assessments will be simpler than your third-year assessments. The goal is not perfection but consistent, risk-informed management of your supply chain risk that scales with your organisation.

    Vendor RiskThird-Party RiskSupply ChainGRC