Every vendor is a door into the business. A courier holds customer addresses, a marketing agency has access to ad accounts, a payroll tool holds salary data, and a reseller may have administrator credentials. The risk is not that vendors are untrustworthy. It is that their security posture can change without your knowledge, and your name is still on the customer relationship.
This guide explains what third-party security risk costs, how to scope an assessment programme and how to keep the cost proportional to the exposure.
What counts as a third party
Suppliers, SaaS providers, IT support firms, cloud hosts, payment providers, logistics and courier partners, marketing and creative agencies, freelancers, resellers, recruitment firms, payroll processors and any subcontractor that touches your data or systems. The list is usually longer than expected, because procurement rarely sees every tool a department buys with a corporate card.
Risk categories
- Data exposure: personal data, pricing, contracts, payroll and customer lists.
- Access risk: admin credentials, integrations, shared accounts and remote support tools.
- Operational dependency: a single vendor, no tested exit and a long recovery time.
- Financial and contractual: liability limits, auto-renewal, insurance and unclear breach costs.
- Compliance: data protection, sector rules and client audit requirements.
- Concentration and subcontracting: the same small supplier behind several critical services.
Tier vendors by data access, system access, business criticality and substitutability. A design agency with a public social account is not the same risk as a payroll processor with bank details. Review the tiering when a vendor gains new access or is acquired.
Likelihood and impact
Do not score every vendor with the same rubric. Ask two questions: how likely is a failure at this vendor, and how much would it hurt? Likelihood rises with data volume, privileged access, subcontracting and a weak security programme. Impact rises with regulatory exposure, customer trust, revenue dependency and the cost of replacement.
A high-likelihood, low-impact vendor can be handled with a standard clause. A low-likelihood, high-impact vendor needs an exit plan and a tested incident path even if the questionnaire looks clean.
What drives the cost
- Vendor count and tiering: more vendors mean more assessments and more contract reviews.
- Assessment depth: questionnaire, evidence review, interview, site visit, penetration test evidence or certification review.
- Legal review: security schedule, liability, breach notification, data return and termination.
- Technical review: integration design, access model, data flows and logging.
- Ongoing monitoring: certificate expiry, news, incident alerts and annual reassessment.
- Onboarding time: security review before access is granted, not after.
- Incident response: forensics, notification, customer support and legal costs.
- Remediation: changing integrations, reducing access or replacing a vendor.
- Tooling and training: vendor register, questionnaire platform and staff awareness.
A cost model
Programme cost = inventory and tiering + due diligence + contract review + monitoring + incident reserve
Price each line in effort days and annual cadence. Critical vendors may need a deep assessment every year and a light check at renewal. Medium vendors may need a questionnaire and evidence review. Low-risk vendors may need only a standard clause and a register entry.
Build your own estimate
- Count vendors by tier: critical, high, medium and low.
- Choose the assessment depth for each tier and the review frequency.
- Add legal hours for new contracts and renewals.
- Add monitoring tooling and the internal owner's time.
- Add a contingency for incident response and remediation.
- Ask providers for unit rates so the estimate can be compared.
Controls that reduce the cost of risk
- A short security questionnaire before contract signature, with evidence.
- A security schedule covering access, encryption, breach notification, subcontractors and data return.
- Least-privilege access, single sign-on and multi-factor authentication for vendor accounts.
- A named owner and an offboarding checklist for every vendor.
- Annual reassessment for critical vendors and a trigger-based review after an incident or ownership change.
- A tested exit plan for the top five vendors.
Contract clauses that carry the most weight
- Breach notification within a defined window, with a named contact.
- Security requirements that are specific enough to test.
- Right to audit or to receive independent assurance evidence.
- Subprocessor approval and a current list of subcontractors.
- Data return and deletion at termination, in a usable format.
- Liability and insurance that match the data and access involved.
- Transition assistance and a notice period that allows an exit.
Questions to ask a vendor
- Which data do you hold, where is it stored, and who can access it?
- How quickly would you notify us of a breach, and through whom?
- Which subcontractors support the service, and how are they assessed?
- Can you provide independent assurance evidence that matches our risk tier?
- What happens to our data at termination, and what does the exit plan include?
Board questions
- Which vendors can access customer data, move money or change production systems?
- Which vendor failure would stop the business this week?
- Do we have evidence of their controls, or only an assurance in a sales deck?
- What is our notification and containment plan if a vendor is breached?
- Do our contracts match the risk we carry?
- What are we doing about the top five gaps, and by when?
A 90-day plan
- Days 1-15: build the vendor register and tier by data, access and criticality.
- Days 16-35: assess the top ten vendors with a questionnaire and evidence review.
- Days 36-55: fix contract gaps and reduce unnecessary access.
- Days 56-75: set the monitoring cadence and assign owners.
- Days 76-90: report the top risks and the remediation plan to management.
Metrics
- The share of critical vendors assessed in the last 12 months.
- The share of contracts with security, breach and exit clauses.
- The number of vendors with administrator access.
- Time to onboard a new vendor, including security review.
- Incidents involving a vendor and time to contain.
- Remediation actions closed on time.
Where this fits in our work
If you need help building a vendor risk programme, start with Managed Technology & Cybersecurity. The pricing page explains scope. For the operating rhythm, read the third-party security risk guide.
Sources
- NIST SP 800-30, Guide for Conducting Risk Assessments, accessed 17 November 2026.
- NIST, Cybersecurity Framework 2.0, accessed 17 November 2026.
- IBM, Cost of a Data Breach Report 2026, accessed 17 November 2026.
- World Economic Forum, Global Cybersecurity Outlook 2026, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive amid rising threats", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.