Ransomware rarely bricks hardware, and that changes the claim
After a ransomware attack, many finance teams expect the cyber policy to buy new laptops and servers. Usually it won't. That's normally the right outcome: most ransomware encrypts data and leaves the hardware working. A wiped, encrypted laptop can be reimaged and returned to service. In claims terms, the device was disrupted, not destroyed.
Bricking coverage cyber insurance handles the narrower case: a device that can't be made to work again by reinstalling software. Firmware corruption, a damaged BIOS or UEFI, attacks on storage controllers, or a destructive payload that leaves a device unbootable can all brick hardware. Some wiper malware disguised as ransomware does this. So does an attack that pushes malicious firmware to network appliances or industrial controllers.
Whether your policy replaces equipment depends on three coverage parts working together: data restoration, bricking (sometimes called hardware replacement), and betterment. Buyers who know where each part starts and stops get paid faster. Buyers who don't often end up in disputes over a few hundred devices.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Three coverages that can apply to the same broken laptop
Each coverage part answers a different question about the same incident. The table shows how they commonly line up in policies from the London, European and North American markets, and in policies sold across Asia, the Middle East, Africa and Latin America that are modeled on them. Wording varies by insurer, so treat this as a map, not a promise.
| Coverage part | What triggers it | What it typically pays | Common limit structure |
|---|---|---|---|
| Data restoration (digital assets) | Data or software damaged, encrypted or destroyed by a covered event | Costs to restore, recover or recreate data and software from backups or other sources, including reimaging | Often the full policy limit, sometimes sublimited |
| Bricking / hardware replacement | Hardware made unusable by a covered event and can't be restored by software means | Cost to replace or repair the affected devices | Frequently sublimited, either a fixed amount or a share of the aggregate limit |
| Betterment | Replacement or restoration ends up better than what was lost | The cost of the upgrade, within limits | Usually a small sublimit, or a percentage of the covered loss |
The key point: data restoration costs coverage and bricking cover are sequential. Insurers expect you to try restoration first. Bricking cover applies only once restoration is shown to be impossible or uneconomic.
Why the reimage-or-replace decision drives the payout
Most bricking clauses include a cost-effectiveness test. The insurer pays for replacement when it costs less than restoring the device, or when restoration isn't possible. Many forms also require the insurer's written consent before you buy replacements. Skip that consent and a valid loss can become a disputed one.
Here's a hypothetical example. Say a 40-person company has 60 laptops and 6 servers encrypted. Using indicative 2026 market ranges, which vary by contract and region, reimaging an endpoint through an incident response firm or managed service provider might run $50 to $200 in labor. A business laptop costs roughly $900 to $2,000 to replace, and a mid-range server $8,000 to $40,000. Reimaging the fleet might cost $10,000 to $25,000; replacing everything could reach $100,000 to $350,000. The insurer will push for reimaging, and if the devices boot cleanly, it will be right.
The picture changes when:
- Forensics require evidence preservation. If investigators or law enforcement need the original drives, you may need working replacements. Check whether the policy treats that as a covered recovery cost or leaves it to you.
- Firmware compromise can't be ruled out. If the response firm can't confirm a device's firmware is clean, reimaging may not make it safe. Get that conclusion in writing. It's your best evidence for a bricking claim.
- Restoration time costs more than the hardware. If reimaging takes days but new laptops could ship within hours, the business interruption savings may justify replacement. Make that case to the adjuster in numbers, before you place the order.
Betterment: when the replacement is better than what you lost
Insurance indemnifies. It puts you back where you were, not somewhere better. That causes trouble after an attack, because like-for-like replacement is often impossible or unwise. A five-year-old server may no longer be sold. Your response firm will almost certainly recommend controls you didn't have before: endpoint detection and response, phishing-resistant MFA, immutable backups, network segmentation.
Betterment coverage cyber pays some or all of that gap. Without it, you may receive the depreciated or functionally equivalent value of the old kit and fund the rest yourself. With it, you still face limits. Some forms cap betterment at a set amount, some at a percentage of the related loss, and some only pay for upgrades the response firm specifically recommended to prevent a repeat attack.
Our view: for most mid-size companies running older infrastructure, betterment cover is worth requesting even with a modest sublimit. A typical recovery includes a lot of security work, and without betterment cover all of it is uninsured capital spending at a moment when cash is already tight.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Wording details to check before renewal
Bricking disputes usually turn on definitions, not on the facts of the attack. Ask your broker to answer each of these in writing:
- Firmware. Does the definition of computer system or digital assets include firmware, BIOS and UEFI? If not, a firmware attack may fall outside both data restoration and bricking.
- Operational technology. Are PLCs, SCADA components, medical devices, point-of-sale terminals and IoT equipment in scope? Manufacturers, utilities, logistics firms and hospitals should treat this as essential. Many forms cover office IT only.
- Ownership. Does the policy cover leased hardware, devices managed by service providers, and employee-owned devices used for work?
- Trigger. Does bricking apply only to malicious attacks, or also to a non-malicious failure, such as a bad patch that leaves devices unbootable?
- Sublimit and retention. How large is the bricking sublimit compared with your realistic worst case, and does a separate retention apply?
- Property interplay. Property policies often carry cyber exclusions, including cyber clauses commonly seen in London-placed business. Check that a destroyed device isn't excluded under both property and cyber.
- War and infrastructure exclusions. State-backed wiper attacks are exactly the events that brick hardware at scale. Read how these exclusions are worded.
Availability varies. Bricking cover is widely offered in the UK, continental Europe and North America. In parts of Asia, the Middle East, Africa and Latin America, it may be available only as an endorsement, or not at all, depending on local insurers and regulation.
Sizing the cover and a decision rule for this renewal
Insurers price bricking cover on device count, how much OT you run, backup quality, and firmware management. Many include it at little or no extra premium within a standard limit. Larger sublimits or OT extensions draw more underwriting scrutiny. Pricing varies widely by market, so get quotes rather than assuming.
To size what you need, work out a worst-case replacement figure. Count the devices that would be hard or slow to reimage: servers, firewalls, storage arrays, OT controllers and specialist workstations. Price them at current replacement cost, not book value, and add shipping and setup. Then compare that number with your bricking sublimit.
Decision rule: if your worst-case replacement figure is more than twice your bricking sublimit, or if OT and firmware aren't clearly covered, raise both issues with your broker at least 60 days before renewal. Also agree a pre-approval process with your insurer's response panel, so you aren't negotiating replacement consent mid-incident. Before accepting any wording changes, have a licensed broker or coverage counsel review the final policy.