Skip to content

Lost money to a cyber fraud? Call 1930 now and file at cybercrime.gov.in. The first hour matters.

What to do, step by step →
Cyber Crime Help Desk An initiative from Kramate for Society
Business security 7 min read

Ransomware Response Plan: The Playbook for Indian SMEs

A ransomware response plan for Indian SMEs: the first hour, CERT-In reporting within six hours, whether to pay, restoring from backups, and the prevention list.

By Editorial team, Research and writing · Published
Colleagues around a meeting table reviewing documents and laptops together

In short

  • The first hour decides the damage: disconnect affected machines from the network, do not power them off, and stop the backup jobs before they overwrite clean copies.
  • Reporting to CERT-In within six hours of noticing the incident is a legal duty under the 28 April 2022 directions, regardless of company size.
  • Paying is legal in India but unwise: it funds the next attack, gives no guarantee of a working decryptor, and does not stop leaked data being sold.
  • Recovery is only as good as the backup that was offline when the attack ran; test restores monthly, before you need them.
  • If personal data was taken, the DPDP Act requires notifying the Data Protection Board and affected individuals; plan the message before the incident.

Who this is for: Owners, IT managers and whoever will be on the phone at 2 a.m. in Indian companies with 10 to 500 staff.

At 7:40 on a Monday morning the first call comes from the accounts office: Tally will not open, every file on the shared drive has a strange extension, and there is a text file on the desktop with a payment demand. What happens in the next hour decides whether this is a bad week or the end of the company. A ransomware response plan is the difference, and it fits on two pages.

This playbook is written for Indian SMEs without a security team. It gives the first hour, the legal reporting, the payment decision, the recovery sequence and the short prevention list. Keep a printed copy outside the computers; the plan on the file server is encrypted along with everything else.

The first hour: contain before you understand

Nobody knows what happened yet, and that is fine. The first hour is about stopping the spread and preserving evidence, not investigation.

First sixty minutes

  • Disconnect affected machines from the network: unplug the cable, turn off Wi-Fi. Do not power them off; memory holds evidence and some decryption keys
  • Isolate the network from the internet at the router or firewall if you cannot tell how far it has spread
  • Stop backup jobs immediately, so encrypted files do not overwrite the last clean backup; disconnect any backup drive that is still attached
  • Photograph the ransom note and the affected screens with a phone; note the time, the first machine affected and who noticed
  • Do not reinstall, do not run cleanup tools, do not reply to the attackers yet
  • Start the call list: owner, IT vendor, insurer, and an incident responder if you have one
  • Change passwords for the domain admin, email admin, bank portals and cloud consoles from a clean device, not from an affected machine

The instinct to "clean" the first infected laptop and reconnect it is the most common early mistake. Ransomware usually arrives days or weeks after the initial intrusion; the attacker already has credentials and often a foothold on several machines. Containment is of the whole network, not the one PC with the note.

Reporting: CERT-In in six hours, 1930 if money moved, the FIR

Under the directions CERT-In issued on 28 April 2022 under section 70B(6) of the IT Act, ransomware is one of the listed incident types that every service provider, intermediary, data centre, body corporate and government organisation must report within six hours of noticing it. There is no exemption for small companies. Report what you know at the time; the form allows updates. Email incident@cert-in.org.in using the incident reporting form from the CERT-In site, and keep the acknowledgement. Non-compliance is punishable under section 70B(7). The reporting guide goes through the form field by field.

The same directions require you to keep logs for 180 days, which is why preserving rather than wiping matters: those logs are what shows how the attacker got in. If any money has moved, for example through a compromised bank portal, call 1930 immediately and follow the standard sequence. File on cybercrime.gov.in and obtain an FIR under IT Act sections 43 and 66 and BNS section 308 (extortion); insurers and customers will ask for it. The ransomware and data breach page lists the provisions.

Six hours, 180 days. The CERT-In directions of 28 April 2022 require reporting of listed incidents within six hours of noticing them, retention of logs for 180 days within India, and clock synchronisation with NIC or NPL servers. They apply to body corporates of any size. (Source: CERT-In directions under section 70B(6), IT Act, 28 April 2022.)

The payment decision

Most modern ransomware is double extortion: the attackers encrypt your systems and have also copied data, threatening to publish or sell it. Paying therefore buys two uncertain promises, a decryptor that may not work and a deletion you cannot verify.

Paying a ransom is not itself an offence in India, but it carries risks beyond the money: some groups are sanctioned entities, which can create legal exposure depending on who is paid; payment marks you as a company that pays; and decryptors from criminal groups are slow and frequently corrupt large files. Our position is that payment should be the last option, considered only when there is no recoverable backup and the survival of the business is at stake, and never before isolation and reporting are complete. If you reach that point, involve your cyber insurer (most policies require consent before payment), counsel and an experienced negotiator. What policies cover is set out separately.

Recovery: clean rebuild, then restore

  1. Find out how they got in before reconnecting anything. The usual answers for Indian SMEs: remote desktop (RDP) exposed to the internet, a VPN without multi-factor authentication, a reused password from a leaked site, or an email attachment. If you cannot determine the entry point, assume all of them and fix all of them.
  2. Rebuild machines from scratch, from known-good installation media, not by cleaning the infected ones. Restoring data on top of a compromised operating system brings the attacker back.
  3. Restore data from the most recent backup that was offline or immutable when the attack ran. Verify a sample before restoring everything. Backups that were connected during the attack are suspect.
  4. Reset every credential: domain accounts, email, cloud consoles, bank portals, GST, vendor logins, Wi-Fi. Enable MFA everywhere it was missing.
  5. Reconnect in stages, core systems first, watching logs for the attacker returning.
  6. Handle the data breach. If personal data was accessed, the Digital Personal Data Protection Act, 2023 requires notifying the Data Protection Board and affected individuals. Prepare the notice with counsel and send it within the prescribed time; do not wait for negotiations to conclude. The data breach response template has the structure.

For most SMEs this is a week of nights, and it goes much faster with people who have done it before. Our incident response service handles containment, the CERT-In and police reporting, forensic preservation and the rebuild sequence alongside your IT vendor.

Prevention: the list that makes the playbook unnecessary

Before the Monday morning call

  • Backups: one copy offline or immutable, covering file servers, Tally or ERP, email and databases; a restore tested every month and recorded
  • No RDP or database port exposed to the internet; remote access only through a VPN with multi-factor authentication
  • MFA on email, cloud consoles and bank portals; separate admin accounts not used for daily work
  • Patching: automatic updates on, unsupported Windows versions retired
  • Endpoint protection on every machine, with alerts someone actually reads
  • Network segmentation: the shop-floor machines, CCTV and guest Wi-Fi are not on the same network as the file server
  • Logs kept for 180 days as the CERT-In directions require, and clocks synchronised
  • A tabletop exercise once a year: the owner, IT and finance walk through this playbook with a scenario, and find what is missing

A vulnerability assessment and penetration test finds the exposed RDP and the forgotten web server before an attacker does; VAPT explains the scope. The broader starter list for small companies is in our small business guide, and the numbers on how often this happens, in India and elsewhere, are in the ransomware statistics post.

Your ransomware response plan, this week

Print this page. Write the call list on it with real names and mobile numbers: owner, IT vendor, insurer, CERT-In's email, 1930, the bank's corporate fraud line. Check where the backup actually is and whether anyone has restored a file from it this year. Then book an hour with the owner, the IT person and the finance head to walk through the first-hour checklist aloud. That hour is the cheapest part of any ransomware response plan, and the one most companies skip.

Frequently asked questions

Should we pay the ransom?

Our advice is no, with eyes open. Payment is not prohibited by Indian law, but it funds organised crime, decryptors often fail or are slow, and in double-extortion cases the stolen data is sold anyway. If you have no backups and the business will not survive downtime, involve your insurer, counsel and an experienced responder before any decision. Never pay before isolating and reporting.

How do we report to CERT-In and what do they do?

Email incident@cert-in.org.in with the incident reporting form from cert-in.org.in, or use the toll-free number listed there. Report within six hours of noticing the incident, with what you know at that moment; you can update later. CERT-In records the incident, may issue guidance and coordinates where multiple victims share an attacker. It does not take over your recovery.

Can the police recover our data or catch the attackers?

Rarely, because the groups operate from abroad. File on cybercrime.gov.in and get an FIR anyway; it documents the incident for insurers, customers and the DPDP Board, and it establishes you as a victim of offences under IT Act sections 43 and 66 and extortion under the BNS. Expect investigation, not restoration.

The attackers say they have our customer data. What does the DPDP Act require?

If personal data was accessed or taken, you are required to notify the Data Protection Board and each affected individual of the breach, in the form and time the rules prescribe. Penalties for failing to protect data or to notify can be severe. Prepare the notification with counsel, but do not delay it to negotiate with the attackers.

How long does recovery take?

With tested offline backups and a plan, core systems can often be running within days and the rest within weeks. Without backups, it can be months or never. The time is spent rebuilding machines cleanly, restoring data, resetting every credential and confirming the attacker's access is gone before reconnecting. Reinstalling over an infected system and restoring on top of it is how companies get hit twice.

If you want help with this

  • Incident response and digital forensics · Ransomware, a compromised mailbox, a data leak or an insider walking out with the database. We contain first, investigate properly, handle the CERT-In and DPDP reporting, and leave you with evidence that holds up.
  • Vulnerability assessment and penetration testing (VAPT) · Manual testing of your web apps, mobile apps, APIs, networks and cloud by people who think like the attacker, with findings ranked by what would actually be exploited first and a report your engineers can act on.
  • Leadership and board cyber-risk briefing with ransomware tabletop · training · A three-hour briefing for founders, directors and CXOs that explains cyber risk in business terms and then runs a ransomware tabletop in which the leadership team makes the real decisions.
Talk to us
E

Written by

Editorial team

Research and writing