Short answer: under CERT-In's Directions of 28 April 2022, every service provider, intermediary, data centre, body corporate and government organisation in India must report the cyber incidents listed in the Directions to CERT-In within six hours of noticing them or being told about them, and must keep the logs of all its ICT systems for a rolling 180 days, within Indian jurisdiction. Reports go to incident@cert-in.org.in, by phone to 1800-11-4949 or by fax to 1800-11-6969.
This guide summarises the Directions for planning. It is not legal advice. Read the Directions themselves and CERT-In's FAQs, and take advice on how they apply to you.
Who has to comply
The Directions name five groups: service providers, intermediaries, data centres, body corporates and government organisations. "Body corporate" is wide enough to cover most companies that run computer systems in India. Banks, NBFCs, brokers and insurers have their own regulators' reporting rules as well, and those clocks run separately: telling RBI or SEBI does not count as telling CERT-In.
What the six hours are counted from
The wording is "within 6 hours of noticing such incidents or being brought to notice about such incidents". The clock starts when your organisation becomes aware, including when a customer, vendor or researcher tells you. It does not wait for you to finish investigating. Report what you know, then add to it.
The 20 kinds of incident that must be reported
Annexure I of the Directions lists them:
- Targeted scanning or probing of critical networks or systems
- Compromise of critical systems or information
- Unauthorised access of IT systems or data
- Defacement of a website, or intrusion into a website with unauthorised changes such as malicious code or links
- Malicious code attacks: virus, worm, Trojan, bots, spyware, ransomware, cryptominers
- Attacks on servers such as database, mail and DNS, and on network devices such as routers
- Identity theft, spoofing and phishing attacks
- Denial of service and distributed denial of service attacks
- Attacks on critical infrastructure, SCADA and operational technology systems and wireless networks
- Attacks on applications such as e-governance and e-commerce
- Data breach
- Data leak
- Attacks on Internet of Things devices and their systems, networks, software and servers
- Attacks or incidents affecting digital payment systems
- Attacks through malicious mobile apps
- Fake mobile apps
- Unauthorised access to social media accounts
- Attacks or suspicious activity affecting cloud computing systems, servers, software or applications
- Attacks or suspicious activity affecting systems related to big data, blockchain, virtual assets, robotics, 3D and 4D printing, additive manufacturing and drones
- Attacks or suspicious activity affecting systems related to artificial intelligence and machine learning
The list is broad on purpose. A successful phishing sign-in, ransomware on one laptop and a defaced website are all on it.
The other duties in the same Directions
| Duty | What the Directions say |
|---|---|
| Logs | Enable logs of all ICT systems and keep them securely for a rolling 180 days, within Indian jurisdiction. Provide them to CERT-In with an incident report or when ordered |
| Clocks | Synchronise all ICT system clocks with the NTP servers of NIC or NPL, or with servers traceable to them |
| Point of contact | Designate a point of contact for CERT-In and send the details in the format in Annexure II; keep it up to date |
| Information on request | Take action or provide information when CERT-In orders it, in the format and time it specifies |
| Data centres, VPS, cloud and VPN providers | Keep validated subscriber records for five years or longer |
Why six hours is hard
Most of the six hours is usually lost before anyone decides there is an incident. An alert sits in a queue overnight; when it is opened, someone has to work out who the user is, what else happened on that machine, and whether the address has been seen before. Only then does the reporting start, and the report needs a timeline that nobody has written down.
Three things shorten it:
- Triage every alert when it is raised, at night and on holidays too, so "noticing" and "understanding" happen within minutes of each other.
- Keep the evidence with the case: the events, the user's history, the enrichment and the verdict in one place, with times in a single time zone.
- Draft the report from the case, not from memory, and have a named person approve and send it.
A readiness checklist
- A point of contact is registered with CERT-In, and a deputy knows the process
- Logging is switched on for servers, endpoints, identity, email, cloud and network devices
- Logs are kept for 180 days, in India, and someone has tested retrieving a specific day
- System clocks follow NIC or NPL time
- Alerts are reviewed around the clock, by people or by automated triage with people approving
- There is a one-page runbook: who decides it is reportable, who writes, who sends, to which address
- The reporting format from CERT-In's website is saved where the duty analyst can find it
- Sector reports (RBI, SEBI, IRDAI) and personal data breach duties are in the same runbook, with their own deadlines
- The runbook has been rehearsed once with a made-up incident
Where Cyvion fits
Cyvion, our security operations platform, investigates each alert as it arrives, keeps the evidence and timeline in the case, and drafts a CERT-In incident report from it for a person to check and send. It is in early access; the status table lists what is built and what is not. It does not replace your log archive or your decision about what is reportable.

