Data Breach Response Plan for Clinics: The First 72 Hours
What an Indian clinic should do after a data breach: contain it, preserve evidence, assess the harm, report to CERT-In and under DPDP, tell patients and prevent a repeat.
What the CERT-In directions mean for Indian clinics: which incidents to report within six hours, how to report, log retention, clock sync and a readiness checklist.
The CERT-In directions of 28 April 2022 require organisations, including body corporates, to report specified cyber incidents such as ransomware, data breaches, data leaks, unauthorised access and compromise of systems to CERT-In within six hours of noticing them. Reports can be sent through CERT-In's incident reporting form or by email, with more details added later. The directions also ask for logs to be kept for 180 days within India and system clocks to be synchronised with official time servers. Clinics should know whom to call, keep logs and practise the steps.
The Indian Computer Emergency Response Team (CERT-In) is the national agency for responding to cyber security incidents, under the Ministry of Electronics and Information Technology. Its directions under Section 70B of the Information Technology Act, issued on 28 April 2022, set out reporting duties for service providers, intermediaries, data centres, body corporates and government organisations.
This guide is general information, not legal advice. Whether and how the directions apply to a particular clinic depends on how it is organised; take advice if unsure.
The best-known part of the directions is that specified cyber incidents must be reported to CERT-In within six hours of noticing them, or of being told about them. Six hours is short. A clinic that discovers ransomware at 9 am has until 3 pm. You do not need complete information to report; send what you know and add details later.
The directions list types of incidents that must be reported. Those most relevant to clinics include:
On a narrow screen, scroll the table sideways to see every column.
| Incident type | Clinic example |
|---|---|
| Compromise of critical systems or information | Clinic server or software account taken over |
| Unauthorised access to IT systems or data | Former employee or outsider logging in |
| Ransomware and malicious code | Files encrypted, ransom note on screen |
| Data breach and data leak | Patient records exposed or stolen |
| Identity theft, spoofing and phishing attacks | Fake emails sent from the clinic's account |
| Defacement or intrusion into a website | Clinic website changed by attackers |
| Attacks on servers, databases and applications | Booking site attacked |
| Targeted scanning or probing of networks | Unusual repeated login attempts reported by your provider |
Read the full list on CERT-In's website, because it is longer than this table.
CERT-In provides an incident reporting form on its website and accepts reports by email to [email protected]. Include:
Keep a copy of your report and any reply. CERT-In may ask for more information or logs.
The directions also require organisations to keep logs of their information and communication technology systems for 180 days, within India, and provide them to CERT-In when asked. For a clinic, logs include router logs, login records from software and email, and security software alerts. Many cloud services keep logs for you; ask your vendors where and for how long. The directions also ask organisations to synchronise system clocks with the Network Time Protocol servers of the National Informatics Centre or the National Physical Laboratory, or with servers traceable to them, so the times in logs are accurate.
A data breach may trigger both CERT-In reporting and duties under the Digital Personal Data Protection Act and Rules to inform the Data Protection Board and affected people. These are separate obligations, with separate timelines. Your incident plan should cover both.
CERT-In also publishes advisories and vulnerability notes about software in common use, such as Windows, browsers and routers. Your IT provider should watch these and apply updates. Small clinics can follow CERT-In's general security guidance on passwords, phishing, backups and updates as a basic checklist.
A dental clinic's appointment email account started sending phishing messages to patients one evening. The manager noticed at 7 pm when patients called. Following the plan, she changed the password, signed out all sessions, turned on two-step login, and asked the IT provider to check forwarding rules. At 9 pm she emailed a report to CERT-In with the time noticed, what happened and actions taken, and kept a copy. The next morning the clinic messaged patients warning them to ignore the fake emails, and the IT provider sent CERT-In the login logs it asked for.
Bractis roles limit who can see patient data, and Bractis does not sell health data or use it for advertising. For questions about log retention, audit trails and incident support available today, ask the team what is supported.
The directions apply widely, including to body corporates. Many clinics will be covered; take advice on your situation.
Report as soon as you can and explain the delay. Non-compliance with the directions can lead to action under the IT Act.
They can help prepare the report, but the clinic remains responsible for making sure it is sent.
The directions require logs to be kept for 180 days within India.
Bractis is clinic management software built for Indian OPDs: appointments, patient records, prescriptions, billing and follow-up in one place. You can try it in your own clinic before you decide.
Written by the Bractis editorial team for doctors and clinic owners in India. Rules, fees and prices change: check the linked primary sources before acting, and ask your CA or lawyer about your own case.
Reporting of specified cyber incidents within six hours, log retention and clock synchronisation.
How to report incidents, including the incident reporting form and the [email protected] address.
Guidance on phishing, ransomware, patching, passwords and backups.
Legal recognition of electronic records and signatures, and offences relating to computers and data.
Duties of data fiduciaries, including consent, purpose limits, reasonable security safeguards and breach intimation.
What an Indian clinic should do after a data breach: contain it, preserve evidence, assess the harm, report to CERT-In and under DPDP, tell patients and prevent a repeat.
How ransomware reaches Indian clinics, what it does, how to reduce the risk and what to do if clinic computers are locked: backups, isolation, reporting and recovery.
A practical 15-point cybersecurity checklist for small Indian clinics: logins, updates, backups, email, Wi-Fi, devices, vendors, staff training and incident response.
What cyber insurance covers for Indian clinics: ransomware, data breaches, legal costs, notification and downtime, plus exclusions, security conditions and how to buy it.
How Indian clinics choose IT support: a staff member, a local freelancer or a managed vendor, what each should cover, costs, contracts, access control and response times.