Ransomware negotiation platform

Negotiation · decryptor validation · recovery

Standing by · 24/7

When the ransom notelands at 3 a.m.

Report an active breach

92%

Median reduction of initial demand

Clinics, practices and firms

1,480

Variants with a verified decryptor

Tested on customer file samples

< 4 min

Time to assigned negotiator

24/7/365 hotline SLA

38 hrs

Median time to first decryption test

From case opening

Capabilities

One team from first call to restored chart

Built for medical practices, dental and physio clinics, and small to mid-size accounting and tax firms. Downtime here is a patient safety and a filing-deadline problem, so every hour of negotiation is measured against operational risk.

Adversary negotiation

A lead negotiator engages the ransomware crew directly, controls the tempo, and works the demand down while your clinical operations continue.

Decryptor validation

We source or build a decryptor, then prove it against your own encrypted sample files before anything is trusted on production systems.

Recovery sequencing

Priority restoration of EHR, PACS, scheduling and billing, with a restore order agreed by clinical leadership rather than the ransom note.

HIPAA breach support

Documentation, patient-count scoping and notification timelines that stand up to OCR review, prepared alongside the negotiation.

Forensic attribution

Strain identification, initial access review and exfiltration assessment so you know whether data left the building and how much.

Legal & board liaison

Sanctions screening, payment policy guidance and executive briefings written for trustees, counsel and cyber insurers.

Engagement model

The first 72 hours, choreographed

Every case runs on the same clock. You always know which phase you are in, who owns the next action, and what decision is waiting on you.

  1. 0 – 60 min01

    Intake and containment advisory

    Case opened, responder assigned, ransom note and encrypted sample collected through the secure portal. Immediate guidance on segment isolation and clinical workarounds.

  2. 1 – 6 hrs02

    Strain identification and proof of life

    Variant confirmed, decryptor candidates queued, and the adversary's proof-of-decryption verified on a file you control, not theirs.

  3. 6 – 72 hrs03

    Negotiation and decryption trial

    A single negotiator owns the thread. Demand is contested line by line, deadline pressure is absorbed, and a decryption test runs against production-representative data.

  4. 72 hrs →04

    Recovery, notification, closeout

    Restore sequencing with clinical leads, HIPAA breach documentation, board brief, and a written after-action report for counsel and insurers.

Outcomes

Measured in restored systems, not press releases

Representative engagements across clinics, practices and professional firms. Organization names withheld under confidentiality; figures are the case record, not marketing claims.

Demand reduction
Median 92% off the opening figure
Time to decryption test
Median 38 hours from intake
Cases resolved without payment
31% of engagements

Dental group · 6 practices

Demand reduced 91%

BlackCat / ALPHV

Practice management and imaging servers encrypted across six sites. Negotiation ran four days against a 72-hour ultimatum; decryption verified on 40 sample files before restore.

Physiotherapy clinic · 3 locations

Restored without payment

LockBit 3.0

A working decryptor was located and validated within 19 hours. No payment made; booking, billing and patient records restored from verified output.

Accounting firm · 42 staff, tax season

Exfiltration contained

Royal / BlackSuit

Adversary claimed 4.1 TB of client tax data. Forensic scoping narrowed the exposure to 90,000 individuals and drove the notification and monitoring plan.

Recovery readiness

A recovery checklist for medical practices

Prevention reduces risk, it does not remove it. HIPAA's Security Rule already expects a contingency plan, a data backup plan, a disaster recovery plan and an emergency mode operation plan. Ransomware is the test of whether those plans actually work.

Before an attack01

The decisions that limit damage are made months earlier.

  • At least one backup copy is isolated, offline or immutable, so it cannot be encrypted with everything else.
  • Backup administrator credentials are kept separate from everyday accounts.
  • Coverage is confirmed for the EHR, imaging, billing and shared files, not just one server.
  • A restoration order is written down: clinical systems first, then scheduling and patient communication, billing and claims, shared files.
  • A printed contact list exists for the IT provider, cyber insurer, legal counsel and key vendors, because email may be gone.
  • Business associate agreements are reviewed, so you know who restores data and how fast they must respond.
First hours02

A calm, ordered response avoids mistakes that make recovery harder.

  • Isolate affected devices from the network as your IT team directs. Do not wipe or rebuild a machine before evidence is preserved.
  • Activate incident contacts and name one person to coordinate decisions.
  • Switch to downtime procedures: paper schedules, manual check-in, so patients are still seen.
  • Confirm backups are intact and unaffected before any restoration begins.
  • Start a log of what happened, when, and who made which decision.
  • Bring in your compliance lead early. Encrypted patient data is treated as a potential breach until a low probability of compromise is shown, and that decision is documented, not assumed.
After the restore03

Getting systems back online is not the end of recovery.

  • Confirm with IT that the environment is clean and credentials have been reset before you reopen.
  • Have clinical or front-office staff spot-check restored records, so validation is not purely technical.
  • Retain the incident timeline and decision log, backup and restore reports including failed jobs, the breach risk assessment, and notes on lessons learned.
  • Schedule restore tests and a tabletop exercise. They surface an outdated contact list or an unowned system while the stakes are low.

Recovery time objective (RTO)

How long you can operate without a system before patient care and revenue are seriously affected. A front desk can survive a day without billing. It cannot survive a day without the schedule.

Recovery point objective (RPO)

How much recent data you can afford to lose, the last hour or the last day. Both are business decisions first and technical decisions second.

Checklist adapted fromMedical ITG's ransomware recovery guide

Briefings

Read before you need it

Prepared by the response team · updated quarterly

Playbook

The first 24 hours after a healthcare ransomware detonation

Isolation order, clinical downtime procedures, what to preserve, and the four calls to make before you speak to the adversary.

12 min read

Compliance

HIPAA breach notification when the encryption is still live

How the 60-day clock is measured, what OCR expects in your risk assessment, and why the patient count is a negotiation input.

9 min read

Technical

Validating a decryptor before you touch production

The file-sample test we run for every variant, how partial decryptors fail, and what a verified result looks like in writing.

7 min read

Policy

Sanctions screening and the decision to pay

OFAC exposure, insurer involvement, board approval trails, and the documentation that protects the organization afterwards.

10 min read

Active incident?

Do not reply to the ransom note. Call us first.

Every minute the adversary controls the conversation costs you leverage. A negotiator answers the hotline around the clock, including holidays.

+1 800 555 0142Open a secure intake

Encrypted submission · responder assigned in under 4 minutes