Web development and technology
The day after a cyberattack: how long does business recovery take?
How to prepare business recovery after a cyberattack: downtime costs, verified backups, RTO, RPO and annual recovery exercises.

In brief
Key ideas
- Recovery needs verified backups, infrastructure, access, dependencies and prepared owners.
- The hypothetical 48-hour and 6-hour example helps estimate financial impact using company-specific assumptions.
- RTO and RPO express objectives compared with observed test results.
- Sitelicon provides a paid audit, implementation and ongoing service with an annual exercise and intervention under contract.
Cybersecurity is essential to prevent incidents. When an attack compromises a company’s systems, its ability to recover can determine whether the business keeps operating.
Organisations have spent years investing in firewalls, antivirus, detection systems, multifactor authentication, audits and access controls. These measures are necessary. Even protected infrastructure remains exposed to unknown vulnerabilities, human error, ransomware and attacks on suppliers.
Alongside prevention, management needs to answer a practical question. How long would we need to resume operations if our systems were compromised tomorrow?
What happens when the attack has already occurred?
Imagine an online retailer discovering on a Monday morning that its store has been compromised. Files on the servers have changed, some services have stopped and there are signs of intrusion.
The team must contain the incident, establish its scope and restore activity safely. Is there a trustworthy backup? When was it made? Who can deploy fresh infrastructure? Where are the credentials? Who authorises a return to production? How will the vulnerability that enabled the intrusion be addressed?
Answering these questions for the first time during a crisis adds delay and uncertainty. Each hour of disruption can create further costs.
Cyber resilience prepares the business for recovery
Cyber resilience is the ability to anticipate, withstand, respond to and recover from incidents affecting digital systems. It complements cybersecurity by preparing the company to restore its essential functions.
Three elements make that preparation operational.
- Prepared technology, including backups, monitoring, restoration tools and alternative infrastructure.
- Defined procedures, identifying responsibilities, priorities and decision-making authority.
- Verified capability, demonstrated through tests that show how recovery actually works.
The recovery plan must account for relationships between systems. A working website may still be unable to take orders if its payment, identity or inventory integration remains unavailable.
The financial impact of waiting until an incident happens
An incident can stop sales, production, invoicing, logistics or customer support. Staff downtime, emergency suppliers, possible legal obligations and reputational consequences may add to the impact.
An initial estimate is downtime cost = hours of disruption × estimated financial impact per hour. Each company should adapt the calculation to its operations and avoid counting the same loss twice. Revenue lost, gross margin lost and additional costs should be distinguished when building the estimate.
A hypothetical comparison of 48 hours and 6 hours
Suppose a small business estimates its downtime impact at €1,500 per hour.
| Scenario | Downtime | Estimated impact |
|---|---|---|
| Extended recovery | 48 hours | €72,000 |
| Accelerated recovery | 6 hours | €9,000 |
| Potential difference | 42 hours | €63,000 |
This is a hypothetical example, rather than an industry statistic or a promised recovery time.
It illustrates the potential financial value of reducing disruption. Investment decisions should consider the cost of interrupted operations as well as backup and infrastructure costs.
Backups must be usable in an actual recovery
Restoring an application requires servers, networks, configurations, credentials, integrations and integrity checks. A backup can also be incomplete, damaged or compromised.
NIST recommends planning, maintaining and testing backups according to each organisation’s needs. Its guidance helps service providers assess whether backup files will be useful and available when needed. NIST guidance on backup protection and testing
A sound strategy considers protection against modification, isolation where required and regular restoration tests. The operational question is whether the backup can restore a safe working service.
Recovering a compromised online store
Consider a store running on AWS after an attacker compromises the application server. A prepared procedure could include the following steps.
- Detect the incident, activate the procedure and isolate affected systems.
- Preserve evidence and assess the extent of the intrusion and affected credentials.
- Deploy clean infrastructure from verified configurations.
- Restore databases and content from trusted backups.
- Rotate affected credentials, verify integrations and check security.
- Redirect traffic after the replacement environment has been validated.
- Keep the compromised environment isolated for analysis and subsequent retirement.
The order and execution must follow the incident and the people responsible for the response. The joint CISA guide includes containment, evidence preservation and recovery in its response checklist. Official #StopRansomware guide
Automation reduces manual work. Security validation remains part of the return to production. Rehearsing the procedure beforehand reveals missing permissions, dependencies and operational steps that could otherwise delay recovery.
An infected laptop can also interrupt operations
A Trojan on an employee’s laptop can stop their work and expose credentials. The procedure starts by isolating the device, reporting the incident and assessing its scope.
The team then protects credentials and preserves evidence, prepares a clean or replacement device, and restores verified applications and data. Device management, centrally managed applications and protected information can make rebuilding easier.
Where important files exist only on the infected device, the interruption may last longer. Recovery preparation therefore includes critical workstations and the information employees need to do their jobs.
Measuring real recovery capability
Recovery metrics allow the company to compare objectives with observed results.
- Mean time to detect, or MTTD, measures the average time required to identify incidents using available records.
- Activation time measures the interval between detection and the effective start of the procedure.
- Minimum recovery records the target and observed time to restore basic functions.
- Critical-service recovery measures the time needed to reactivate essential processes.
- Full recovery measures restoration of the complete planned service scope.
- Recovery point objective, or RPO, expresses the maximum acceptable age of restored data as a period of time.
Recovery time objectives, or RTOs, should be defined for individual services and compared with observed recovery times. A target does not automatically constitute a contractual guarantee. AWS recommends defining RTO and RPO according to business needs and testing the recovery strategy. AWS Well-Architected disaster recovery guidance
The annual recovery exercise
A written plan needs practical testing. The frequency should reflect system criticality and technological changes.
Imagine an exercise in which a business application is declared unavailable. The team must activate the procedure, locate a clean backup, deploy an alternative environment, restore data and check that users can resume work. Times, obstacles, decisions and unexpected dependencies are recorded throughout.
The outcome is a recovery capability report, showing observed metrics and improvement actions. An annual exercise can provide a starting point. Especially critical systems may need more frequent testing, and major infrastructure changes can justify another validation.
The exercise should have an agreed scope, authorised actions and clear acceptance criteria so the results can be interpreted in context.
Implementing and maintaining the recovery technology
Execution includes configuring backups, deploying automation, setting alerts, connecting security tools, preparing alternative infrastructure and checking restores. Those capabilities must remain usable as systems change.
Sitelicon’s cyber resilience and recovery service has three levels.
- A paid initial audit provides a documented diagnosis and prioritised roadmap.
- A technical design and implementation project delivers the agreed improvements.
- An ongoing service includes maintenance, supervision and an annual recovery exercise.
Direct Sitelicon intervention to execute recovery during a real attack is provided through the active ongoing service, within the contracted scope, hours and terms. Availability and any recovery commitment must be agreed expressly for the company’s architecture and dependencies.
Business responsibilities during recovery
Management determines which processes take priority and how much interruption the business can tolerate. Technical teams design and execute the recovery. Operational owners validate that restored services let people work again.
The response also needs clear decision-making authority. Someone must approve isolation, decide recovery priorities, coordinate communications and authorise the return to production. Recording those responsibilities before an incident supports faster, better-informed decisions.
Prepare before recovery becomes urgent
Identifying critical systems, implementing technology, assigning owners, testing restores and measuring times gives the company an operational capability it can maintain and improve.
How long can your business afford to stop? How would it resume operations today?
Explore the scope of our cyber resilience and cyberattack recovery service and describe your situation using the form on that page. The initial audit is a paid professional service.
Editorial responsibility
Who is responsible for this content?
Equipo Sitelicon
Content created and maintained by Sitelicon’s multidisciplinary team.
- Publication
- Latest review
- Traceability
- 3 referenced sources
Sources and updates
Verified and dated information.
Last update recorded on . The features and terms of digital platforms may change over time.
Related services
We can help you put it into practice.
For each article, we select the Sitelicon capabilities most directly related to the topic.
Cyber resilience and recovery
Paid auditing, implementation and ongoing service with an annual exercise.
View service 02Website maintenance
Maintenance, support and continuity for digital platforms.
View service 03AWS, cloud and systems
Architecture, automation and alternative recovery environments.
View service