Business Continuity at Critical Suppliers: Dependency and Assurance

Identifying critical suppliers from the BIA, concentration risk, a question list that asks for evidence, continuity clauses in contracts and strategies for single-source dependency.
Technical summary
Technology
ISO 22301, ISO/TS 22318, ISO/IEC 27001:2022 Annex A 5.19–5.23
Topic
Managing the risk of disruption caused by critical suppliers
Level
Intermediate
Prerequisites
  • Business impact analysis and process dependencies
  • List of suppliers and contracts
In this article8 sections

Unless you’ve set up an alternative arrangement, your recovery capacity is only as good as your weakest critical supplier’s recovery capacity. Your own data center may have dual feeds and redundancy; when the cloud provider hosting your ERP, your single internet operator or the raw material you buy from a single source stops, the business still stops. Below we explain how to identify critical suppliers from the business impact analysis, how to question a supplier’s continuity capacity with evidence, the clauses to put in the contract and strategies against single-source dependency. The information security dimension of supplier risk is a separate topic; the focus here is the supplier’s ability to keep providing its service without interruption.

How do you identify a critical supplier?

The critical supplier list doesn’t come out of purchasing’s spend report; it comes out of the business impact analysis (BIA). A maintenance company with small annual turnover can be far more critical than a stationery supplier with large turnover. In the BIA, dependencies are recorded for each critical process: people, systems, facilities and suppliers. A supplier is critical when:

  • The process it supports is marked critical in the BIA and an outage at the supplier causes a disruption that exceeds this process’s RTO,
  • No other source can be brought in to replace it at short notice,
  • The supplier is part of your own recovery strategy (backup service, DR site, alternative office provider, hardware maintenance company).

The last item is often skipped. In a regional incident, the supplier you rely on for recovery is trying to reach many customers in the same region at the same time. The contract may say on-site response in four hours; if twenty of its customers have storage units under water on the same day, those four hours stay on paper. For the BIA data collection method, see the guide how to do a business impact analysis.

Two axes are enough for classification: business impact (which processes an outage stops, and how quickly) and substitutability (how long switching to an alternative source takes). Suppliers where high impact and low substitutability meet go through all the assurance steps below.

Single-source and concentration risk

Single-source dependency means an input can be bought from only one supplier. Concentration risk means suppliers that look different actually rely on the same infrastructure. The second is more insidious; on paper there appear to be two sources, but in the field there’s a single point of failure:

  • Lines from two different internet operators running along the same cable route, through the same duct into the building or via the same exchange,
  • Different software providers hosted in the same cloud region,
  • The primary and backup logistics companies using the same warehouse,
  • Two companies with maintenance contracts sourcing parts from the same distributor.

A situation you may come across with line diversity: circuits from two operators are cut together by the same excavation in front of the building. Without asking the operator in writing for path diversity information, “two lines” doesn’t count as redundancy. To see concentration, ask critical suppliers about their own critical subcontractors. ISO/TS 22318 (a guidance document supporting ISO 22301) gives direction on supply chain continuity; but the real work is overlaying the suppliers’ answers onto your own dependency map.

How do you question a supplier’s continuity capacity?

Asking a supplier “Do you have a business continuity plan?” produces no information beyond “yes”. The question list must ask for evidence, and the answers must be comparable with your targets. The table below is a sample question set.

Field Question Expected evidence
Management system What’s the scope of your continuity management, and is it certified? Scope statement, ISO 22301 certificate if any
Targets What are the RTO and RPO for the service you provide us? A written, service-specific target
Test When was the last recovery test, and what was the result? Test summary, open actions
Location Which facilities is the service provided from, and is there an alternative site? List of facilities, alternative site plan
Subcontractors Who are the critical subcontractors for the service? List of subcontractors
Notification When and through which channel will you notify us of an outage? Notification procedure, point of contact
Prioritization How do you prioritize customers in a regional crisis? Prioritization rule

When assessing the answers, look at three points. First, certificate scope: an ISO 22301 certificate may not cover the location or service that serves you; always read the certificate’s scope statement. Second, target alignment: if the supplier’s RTO is longer than your process’s RTO, your own additional measure has to close the gap. Third, test evidence. An untested plan is a statement of intent.

Continuity clauses in the contract

Questioning is done once and goes out of date over time; a contract clause makes the obligation permanent. The supplier relationship controls (5.19–5.22) and the cloud services control (5.23) in ISO/IEC 27001:2022 Annex A also expect requirements to be defined and monitored in supplier agreements. Add these clauses to critical supplier contracts:

  1. Continuity plan obligation: The supplier maintains a continuity plan for the contracted service and tests it at least once a year.
  2. Service-specific recovery targets: An RTO/RPO or equivalent delivery time commitment for the service.
  3. Outage notification: An incident affecting the service is notified within a set time, through a defined channel, with regular status updates.
  4. Sharing test results: Test reports are shared on request, and the supplier takes part in joint exercises.
  5. Subcontractor changes: A change of critical subcontractor or service location is notified in advance.
  6. Data return and exit: In what format and how quickly data will be returned when the contract ends or the supplier can no longer provide the service; transition support.
  7. Source code escrow: For custom software, an escrow arrangement giving access to the source code if the supplier ceases trading.
  8. Right to audit: Continuity arrangements can be verified on site or from documents.

Read the force majeure clause separately. A broadly defined force majeure clause releases the supplier from its obligations in exactly the events in which the continuity plan should kick in. If earthquakes, cyber attacks and power outages count as “force majeure” on this list, the continuity clause is worthless in practice. Agree the legal wording of the clauses together with your legal department.

Alternative supply strategies

A contract strengthens the supplier’s preparedness; it doesn’t guarantee the supplier won’t stop. For critical dependencies, you need to choose a strategy on your own side. The options:

Strategy When is it suitable? Limitation
Multiple sources (active) Inputs whose volume can be split between two suppliers, internet lines Cost, quality and management burden increase
Approved backup supplier (passive) Products and services where switching can be done within days It remains unclear whether an unused supplier is ready
Stock / buffer Storable inputs with a shelf life, spare parts Ties up capital, risk of obsolescence
Temporary in-house production Simple services, processes that can be replaced manually Doesn’t scale, requires competent staff
The supplier’s geographic redundancy Cloud and hosting services The same-provider risk remains
Accepting the risk Cases where management can tolerate the impact Must be written down and approved

In IT services, a passive backup supplier doesn’t work as fast as people assume. Data migration, rebuilding integrations, licensing, user access and DNS/MX changes can take weeks. For services such as SaaS, the realistic strategy is regular data export and defining manual working methods for the duration of the outage. Test the export too. Record that the exported file can be opened and the data read.

Joint exercises and monitoring with suppliers

The handover points between the supplier’s plan and yours are only validated when tested together. A joint exercise is usually held in tabletop format: the scenario starts with the supplier’s outage, the supplier describes its notification and recovery steps, and you show how your processes will run during that time. The three most common findings in these exercises are: the notification going to the email address of someone who has left the company, the supplier’s RTO turning out longer than you assumed, and it remaining unclear who makes decisions during the outage. For choosing the format, see the article types of business continuity exercise.

For monitoring, the critical supplier record should carry at least these fields: supported processes, the supplier’s RTO/RPO commitment, last assessment date, latest test evidence, contract end date, alternative strategy and open actions. Update the record at least once a year and when there’s a significant change at the supplier (a merger, a change of location, a major incident).

Checklist

  • The critical supplier list has been derived from BIA dependencies; recovery suppliers are included.
  • Critical subcontractors have been asked about and mapped for concentration risk; line routes have been confirmed in writing.
  • Supplier RTO/RPO commitments have been compared with process targets, and measures defined for the gaps.
  • Contracts have notification, testing, exit and data return clauses; the force majeure definition has been reviewed.
  • An alternative strategy has been chosen for single-source dependencies, or risk acceptance has been approved by management.
  • A joint exercise has been held with the most critical suppliers.

Assessing a supplier’s information security controls is a separate process, explained in the guide supplier information security risk assessment. To combine the two assessments in a single supplier lifecycle, you can design supplier and third-party risk management and BIA and business continuity plan work together.

Frequently asked questions

Is a supplier’s ISO 22301 certificate sufficient assurance?

Not on its own. Check whether the certificate covers the service and location provided to you, compare the recovery time the supplier commits to for this service with your own process targets, and ask for the latest test results.

Who should prepare the critical supplier list?

The list is prepared under the coordination of the business continuity manager, from the dependencies reported by process owners in the BIA. Purchasing provides supplier and contract information, and IT provides the service dependencies of technology suppliers.

What can be done if a SaaS provider has an outage?

Switching to another SaaS at short notice is usually unrealistic. Workable measures: regularly exporting data in a readable format, defining manual working methods to use during the outage and having notification, data return and exit clauses in the contract.

How often should a supplier continuity assessment be renewed?

For critical suppliers, an annual assessment is common practice. A merger, a change of location or subcontractor at the supplier, a major incident, or a change in your own process targets brings the assessment forward.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles