Pay, Restore, or Rebuild: The Postage Bill That Beats the Ransom

Archi4 min read

breachesransomwarebackupscompliance

Contents
  1. Three Options, One Surprising Line Item
  2. Pay and decrypt
  3. Restore from backups
  4. Rebuild the estate
  5. The Table, Side by Side
  6. The Number That Decides It
  7. Where the clock bites
  8. What to settle before the incident

Three Options, One Surprising Line Item#

The cheapest number in a breach spreadsheet is usually the ransom demand. The most expensive is often the postage.

A crew asks for $60,000. Mailing notice letters to 120,000 people costs about $87,600 in first class postage before the print house adds its bill, and that bill runs $42,000 to $72,000 for printing, envelopes and address verification. The extortion payment sits below the mailroom line.

The model here is a 400 person company with 120,000 customer records, 80 TB of file storage and a $60,000 demand. Treat every figure as a planning estimate, not a quote.

Pay and decrypt#

Cash out: $60,000 in bitcoin, priced at the moment of transfer, plus $25,000 to $60,000 for a negotiator and incident response help if the insurer wants a professional in the room. Decryption on the crew's tooling runs near 500 GB an hour, so 80 TB takes about seven days, and some files come back corrupted.

Downtime lands at six to nine days. At $12,000 a day in lost gross margin, that is another $72,000 to $108,000. The payment also does not buy silence. Most crews copy data before they encrypt, so a notification obligation may survive regardless.

Then the renewal arrives. Insurers commonly raise premiums or add exclusions after a paid event, which is a cost that shows up twelve months later in a different budget.

Restore from backups#

This option looks free and is not. Expect ten to fourteen days before normal service, including a clean room check of every backup set and a rebuild of the directory service, because the attacker usually owns that too.

Notice costs dominate. Postage at $87,600, print and mailing at $42,000 to $72,000, a call center handling around 1,200 calls at $5 to $8 each. Credit monitoring is the sleeper. If 9,000 of those records carry Social Security numbers, a year of coverage at $12 a month costs $144 per person, or about $1.3 million. That is why firms map eligibility by state statute and offer monitoring to a subset rather than the whole file.

A realistic total: $300,000 to $450,000, with the largest chunk arriving in weeks three through eight.

Rebuild the estate#

Pull the environment down and stand up a new one. New hardware at $150,000 to $220,000, fresh credentials and keys for every system, 400 laptops reimaged at roughly two hours each, which is 800 hours of staff time nobody planned for.

Call it five to six weeks and $500,000 or more. It is the priciest column in year one and the one that removes whatever the intruders left behind, including the accounts and scheduled tasks that a restore quietly brings back.

The Table, Side by Side#

| Option | Year one cash | Time to normal | What returns | |, |, |, |, | | Pay | $160,000 to $230,000 | 6 to 9 days | Possibly the same crew | | Restore | $300,000 to $450,000 | 10 to 14 days | Anything hidden in the backup | | Rebuild | $500,000 and up | 5 to 6 weeks | A clean estate |

The Number That Decides It#

The line that flips the decision is not the total. It is the count of repeat intrusions. In incident reporting, organizations that pay are frequently hit again inside a year, because the payment marks them as a customer with a budget and a working bitcoin desk.

Run the model with a second event in month fourteen and the paid option loses. Two ransom payments, two rounds of downtime, two sets of forensic fees and an insurance market that has stopped returning calls. The restore option carries a similar risk if the backups were reachable from the compromised network, which is the configuration error behind a large share of repeat cases.

Rebuild carries the highest invoice and the lowest recurrence. That is the trade, stated plainly.

Where the clock bites#

Several state statutes and most enterprise contracts start a 30 day or 72 hour clock from confirmation, not from the end of the investigation. A slow forensic review eats the window. Companies that finish the notification mailing in week five are already late.

Sanctions screening matters too. Paying a crew on a restricted list is its own legal problem, and the check takes days, which is time the decryptor is not running.

What to settle before the incident#

Decide the trigger for each option now, while nobody is on the phone. Who signs off on a payment, at what dollar ceiling, and who can authorize the rebuild instead. Whether backups are offline and tested, and when they were last restored end to end rather than merely copied.

Draft the notice template and pre-negotiate the print contract. The postage figure is knowable in advance, which means it belongs in the plan, not in the surprise column at 2 a.m.

One more line worth pricing early: the call center. Operators who can answer a nervous customer in the first hour cost far less than a queue that grows for three weeks, and the transcript of that queue tends to appear in the regulator's file.

More articles