Ransomware’s total business cost starts after the demand
The ransom gets a headline. The business bill keeps running.
A ransomware incident can mean unavailable systems, lost work, delayed transactions, interrupted customer service and a recovery effort that pulls technical staff away from ordinary operations. Add restoration, investigation, remediation and legal work, and the payment demanded by an attacker may be only one line in a much larger account.
A BleepingComputer article sponsored by Datto, published September 16, 2026, cites two figures that help put the distinction in view. IBM’s Cost of a Data Breach Report 2025 put the average total cost of a ransomware incident at $5.08 million when downtime, remediation, legal work and business disruption are included. Separately, the 2026 Verizon Data Breach Investigations Report gave a median ransom payment of $139,875.
Those figures describe different measures, drawn from different reports and years: an average overall incident cost and a median payment. They aren’t universal forecasts, nor are they directly comparable like-for-like estimates. Their useful lesson is narrower: focusing only on the ransom leaves much of the potential cost out of view.
Downtime turns an incident into a business loss
When critical systems are unavailable, the effects spread beyond the IT team. Employees may be unable to do their jobs; transactions can be delayed; customers may not receive service. Meanwhile, technical staff are occupied with containment and recovery instead of planned work.
The Datto State of BCDR Report 2025, as cited in the article, found that more than 60% of organizations believed they could recover from an incident in under a day, while only 35% did. The gap matters because expected recovery time and achieved recovery time aren’t the same thing. Confidence is not a restoration test.
For a business, each extra hour offline can compound disruption. The source describes recovery time as a financial metric as well as an IT one: restoring critical operations sooner can contain lost productivity, delayed business and service interruption. It doesn’t mean every hour has the same price for every company. The impact depends on which systems are down and what work depends on them.
Restoration and remediation add their own costs
Getting systems back is not necessarily a matter of copying data and switching everything on. The source notes that attackers may target backup infrastructure, leaving organizations with fewer recovery options. A backup copy is useful only if it is clean, accessible and recoverable.
If backups have been compromised, response may involve forensic investigation, incident-response specialists, rebuilding systems, acquiring software and committing substantial internal IT time. Those efforts sit alongside the work of restoring operations, not in place of it. Even where backups exist, an organization still needs to know whether it can restore the systems and data that matter, in what order, and within a workable period.
Remediation also competes with normal business priorities. Staff diverted to incident response cannot spend that time on other operational work. The article’s cited average-cost figure explicitly includes remediation and business disruption, a reminder that the recovery bill is not limited to external invoices.
Legal obligations run alongside technical recovery
An incident involving personal data can create deadlines while teams are still investigating and restoring systems. The cited article says the EU General Data Protection Regulation (GDPR) requires notification of a qualifying personal-data breach within 72 hours of becoming aware of it. It also notes that SEC rules require public companies to disclose material cybersecurity incidents within four business days, and that HIPAA imposes its own requirements.
These obligations depend on the circumstances and applicable rules; they shouldn’t be treated as one universal notification schedule. But they can add legal support, investigation, notification and reporting work to an already difficult response. Organizations need to manage that work in parallel with containment and recovery, not wait for the technical effort to finish.
Tested BCDR is more useful than confidence
Business continuity and disaster recovery (BCDR) is valuable when it works under real conditions. A backup proves a copy was made. A tested recovery strategy provides evidence that the copy can be used to return systems and operations to service.
That difference is practical. Testing can expose whether backups are available and recoverable, whether restoration steps are understood, and whether the organization’s expectations about recovery time match what its people and systems can actually achieve. The Datto report’s contrast between what organizations believed and what they achieved is a warning against treating a plan—or a reassuring estimate—as proof.
A useful exercise should test recovery of critical operations, not just the presence of backup files. Teams need to learn where restoration gets stuck and what decisions or resources are needed to move forward. The source does not promise that BCDR prevents an attack or eliminates its costs. Its case is more grounded: a mature, tested recovery capability can help reduce disruption by making a return to operations more predictable.
Make recovery readiness a business question
Leaders don’t need to predict one exact ransomware bill to take the issue seriously. They need to understand which services matter most, how long the business can tolerate their loss, and whether recovery has been demonstrated rather than assumed.
The source’s figures are not a budget template: the $5.08 million average incident cost and $139,875 median ransom payment come from different reports and measure different things. But together with the reported recovery-confidence gap, they illustrate why the payment alone is a poor proxy for the impact.
Ask when critical systems were last restored in a test, what failed, and whether the resulting recovery time fits the business’s needs. Then use what the exercise reveals to improve the plan. That’s less comforting than saying “we have backups.” It’s also a much better basis for deciding whether the organization can keep functioning when an attack disrupts normal operations.
ransomwares total business cost starts after the demand