Q-Cyber Magazine

Enterprise · 21 July 2026 · 3 min read

Enterprise ransomware preparedness: Controls that still hold

CISA's #StopRansomware Guide still offers a practical two-part discipline — prevent common access paths, and rehearse response — while Indian enterprises must also meet CERT-In's six-hour reporting rule.

Abstract graphic of layered document sheets in Knowlcom blue

Ransomware remains a business-continuity problem first. The useful response is not a new vocabulary, but a short list of controls that still determine whether an enterprise can refuse payment and resume work.

Prevention is a path problem

The guide's design is more useful than a generic "best practices" list. It groups prevention around the ways incidents commonly begin, including compromised credentials, social engineering and internet-facing vulnerabilities. That is an operational prompt: identify the paths that actually reach the enterprise, and close them in order.

Two recovery controls are stated without ornament. Backups of critical data should be offline and encrypted, and their availability and integrity should be tested in a disaster-recovery scenario, because many ransomware variants try to find and destroy accessible backups. Golden images of critical systems should be maintained and updated, so that a host can be rebuilt from a known template rather than from a compromised estate.

The May and October 2023 revisions also folded in zero trust architecture and cloud-backup considerations, and expanded the response checklist with detection and analysis advice. None of this requires a claim about this year's incident volume. It requires a claim about readiness: can the enterprise restore, and can it do so without trusting a live, possibly contaminated, backup path?

Exhibit 1

A minimum enterprise ransomware control set, drawn from published guidance

ControlPublished sourceWhat 'done' looks like
Offline, encrypted, tested backupsCISA #StopRansomware Guide, preparing for incidents (CPG 2.R)Restore has been rehearsed; backups are not reachable from the production estate
Golden images of critical systemsSame guide (CPG 2.O)A known-good image can rebuild a server or workstation without relying on a compromised host
Close common initial access pathsGuide, Part 1, organised by access vectorCredentials, phishing paths and internet-facing vulnerabilities have named owners
Zero trust architectureGuide updates, May and October 2023Access to data and administration is not implied by network location
Six-hour incident report and 180-day logsCERT-In directions, 28 April 2022A complete initial report can be filed from first awareness; logs exist in India

Source: CISA #StopRansomware Guide resource page and 23 May 2023 announcement; CERT-In Directions No. 20(3)/2022-CERT-In, 28 April 2022. This is a control list, not an incident statistic.

Response is a sequenced checklist

The second part of the guide is a checklist, not a narrative. Isolate affected systems, preserve evidence, contain and eradicate, recover from trusted backups, and conduct a post-incident review. The authoring agencies advise moving through the first steps in sequence. Organisations that begin rebuilding before they have captured logs and images often destroy the only record that would explain the path in, or support a CERT-In follow-up.

For Indian enterprises, that sequence has a statutory clock attached. The six-hour duty is timed from noticing the incident, not from the end of analysis. A ransomware event that also exposes personal data will later engage DPDP breach-notification duties as those rules apply. The immediate task is still the same: contain, preserve, report, and restore from a backup that was never in the adversary's reach.

Implications

  1. Test restore, not only backup jobs. An untested backup is a hope.
  2. Map and close initial access paths with named owners, starting with credentials and internet-facing systems.
  3. Rehearse the first six hours, including the CERT-In report, on a holiday timetable.
  4. Keep forensic artefacts before any wipe-and-rebuild.

What this means for enterprise

Boards do not need a new threat briefing as much as they need evidence that restore works, that logs will exist, and that the six-hour report can be sent. Those three tests are sufficient to start a serious review this quarter.

Sources

  1. CISA #StopRansomware Guide
  2. CISA, FBI, NSA, MS-ISAC publish updated #StopRansomware Guide
  3. CERT-In Directions, 28 April 2022