Cyber Awareness for the Boardroom · Guide 3

Supplier assessed. What happens if it fails?

A practical guide to dependency, disruption and decision-making.

A supplier assessment shows what was reviewed, not what happens to your service when the supplier fails. For bank boards and senior executives, the next question is whether management has a practical option before disruption causes customer harm.

5-page PDF Prepared by Professor Buck Rogers
Get the guide
Front cover of the Poro Advisory guide: Supplier assessed. What happens if it fails?

What's inside

  • Services and dependencies

    Start with the service outcome, follow the dependencies behind the supplier and identify shared points of failure.

  • Evidence of a response

    Bring supplier assessments together with evidence of usable workarounds, recovery options and clear decision authority.

  • Three board questions

    What would degrade, how quickly, and what could management do before the agreed tolerance is breached?

  • Ten minutes at the next meeting

    A payment-screening supplier incident, a timed discussion and a practical follow-up record for your board.

The key insight

A contractual exit right is not the same as an alternative that can be used today.

Get your free copy

Tell us where to send it and we'll email you the download link straight away.

We'll only use your details to send the guide and occasional Poro Advisory insights. No sharing, ever.

From the guide

Supplier risk and operational resilience: beyond the assessment

A satisfactory supplier rating can coexist with a service that has little room for disruption. For a bank board, the useful starting point is the customer outcome: what stops, how quickly it matters and which options remain available.

The questions a board should ask

Which important service depends on this supplier, and how quickly would failure cause material degradation? Ask management to connect the assessment to the service's impact tolerance, the intervention available and the person authorised to act. Then challenge the dependencies behind the contracted provider.

The evidence to request

  • A service and dependency map showing material concentration and unverified assumptions.
  • Evidence that a fallback is usable, including activation time, capacity and reconciliation needs.
  • Clear supplier warning signals, escalation routes and authority to start a workaround.

A practical scenario

Illustrative scenario from the guide

A payment-screening supplier reports a cyber incident while its service remains available. Peak volumes are approaching, and an alternative route takes about 90 minutes to activate. Switching has costs; waiting may close the option. What evidence would trigger a decision?

Buck's interpretation

The guide's central distinction is between assurance about a supplier and assurance about the service. A sound response neither disconnects solely because an alert exists nor waits passively for certainty. It establishes exposure, prepares options and records the decision trigger, owner and trade-offs while action is still possible.

The full guide includes all three board questions, the structured ten-minute discussion, a response checklist and a practical follow-up record.

Download the full guide