CERT-In: Its Role, Incident Reporting and the Six-Hour Rule
What CERT-In does, who must report cyber incidents within six hours under the April 2022 directions, what to send, the 180-day log rule, and its limits.

In short
- CERT-In is the national incident-response agency under section 70B of the IT Act, part of MeitY; it issues advisories, coordinates response and empanels auditors.
- Its directions of 28 April 2022 require service providers, intermediaries, data centres, corporate bodies and government organisations to report listed incidents within six hours of noticing them.
- The same directions require ICT system logs to be kept for 180 days within India and clocks to be synced to NIC or NPL time servers.
- Individuals with financial fraud go to 1930 and cybercrime.gov.in, not CERT-In; phishing sites can be reported to CERT-In by anyone.
- Reporting to CERT-In is not the same as reporting to the police or to the Data Protection Board; a breach may require all three.
Who this is for: Owners, IT staff and compliance officers of Indian organisations of any size, and individuals who want to know which agency handles what.
Two Indian agencies get confused with each other more than any others. I4C runs 1930 and the portal for citizens who lose money. CERT-In is the agency an organisation must tell, within six hours, when its systems are breached. They sit under different ministries, use different forms and serve different people. This explainer is about the second one: what it is, what the 2022 directions require, and how a company that has just been hit should use it.
What CERT-In is
The Indian Computer Emergency Response Team was set up in 2004 and is the national agency for cyber security incident response under section 70B of the Information Technology Act, 2000. It sits within the Ministry of Electronics and Information Technology. Its statutory functions include collecting and analysing information on cyber incidents, issuing forecasts and alerts, coordinating response, and issuing guidelines and advisories on security practices. Section 70B(6) lets it issue directions to service providers, intermediaries, data centres and corporate bodies, and 70B(7) makes non-compliance punishable.
In daily practice, four outputs matter to an Indian organisation. Advisories and vulnerability notes on the CERT-In website, which tell you what to patch this week. Incident coordination when something goes wrong. The empanelment of security auditors, whose reports regulators such as RBI and SEBI accept. And the April 2022 directions, which turned reporting from good practice into an obligation.
The directions of 28 April 2022
Issued under section 70B(6) and in force from late June 2022, the directions apply to service providers, intermediaries, data centres, body corporates and government organisations. There is no size threshold. The main obligations:
| Obligation | What it means in practice |
|---|---|
| Report listed incidents within six hours | From noticing the incident or being told of it; a preliminary report is enough, with details to follow |
| Keep ICT system logs for 180 days within India | Firewall, server, application and authentication logs, retained and producible on request |
| Sync clocks to NIC or NPL servers | So timestamps across organisations line up during an investigation |
| Designate a point of contact | A named person whose details are sent to CERT-In for incident communication |
| Extra duties for specific sectors | Data centres, VPS, cloud and VPN providers must keep customer registration details for five years; virtual asset providers must keep KYC and transaction records for five years |
The six-hour clock. The directions require reporting "within 6 hours of noticing such incidents or being brought to notice about such incidents". The types of incident are listed in an annexure that includes ransomware, data breaches, unauthorised access, defacement, malware and attacks on critical systems. (Source: CERT-In directions under section 70B(6), 28 April 2022.)
What a CERT-In incident report contains
The reporting form, available on the site, is short by design; CERT-In would rather have a thin report at hour five than a thorough one at day three. Prepare:
The six-hour report
- Organisation name, sector, and the designated point of contact with phone and email.
- Type of incident from the annexure list, and a one-paragraph description.
- Affected systems: hostnames, IP addresses, applications, number of users or records, as far as known.
- Date and time of occurrence if known, and of detection.
- Indicators: attacker IPs, malicious domains, file names and hashes, ransom note text.
- Actions taken so far: isolation, password resets, backups invoked.
- Whether personal data is involved, and whether other regulators or the police have been informed.
Send by the email or form published on the site, and keep the acknowledgement. Update as facts emerge. CERT-In may ask for logs, which is where the 180-day retention rule bites: an organisation that cannot produce logs cannot show what happened, and that weakens its position with every other regulator too.
What CERT-In does with a report
It is not a police force and does not investigate crime. What it does is coordinate: share indicators with other potential victims, work with hosting providers and registrars to take down phishing pages and command servers, advise on containment, and, for incidents with national implications, bring in other agencies. It also aggregates reports into the statistics that appear in parliamentary replies, which is one reason under-reporting matters to more than the reporting organisation. Breach numbers and their limits are discussed in data breach statistics for India.
What CERT-In does not do
It does not handle an individual's financial fraud; that is the I4C system through 1930 and cybercrime.gov.in. It does not register FIRs or recover money. It does not decide liability or compensation under the Digital Personal Data Protection Act, 2023; that is the Data Protection Board once the rules are in force, with penalties up to ₹250 crore for serious breaches, and a personal data breach may need to be notified to the Board and to affected individuals separately from the CERT-In report. And it does not certify that a company is "compliant"; it empanels auditors who test and report.
Individuals and CERT-In
Anyone can report a phishing website, a fake banking page or a malware sample to CERT-In, and it is worth doing, because takedown protects the next person. For everything else that affects an individual, the channels are elsewhere: 1930 and the portal for fraud, as in how to report cyber crime in India; Chakshu for fraud calls and SMS; the platform grievance officer for impersonation. If your employer or a service you use has been breached and your data leaked, the data leak guide covers the personal steps.
What to do if you are an organisation and it has just happened
- Isolate affected systems; do not wipe them, since logs and disk images are evidence.
- Note the time of detection; the six-hour clock has started.
- Send the preliminary CERT-In report with what you know; update later.
- Preserve logs beyond the 180-day minimum for this incident, and take forensic images before restoring.
- File a police complaint; for extortion or data theft an FIR is needed, and the process is the same as in our FIR guide.
- Assess whether personal data is involved and what the DPDP Act and sector rules require.
- Expect "negotiators" and "decryption services" to contact you; most are the attackers or their affiliates, and the same recovery-agent logic that applies to fraud victims applies here.
The step-by-step compliance detail, including a template for the report and the log retention checklist, is in CERT-In incident reporting: who must report, what, and within six hours. Organisations that want the reporting, containment and regulator communications handled under one roof can use our incident response service, and those preparing in advance can start with CERT-In compliance; the ransomware and data breach page explains what you are likely to face.
Frequently asked questions
Does the six-hour rule apply to a small company?
Yes. The directions apply to all service providers, intermediaries, data centres, body corporates and government organisations, with no size threshold, for the types of incident listed in the annexure. A ten-person startup whose database is accessed without authorisation is within scope. The six hours run from noticing the incident or being told about it, not from its occurrence.
What counts as a reportable incident?
The annexure lists categories including targeted scanning or probing of critical systems, compromise of critical systems, unauthorised access to IT systems or data, defacement, malware and ransomware attacks, identity theft and phishing, denial-of-service attacks, attacks on servers and network devices, data breaches and data leaks, and attacks on applications, cloud, IoT and payment systems. The full list is in the directions.
How do I actually report an incident to CERT-In?
By email to the incident reporting address published on cert-in.org.in, by the online form on the same site, or by the published phone number. The report should give the organisation's details, the type of incident, the systems affected, the time of detection, indicators such as IP addresses or file hashes, and the actions taken so far. A preliminary report within six hours is acceptable; details can follow.
What happens if we do not report in six hours?
Non-compliance with directions under section 70B(6) of the IT Act is punishable under section 70B(7), which provides for imprisonment of up to one year, a fine, or both. In practice, CERT-In's first response is engagement, not prosecution, but a documented failure to report is also damaging in regulatory, insurance and litigation contexts.
Is CERT-In the right place for a phishing SMS or a fraud call I received?
For a phishing website impersonating a bank or a government service, anyone can report the URL to CERT-In, which coordinates takedown. For a fraud call or SMS, Chakshu on Sanchar Saathi is the right channel. For money lost, 1930 and cybercrime.gov.in. CERT-In does not handle individual financial fraud complaints.
If you want help with this
- Online financial fraud response · Money gone through UPI, net-banking, card or wallet. We get the complaint, bank dispute and regulator escalation right, in the order and at the speed that gives frozen money a chance.
- Citizens' cyber safety session · training · A 90-minute session, in Hindi or English, that teaches any group to recognise the four moves of a scam and to hang up at move two.
Keep reading
CERT-In Incident Reporting: Who Must Report, What, When
The six-hour rule is real, it applies to small companies, and most of them have never read it. Who must report, which incidents, how, and th...
Data Breach Statistics India: CERT-In and Breach Costs
Breach numbers for India come from three places that count three things: CERT-In incidents, IBM's survey of costs and Verizon's incident ana...
Chakshu on Sanchar Saathi: Report Fraud Calls and SMS
You did not fall for the "your electricity will be cut" message. Reporting it on Chakshu takes four minutes and can get the number disconnec...
How to Check If Your Data Was Leaked, and What to Do Next
Your email and phone number are almost certainly in a leaked database somewhere. That is a to-do list, not a crisis. How to find out what le...