The four ways to treat a risk
Every identified risk resolves to one of four decisions. This is the strategic layer of cyber risk response, and it applies whether the risk is in your own systems or inherited from a vendor:
- Mitigate. Reduce likelihood or impact with controls: patching, segmentation, contractual security requirements, added monitoring.
- Transfer. Shift the financial consequence elsewhere, via cyber insurance or contractual indemnities. Note you can transfer cost but rarely accountability; regulators still look to you.
- Avoid. Stop the activity that creates the risk: decline a vendor, drop a data-sharing arrangement, or choose a different architecture.
- Accept. Formally acknowledge a residual risk that sits within appetite, document the decision, and monitor it. Acceptance is a legitimate choice; an undocumented one is just an unmanaged risk.
Response vs incident response
It's worth separating two things that share a word. Incident response is the acute reaction to a confirmed security incident, the containment and recovery work covered in our guide to cyber incident management. Cyber risk response is broader: it includes the upfront treatment decisions above, made on risks that haven't materialized yet, as well as the reaction when one does. Incident response is the acute end of cyber risk response; most of the discipline happens before anything goes wrong.
When the risk is a third party's
Here's what has changed the shape of the problem: more and more, the cyber risk you must respond to lives in a vendor, not in your own estate. A large share of breaches now reach organizations through a third party. When that happens, your usual response toolkit is constrained in three ways:
- Your visibility is second-hand. You learn what happened from the vendor, on their timeline, in their words.
- Your containment is contractual, not technical. You can't patch their systems. Your levers are the clauses in the contract and the access you can revoke on your side.
- The clock may still be yours. If your data or your service is affected, your regulatory reporting obligations can run even though the breach happened somewhere else.
All three are decided long before the incident, by preparation. If you already know exactly what each vendor holds of yours, and you've written notification and audit rights into the contract, you can respond in hours. If you don't, you spend the first day just working out whether you're even affected. That preparation is the whole point of sound third-party risk management, and specifically of classifying vendors by what they hold of yours rather than by an external score.
A third-party response playbook
- Confirm exposure. Establish precisely what of yours the vendor holds or can reach, which is a lookup, not an investigation, if you classified them properly upfront.
- Invoke the contract. Trigger breach-notification clauses, request the vendor's incident details, and hold them to their obligations.
- Assess your reporting duty. Determine whether DORA, NIS2, or GDPR deadlines now apply to you, and start those clocks.
- Contain your side. Rotate shared credentials, revoke or restrict the vendor's access, and watch for lateral movement into your environment.
- Communicate. Inform affected internal stakeholders, customers, and, where required, data subjects and regulators.
- Reassess. After the dust settles, re-tier the vendor and feed the event into your monitoring. A breached vendor is new evidence, not a closed case.
Signals that trigger reassessment
Response isn't only reactive. Between formal reviews, certain signals should pull a vendor back onto your desk: a disclosed breach or ransomware event, a change of ownership, financial distress, a lapsed certification, or new external exposure attached to their resolved identity. The discipline is to treat these as evidence feeding a decision (mitigate, transfer, avoid, or accept) rather than as an automatic alarm. Signals inform the verdict; your own exposure context determines it. That is cyber risk response working as intended: continuous, proportionate, and grounded in what a vendor actually holds of yours.