Colour theme
Book a consultation

Planning for a supplier cyber incident

Separate supplier outages from access compromise, map critical dependencies and test a fallback that can operate without the affected service.

Hands holding a tablet with a cyber attack warning over a digital network graphic

An incident at a supplier can stop deliveries, interrupt a cloud service or expose access to your systems. Those outcomes call for different responses. A supplier outage doesn’t by itself mean your network has been compromised.

Build a plan around the dependencies that would prevent important work from continuing.

Map the dependency and its access

For each critical supplier, record what it provides, what information it holds and whether it can connect to your systems. Include software maintenance, remote support, identity services and physical goods.

Identify the internal owner and a supplier contact you can reach independently of the affected platform.

The Cyber Centre’s supply-chain guidance for smaller organizations provides a starting point for assessing supplier relationships. Use the assessment to decide which suppliers need continuity work first. A good score doesn’t mean a supplier can’t be breached.

Distinguish loss of service from loss of trust

An unavailable ordering portal may require a manual process or alternate supplier. A compromised support connection may require access containment and investigation. A suspect software update needs technical assessment before it’s used again.

Ask what is known, which products or accounts are affected and which actions the supplier recommends. Verify urgent instructions through a known contact or official advisory channel.

Avoid broadly disabling updates or supplier connections without evaluating the consequences and the evidence.

Define a workable fallback

Choose the minimum service needed to continue urgent work. A secondary supplier may need you set up as a customer ahead of time, with compatible formats and an agreed account, before it can help.

Check whether the fallback shares the same underlying dependency. Two services that use the same unavailable identity provider may fail together.

For manual work, list the forms, records and sign-offs you’ll need. Keep copies where staff can reach them without the failed service.

Test data recovery and reconciliation

Confirm how important cloud information is exported or backed up, who can restore it and whether recovery depends on the supplier’s normal login.

Test retrieving a representative record during the continuity exercise. Check that the record is complete and its permissions are right. A green backup dashboard doesn’t show either.

Plan how changes made during an outage will be reconciled when the service returns. Duplicate orders and inconsistent records can create a second operational problem.

Assign incident decisions

Name who can pause supplier access, approve fallback spending, communicate with customers and decide when to go back to the service. If the incident touches personal information you’re responsible for, PIPEDA or your provincial privacy law may require you to report it and notify the people affected, even though the breach happened at the supplier.

Record the exercise results and the dependencies still unresolved. A supplier’s certifications won’t show whether your business can keep its essential work going during an outage. Use the exercise results for that.


Featured Image Credit