Key Takeaways
- Gartner reports that 45% of organizations experienced a third-party-related business interruption in the prior two years, highlighting the importance of external dependencies in recovery planning.
- Cyber recovery requires establishing what can safely return to operation, including the systems, data, identities, and third-party dependencies needed to restore critical business services.
- Recovery time objectives (RTOs) remain important, but they may not fully account for the additional validation and security requirements introduced by a cyber event.
- Leaders need a clear understanding of critical services, their dependencies, and recovery decision authority before an incident forces difficult tradeoffs.
Cyber recovery becomes more difficult when a critical service depends on a third party. An identity provider, cloud platform, payment processor, managed service provider, or data supplier may be essential to recovery, yet its role may not be fully understood until the organization is already responding to an incident.
Gartner’s research on third-party business interruptions highlights the operational importance of external dependencies, even though those interruptions were not necessarily all cyber-related.
Restoring an internal application does not necessarily restore the business service it supports. A required vendor may still be unavailable, its access may be compromised, or the data and integrations it provides may still need validation before operations can safely resume.
That’s why cyber recovery decisions need to account for more than the systems that are offline or how quickly they can be restored. Leaders need to understand which critical services are affected, which dependencies must be available before they can resume, what conditions must be met to restore operations safely, and who has authority to make decisions when business priorities and security requirements compete.
Containment Does Not Mean Systems Are Ready to Resume
When security teams contain an active threat, the immediate danger may be reduced. But critical systems can remain offline, and the investigation is often still underway. Teams may need to isolate affected environments, review the scope of the incident, and determine whether systems or data have been compromised. Recovery planning and preparation can proceed in parallel, but restoring affected systems requires validation that doing so will not reintroduce the threat.
In my work with organizations on cyber resilience, I’ve seen this disconnect firsthand. Consider what happens when cybersecurity teams need to isolate an order-management system to prevent a potential threat from spreading.
IT may understand which applications and integrations are affected, but the broader consequences may not be immediately apparent.
Customer service could lose visibility into orders, warehouses might be unable to process shipments, and finance could experience billing delays. Business teams understand these operational impacts, but may not anticipate how cybersecurity actions could trigger them. This is why business continuity, cybersecurity, IT, and business leaders need to map dependencies and discuss potential disruption scenarios before an incident occurs.
At the same time, the business still has customers to serve, obligations to meet, and decisions to make. A contained incident can quickly become a recovery coordination problem: which services can operate through workarounds, which systems must be restored first, and what conditions must be met before teams bring them back online?
Those decisions require coordination between cybersecurity, IT recovery, and business leaders to balance operational priorities with the requirements for safe restoration.
Why Traditional Disaster Recovery Assumptions Change
Traditional IT disaster recovery planning often addresses failures with a known cause and a defined restoration path. In an infrastructure outage, teams may be able to follow established recovery procedures and restore applications using environments and controls that remain trustworthy.
Cyber events introduce a different set of assumptions. Teams may not yet know whether a backup is trustworthy, whether credentials remain secure, whether an attacker has retained access, or whether an application can safely reconnect to other systems and dependencies.
Restoring too quickly without these checks can reintroduce the threat or create additional exposure.
The question is no longer only how fast an application can be restored. It is whether that application, its data, and the environment it depends on can return safely and support the business service that needs it.
The Conditions That Shape Cyber Recovery
Those changing assumptions introduce a set of conditions that rarely fit neatly into a standard recovery plan. These include:
- Forensic scoping, containment, and threat eradication to understand what was affected, prevent the threat from spreading, and address remaining attacker access.
- Backup and recovery-point validation to confirm that restoration assets and recovered data are trustworthy.
- Clean or isolated recovery environments, where needed, to rebuild and validate systems before reconnecting them to production.
- Identity, credential, and access restoration to reestablish trusted access so people and systems can operate securely.
- Critical dependency availability and validation, including the applications, infrastructure, suppliers, and teams needed to resume a service.
These are not solely technical questions. Each one affects the order and timing of recovery decisions across the business.
NIST’s Cybersecurity Framework 2.0 reinforces the importance of these recovery safeguards, including verifying the integrity of backups before restoration and validating restored assets before confirming normal operations.
Why RTOs Do Not Tell the Whole Story
Recovery time objectives (RTOs) remain useful for setting expectations and planning investments. But an RTO alone does not capture every condition that can delay a cyber recovery. A system may be technically recoverable within its target window while the backup, credentials, recovery environment, or connected dependencies are still being validated.
Restoring an application also does not necessarily restore the business service that depends on it. A critical service may require a combination of applications, third parties, identity services, data feeds, and trained staff. If any of those pieces are unavailable or untrusted, the service may still be unable to operate.
Recovery sequencing should account for business criticality, impact tolerance, safety, and technical feasibility. That gives leaders a more realistic basis for deciding what to restore, what to defer, and where to use workarounds while recovery continues. Third-party dependencies deserve the same attention.
Third-Party Criticality Shapes Recovery Options
A vendor assessment alone does not show what the business can recover during a cyber event. Teams need to know which third parties support critical services, what data or access they provide, and whether the business has a viable workaround if the vendor is unavailable or compromised.
Gartner found that only 6% of organizations are effective across resource efficiency, risk management and resilience, and influence on business decisions in third-party cyber risk management.
RWE offers a useful model: the business identifies vendor criticality, cybersecurity advises on the risk, and authorized business leaders make risk-treatment decisions within established governance and risk appetite.
That division of responsibility gives recovery teams clearer information before an incident. It helps them understand which third parties require specific contingency plans, escalation paths, and testing as part of cyber recovery.
Closing the Recovery Decision Gap
One of the most difficult parts of cyber recovery is connecting the conditions of the incident to the priorities of the business. Leaders need to see which critical services are affected, the dependencies supporting them, the constraints on recovery, and the tradeoffs attached to each option.
That requires shared information across cybersecurity, IT disaster recovery, business continuity, technology, and business teams. It also requires clear authority for decisions about recovery priorities and escalation.
Defining these handoffs in advance helps teams make recovery decisions with greater confidence, even as an incident evolves. That includes understanding critical third-party dependencies and who owns related business risk decisions.
Prepare for the Decisions After Containment
In Operating Through Cyber Disruption, we explore the recovery decision gap and the five capabilities organizations need to coordinate recovery after a cyber event. Download the whitepaper to learn how to define recovery priorities, establish cyber-specific conditions for safe recovery, connect services to critical dependencies, clarify decision authority, and test the handoffs between containment and recovery.
Sources:
Gartner. Take a Life Cycle Approach to Managing Third-Party Cyber Risk. Christopher Mixter, Oscar Isaka, and Rahul Balakrishnan. October 30, 2024.