After a Cyberattack: Measuring the Loss Beyond the Ransom

November 19, 2026 by

Getting the network back online after a cyberattack does not mean the business is back to normal. A company may regain access to its systems and still be unable to fill orders, ship products, or bill customers. For management, that gap can represent a substantial financial loss. For an insurance claim, it must be measured and documented.

The ransom demand usually gets the most attention. But the harder accounting challenge is often determining what the business lost while operations were interrupted — and how much of that loss is covered by insurance.

A ransom payment has a specific dollar amount. A business interruption loss requires

a more involved analysis: What would the company have earned without the attack? What did it earn during recovery? Which expenses continued, which were saved, and what additional costs were necessary to keep the business operating?

Answering those questions takes more than financial statements. It requires an understanding of how the company actually operates and a careful analysis of how the disruption affected its results.

A Restored Network Is Not a Recovered Business

One of the most challenging issues in a cyber claim is establishing when the interruption began and when it ended. The date an intruder entered the network may not be the date the company began losing business. Likewise, restoring a server does not necessarily restore the company’s ability to return to normal pre-loss operations and profitability.

Technical recovery does not necessarily mean operational recovery. In my experience, operational recovery can take longer.

Consider a hypothetical distributor whose order-processing system is restored after several days. Employees can begin entering orders, but inventory records still need reconciliation, warehouse systems remain unreliable, and previously received orders may need to be recreated. The system is online, but the business is not back to normal.

Measuring the interruption only by the system outage would miss those continuing limitations. Whether the resulting losses fall within the covered period, however, depends on the policy.

The analysis must distinguish three timelines: the technical recovery timeline, the business’s operational and revenue recovery timeline, and the period for which the policy provides coverage. Those timelines may differ because of policy definitions, waiting periods, restoration provisions, and any applicable extensions of coverage.

System logs help establish when systems become available. Production reports, shipping records, order volumes, and management’s explanations show what the company could accomplish. A well-supported claim connects the technical evidence to the operational and financial consequences.

Measuring What the Business Lost

The next task is estimating what the business would have earned without the attack — often called a “but-for” analysis — and comparing that estimate with actual performance.

This involves more than comparing sales before and after the event. A growing company may have expected revenue above historical levels. A seasonal business may have lost its busiest weeks. Conversely, declining demand or the loss of a major customer before the attack may make prior-year results an unreliable benchmark.

Historical sales, budgets, pre-loss forecasts, customer contracts, and order activity can help establish expected revenue. But the budget is not proof of a loss simply because it was prepared before the event. Its assumptions must be evaluated against the company’s performance and business conditions leading to the interruption.

Operational information provides an important check. Did the company have the employees, inventory, production capacity, and customer demand needed to achieve the projected sales? The calculation should reflect what the business could have accomplished, not simply what management hoped to achieve.

Lost sales must also be separated from delayed sales. An order that could not be shipped during the shutdown may have been fulfilled after recovery. A delayed invoice may create a cash-flow problem without representing permanent lost revenue. Some customers may wait for their orders; others may cancel or purchase elsewhere.

Finally, lost revenue is different from the recoverable business interruption loss. The calculation must follow the policy’s measurement provisions and evaluate expenses that did not continue.

A manufacturer producing fewer units may avoid certain material, packaging, and outbound freight costs. Rent, insurance, property taxes, and management salaries may continue. The question is whether the company avoided the expense — not whether its accounting system normally classifies that expense as variable.

Hourly employees may remain on payroll despite being unable to work. The treatment of those wages depends on the policy’s ordinary payroll provisions and any applicable limitations. Minimum purchase commitments may remain payable. Materials ordered before the attack may still have to be purchased.

A well-supported claim brings these financial and operational facts together, showing how lost sales, continuing expenses, actual savings, and subsequent sales recovery each affect the recoverable loss.

Documenting Recovery Costs

Financial documentation should begin while recovery is underway, not after operations return to normal.

Management’s immediate priority is understandably containment and restoration. But decisions made during the response may later become central to the claim. Why was the production line shut down? Why was a temporary co-packer or supplier needed? What could employees do manually, and what work could not be performed?

These questions are easier to answer at the time than months later.

I recommend establishing dedicated general ledger accounts or project codes early to track incident-related expenditures. A running record of operational restrictions, recovery milestones, and management decisions is equally important. An invoice shows what was spent; it rarely explains why the spending was necessary.

Recovery costs may include emergency IT support, data restoration, temporary software, alternative hosting, and overtime. Depending on the policy’s wording and defined terms, these costs may fall under incident response, data restoration, extra expense, or other coverage provisions. “Extra expense” is a policy term, not simply a label for every additional dollar spent.

A technology consultant’s invoice, for example, may include containing the intrusion, rebuilding systems, improving security, and performing routine maintenance. Those activities may receive different treatment under the policy.

Detailed invoices, statements of work, and time records help explain allocations between work included in the claim and work excluded from it. The same expenditure should not be counted twice across claim components.

For mitigation measures, such as temporary equipment or overtime for hourly workers to clear a backlog, records should explain the operational need and, where practicable, how the spending helped reduce the business interruption loss.

Making the Claim Understandable

A good submission explains what happened, how operations were affected, how recovery progressed, and how those facts produced the amounts claimed.

Financial statements, general ledger records, sales reports, and pre-loss forecasts provide the forensic accounting foundation. Production statistics, order cancellations, shipping records, and restoration reports connect the numbers to the event.

The calculations should be reconciled to those records. Expected revenue, actual results, expenses saved, and additional recovery costs should be identified separately. Significant assumptions should be explained — not buried in spreadsheet formulas.

More documentation is not necessarily better documentation. An enormous collection of invoices and spreadsheets without an explanation may create more questions than it answers. A concise narrative and clearly labeled supporting schedules make the claim easier to review.

This organization also helps address disagreements. If the insurer focuses on when a system became functional while management focuses on when sales recovered, the submission must identify the limitations that remained and explain their financial effect. Specific, understandable responses to the carrier’s questions are important. The broker’s claim advocate can help address coverage questions.

Continuing losses require particular care. Customer attrition, delayed projects, and reputational harm may outlast the outage. Any claimed continuing loss must be supported by evidence connecting it to the cyber event, distinguished from unrelated business conditions, and evaluated against the policy’s terms, time limitations, and any applicable extensions of coverage.

The objective is a defensible measurement of the financial loss, with a clear explanation of how the claim addresses the policy’s coverage requirements.

Preparing Before an Attack

Cyber preparedness is a business continuity issue. Management needs to ask: How will we keep operating if our primary systems are unavailable?

An incident response plan should identify how orders will be received, employees will communicate, and essential financial records will be accessed. It should also assign responsibility for documenting operational disruption and tracking exceptional expenditures.

Periodic tabletop exercises should assess those responsibilities alongside technical recovery. Can the company retrieve payroll records, sales data, customer contracts, and accounting reports without access to its primary network? Daily backups are useful only if they are protected, tested, and accessible when needed.

Insurance reviews should occur before a loss. Management should understand notice and consent requirements, deductibles, waiting periods, limits and sublimits, and the provisions governing a business interruption loss and recovery costs. The middle of a cyber response is not the time to learn what the policy covers and excludes.

A cyber claim is not measured simply by the ransom paid or the number of days the network was offline. It requires understanding what the business could not do, translating that disruption into a supportable financial loss, and evaluating the loss under the insurance policy.

In my experience, companies are better positioned to support their claims when financial documentation proceeds alongside operational recovery — not months later. A clear timeline, reasonable assumptions, and organized records make the loss easier to explain and the claim easier to evaluate.

Preparation matters as well. A well-developed and tested incident response plan can help demonstrate to underwriters that a company understands its cyber exposures and has practical measures in place to mitigate disruption.

The ransom may be the most visible number. It rarely tells the whole story.

Glasser is a managing director in BRG’s business insurance claims practice. He has more than 35 years of experience in financial management, insurance claims, and accounting and forensic fraud investigation at public and private companies.