Q-Cyber Magazine
Ransomware in hospitals: Restore, report, and protect the record
Hospitals should apply CISA's #StopRansomware discipline — tested offline backups, golden images, and a sequenced response — together with CERT-In's six-hour reporting duty and DPDP notice to affected patients.

A hospital cannot treat ransomware as a routine information-technology outage. Care continuity, the integrity of the clinical record, and statutory reporting all start at the same moment: when staff first notice that systems, or the data on them, are no longer theirs to use.
Why the generic guide still fits
The guide does not need hospital-specific incident counts to be useful, and this article will not invent any. Its logic is operational. Many ransomware variants try to find and encrypt or delete accessible backups. If the only copy of the electronic medical record sits on a connected volume, restore is already compromised. Offline, encrypted backups, tested in a disaster-recovery exercise, are therefore a clinical control. Golden images allow a workstation or server to be rebuilt from a known template rather than from a possibly contaminated estate.
The May and October 2023 revisions also include zero trust architecture and cloud-backup design. In a hospital, that should be read as a warning against implicit trust on the clinical network: a workstation used for records, imaging or pharmacy should not be reachable merely because it is "inside." Identity, device posture and segmentation belong in the same conversation as backup.
Exhibit 1
A hospital ransomware path that meets published duties
| Time or control | Published expectation |
|---|---|
| Before an incident | Offline, encrypted, tested backups of critical data; golden images; closure of common initial access paths (CISA #StopRansomware Guide) |
| At first awareness | Six-hour clock to report a specified incident to CERT-In; designate and use the notified point of contact |
| Immediate response | Isolate affected systems; preserve logs and images before rebuild; then contain, eradicate and restore from trusted backups (CISA checklist) |
| If personal data is involved | Prompt, plain-language notice to affected individuals under the DPDP Rules, explaining nature, possible consequences, steps taken and a contact point |
| Standing evidence | ICT logs retained securely for a rolling 180 days within Indian jurisdiction |
Source: CISA #StopRansomware Guide; CERT-In Directions, 28 April 2022; Press Information Bureau, DPDP Rules notification, 14 November 2025. This is a control sequence, not an incident statistic.
Response without destroying the record
The guide's checklist asks organisations to move through the first steps in sequence. Isolation and evidence preservation come before a hurried wipe. That matters in healthcare for two reasons. First, a forensic gap will make the CERT-In report, and any later root-cause work, weaker. Second, a rushed rebuild can leave the clinical record incomplete or uncertain, which is a patient-safety failure as well as an information-security one.
Paper downtime procedures, pre-agreed decision rights, and a tested method for reconciling the record after restore are therefore part of the same programme. They are not extras to be written after the first incident.
Implications
- Test restore of the clinical record, not only of file servers.
- Rehearse the six-hour CERT-In report with clinical, IT and legal staff on the same clock.
- Preserve evidence before rebuild, in line with the CISA checklist.
- Prepare DPDP notice templates for patients and staff whose personal data may be involved.
What this means for healthcare
A hospital board does not need a new threat narrative. It needs proof that the record can be restored, that logs will exist, and that the first six hours have been rehearsed. Those three proofs are a sufficient agenda for the next quarter.


