OneNym.idDiscuss deployment
English

THE BOARDROOM FIREWALL / Chapter 8

Your Suppliers Are Your Risk Too

Every supplier that holds your data, connects to your systems or keeps your operations running is holding a spare key to your house. This chapter explains how a leader can judge those suppliers without theatre and limit the damage when one of them fails.

This page summarises the chapter. The full text is in the book.

Knowing who holds a key

Many of the most damaging recent incidents began not with an attack on the victim but on a supplier that became a doorway into its customers. The first step sounds easy and rarely is: knowing who your suppliers are. Procurement sees the large contracts, but teams also sign up for tools on credit cards, engineers connect services and forget them, and shared links stay open for years.

The goal is an inventory of the third parties that matter: those holding sensitive data, those able to connect to your systems, and those whose failure would stop operations even if they never touch your data. Sort them into tiers, concentrate effort at the top, and refresh the list, because small tools quietly become critical. When the fictional Meridian Foods compared lists, procurement had twenty-two critical suppliers while security found one hundred and forty organisations with access. Thirty-one belonged in the top tier, twelve had never been reviewed, and one small marketing analytics tool held a copy of the customer loyalty database.

Due diligence without the theatre

Sending the same three-hundred-question questionnaire to every supplier, filing the copied answers and never reading them, produces a feeling of safety rather than safety. Better due diligence is proportionate: real effort for top-tier suppliers and a short check for the rest. Ask fewer, sharper questions relevant to the relationship, ask for evidence such as independent audit reports or certifications rather than bare claims, look at how the supplier handled past incidents, and do the most work before signing, when you still have leverage. Top-tier suppliers deserve a light annual review and an immediate one after an acquisition, a public incident or a major service change.

For practitioners, the chapter explains why a SOC 2 Type II report, which tests controls over a period, is stronger evidence than a Type I, why the scope of an ISO 27001 certificate decides what it covers, and why the exceptions and the controls a report expects the customer to operate deserve close reading.

Concentration risk: many eggs, one basket

Concentration risk is heavy dependence on one provider, or on a few providers that many other companies also rely on. Each consolidation decision may be sensible alone, yet together they can turn one supplier's bad day into your bad week. When a shared provider fails, thousands of firms are affected at once and recovery help is scarce. The practical responses are a fallback for the most critical services, your own copy of key data, contracts that let you leave with your data, and rehearsal.

At Meridian, ordering, the customer app, email and backups all ran with one cloud provider, chosen by different teams in different years; the fix was a second location for backups and an agreed way to communicate if usual tools failed. A similar question about payroll led to a simple plan: keep a copy of each month's final payroll and, if the provider is unavailable, pay the previous month's net amounts through the company's own bank and correct later.

Contracts: writing the rules early

A good contract does not prevent a breach, but it ensures you hear quickly and are not left alone with the consequences. Leaders should check five areas in critical contracts: breach notification within a defined number of hours rather than a vague promptly, since a supplier's delay uses up your own regulatory clock; a right to audit or at least to independent reports; service levels, remembering that service credits are a discount, not compensation for lost business; data location, use, return and deletion; and naming and controlling subcontractors. Where terms are not negotiable, the task shifts to understanding them and covering the residual risk with fallbacks or insurance.

Other people's code and outsourced IT

Modern software is largely assembled from outside components, many of them open source. A weakness in a widely used component, or a malicious update slipped into a supplier's software, can affect thousands of organisations at once. A software bill of materials, an ingredients list for software, lets a company answer whether it is affected in hours rather than days. When news of one such weakness broke, Meridian checked its own app within the hour while several suppliers took a week to reply.

Many smaller firms outsource IT entirely to a managed service provider. The work can be handed over; the accountability and risk cannot. Contracts often cover keeping systems running but say little about protecting them, and a provider holding keys to many clients is an attractive target. Meridian found its distribution centre's provider sharing one administrator login without multi-factor authentication, and renegotiated for individual logins, multi-factor authentication, a patching commitment and breach notification within twenty-four hours.

KEY POINTS

Key points

  • Keep one current, owned list of suppliers that hold data, connect to systems or are critical to operations.
  • Focus due diligence on the top tier and ask for evidence rather than questionnaire answers.
  • Identify where the business depends on a single provider and rehearse a fallback for a week-long outage.
  • Require breach notification within a defined number of hours in critical contracts.
  • Make sure the company can say quickly which outside software components its key systems contain.
  • Check that outsourced IT contracts cover protecting systems, not only keeping them running.

QUESTIONS

Common questions

How should a company assess the cybersecurity of its suppliers?
Start by listing every supplier that holds sensitive data, can connect to your systems or would stop operations if it failed, then sort them into tiers. Concentrate due diligence on the top tier with a few sharp, relevant questions and ask for evidence such as independent audit reports, not just answers. Review top-tier suppliers lightly each year and again after major changes such as an acquisition or a public incident.
What is concentration risk in cybersecurity?
Concentration risk is heavy dependence on a single provider, or on a small number of providers that many companies share. One provider's outage or breach can then stop large parts of your business, and when many firms are hit at once, recovery help is scarce. The answer is not to eliminate concentration but to know where it lies, keep your own copy of critical data and plan a fallback for essential services.
What security clauses should be in a supplier contract?
Critical contracts should require breach notification within a defined number of hours, give you a right to audit or to independent assurance reports, and set clear service levels. They should also say where your data is stored, who can use it and how it is returned and deleted when the contract ends, and require the supplier to disclose and control its subcontractors. Service credits for missed service levels are a discount, not compensation for lost business.
What is an SBOM and why does it matter to executives?
A software bill of materials, or SBOM, is an ingredients list showing which outside components a piece of software contains. When a serious weakness is found in a widely used component, an SBOM lets the company answer whether it is affected, and where, within hours instead of searching for days. Executives should ask whether the team can quickly say what is inside the company's most important systems.
If we outsource IT to an MSP, who is responsible for security?
You remain accountable. Outsourcing to a managed service provider hands over the day-to-day work, not the responsibility or the risk. Many MSP contracts cover keeping systems running but not protecting them, so check what independent assurance the provider has, how it separates clients and controls its own staff's access, how fast it will notify you of an incident, and how you get your data back if you leave.