CERT-In Incident Reporting: Who Must Report, What, When
CERT-In incident reporting under the 28 April 2022 directions: who the six-hour rule covers, the listed incident types, how to file, 180-day logs and penalties.

In short
- The CERT-In directions of 28 April 2022, issued under section 70B(6) of the IT Act, apply to all service providers, intermediaries, data centres, body corporates and government organisations, with no size threshold.
- Listed cyber incidents must be reported to CERT-In within six hours of noticing them or being notified of them; partial information at six hours is acceptable and can be updated.
- Two standing duties come with it: keep ICT system logs for a rolling 180 days within India, and synchronise clocks with the NIC or NPL NTP servers.
- VPN, cloud, data centre and virtual asset providers have additional record-keeping duties, including customer details for five years.
- Non-compliance is punishable under section 70B(7) of the IT Act; the practical cost is also a lost insurance claim and a weak position before the DPDP Board.
Who this is for: Owners, IT heads and compliance officers of Indian companies, service providers, data centres, intermediaries and government organisations.
On 28 April 2022, CERT-In issued directions under section 70B(6) of the IT Act that changed what every Indian organisation must do when something goes wrong. Report within six hours. Keep logs for 180 days. Sync your clocks. Most large companies built a process; most small ones have never read the document. This guide to CERT-In incident reporting is the practical version: who, what, how, and what else comes with it.
Who the CERT-In incident reporting directions cover
The directions apply to "service providers, intermediaries, data centres, body corporate and Government organisations". The phrase that catches most readers is body corporate. It means any company, firm, sole proprietorship or association engaged in commercial or professional activity. There is no turnover threshold, no headcount threshold and no exemption for MSMEs. A ten-person CA firm with a compromised mailbox is covered in exactly the same way as a bank.
Specific categories carry extra duties, described later: data centres, VPN providers, cloud service providers, virtual private server providers, and virtual asset service providers and exchanges. CERT-In published a set of FAQs in May 2022 that clarified scope; among other things, they confirmed that the reporting duty attaches when an incident is noticed or notified, and that enterprise and corporate VPNs are treated differently from consumer VPN services. Read the directions and the FAQs together on cert-in.org.in.
What must be reported: the listed incident types
Annexure I of the directions lists the incidents that are mandatorily reportable. Paraphrased, they include:
| Incident type | What it looks like in practice |
|---|---|
| Targeted scanning or probing of critical systems | Repeated reconnaissance of your servers from a specific source |
| Compromise of critical systems or information | An attacker inside the ERP, the domain controller or a database |
| Unauthorised access to IT systems or data | A compromised mailbox, a staff login used by an outsider |
| Website defacement or intrusion, including malicious code | Your site altered, or serving malware or redirects |
| Malicious code attacks | Virus, worm, trojan, botnet, spyware, cryptominer |
| Ransomware attacks | Encryption of systems with a payment demand |
| Data breach and data leak | Customer or employee data taken or exposed |
| Attacks on servers, network equipment and applications | Database, mail, DNS servers; routers; web applications |
| Identity theft, spoofing and phishing attacks | Your domain or brand used to phish; staff credentials phished |
| Denial of service and distributed denial of service | Site or service knocked offline by traffic |
| Attacks on critical infrastructure, SCADA, OT and wireless networks | Factory, utility and plant control systems |
| Attacks on IoT devices and related systems | Compromised cameras, sensors, smart devices |
| Attacks or incidents affecting digital payment systems | Payment gateway, UPI integration or POS compromise |
| Fake mobile apps | An app impersonating yours on a store or sideloaded |
| Unauthorised access to social media accounts | Company Instagram, X or LinkedIn hijacked |
| Attacks affecting cloud, big data, AI, blockchain, robotics, 3D and additive manufacturing, drones, and similar systems | Compromise of these specific technologies |
Two entries surprise small businesses. A phished staff mailbox used to send fraudulent invoices is "unauthorised access" and "phishing"; the BEC explainer shows how common that is. And a hijacked company Instagram account is expressly listed. Both are reportable within six hours.
How to report, step by step
- Designate a point of contact now. The directions require organisations to designate a point of contact for CERT-In and to share the details. Name a person, give CERT-In the contact details in the prescribed format, and keep it current.
- Download the incident reporting form from cert-in.org.in and store a copy somewhere that is not on the network that might be encrypted, along with the email address and toll-free number.
- When an incident is noticed, start the clock. Note the time of noticing. Six hours later is the deadline.
- Fill what you know. Organisation name and sector, point of contact, incident type from the list, affected systems and their location, date and time noticed, a short description, and actions taken so far. Partial information is acceptable; the FAQs say so.
- Send to incident@cert-in.org.in and keep the sent message. Report by phone as well if email is affected. Record the acknowledgement.
- Update as you learn more. Follow-up reports with root cause, scope and remediation are expected and help if CERT-In issues guidance.
- Do the parallel reports. 1930 and cybercrime.gov.in if money moved; the Data Protection Board and affected individuals if personal data was breached; the insurer within the policy window; the bank in writing for any payment-related compromise.
The two standing duties: logs and clocks
Logs for 180 days. All covered entities must enable logs of all their ICT systems and maintain them securely for a rolling period of 180 days, within Indian jurisdiction, and provide them to CERT-In when ordered or when reporting an incident. For a small company this means: firewall and router logs, server event logs, email admin audit logs, cloud console audit logs and endpoint logs, exported to storage that will survive a ransomware event. Logs stored only on the file server are gone when the file server is encrypted.
NTP synchronisation. System clocks must be synchronised with the Network Time Protocol servers of the National Informatics Centre or the National Physical Laboratory, or with servers traceable to them. It sounds trivial; it is what makes logs from different systems line up in an investigation, and it is a one-line change on most devices.
Extra duties for infrastructure providers
Data centres, VPS providers, cloud service providers and VPN service providers must register and keep accurate information about their subscribers or customers for five years or longer after cancellation: validated names, ownership, period of hire, IP addresses allotted and in use, email and IP at registration, purpose, validated address and contact numbers. Virtual asset service providers, exchanges and custodian wallet providers must maintain KYC records and transaction records for five years. These provisions prompted several consumer VPN companies to remove Indian servers in 2022; the FAQs clarified that enterprise VPNs used by companies for their own staff are not in scope.
Penalties, and the costs that are not penalties
Section 70B(7) of the IT Act makes failure to provide information or comply with CERT-In's directions punishable with imprisonment up to one year, a fine up to ₹1 lakh, or both. Prosecutions have been rare. The costs that bite in practice are different: an insurer declining a claim because the incident was not reported as the policy required; a customer contract breached because the security schedule promised CERT-In compliance; and a weak position before the Data Protection Board when a breach under the DPDP Act is examined and the company cannot show it reported or kept logs.
Setting this up in a week
CERT-In readiness checklist
- Point of contact designated and details shared with CERT-In
- Incident reporting form, email address and phone number stored offline and in the incident plan
- List of reportable incident types circulated to IT, finance and whoever manages social media
- Logs enabled on firewall, servers, email and cloud consoles, exported to India-hosted storage, retained 180 days
- Clocks on all devices synchronised to NIC or NPL NTP servers
- A six-hour drill run once: someone "notices" a scenario, and the form is completed and sent to an internal address against the clock
- Parallel reporting map written: 1930, portal, DPDP Board, insurer, bank
Most of this is a few hours of configuration and one meeting. If you want it set up and documented so it can be shown to an auditor, insurer or customer, our CERT-In compliance service does the logging, NTP, point-of-contact registration and the drill, and incident response is available for the day the clock actually starts. The wider role of the agency is covered in our CERT-In explainer and on the CERT-In page. Start with the point of contact and the offline copy of the form; both take ten minutes and both are what companies wish they had done when the first call comes in.
Frequently asked questions
We are a 15-person company. Does CERT-In incident reporting apply to us?
Yes. The directions cover "body corporate", which includes any company, firm or association engaged in commercial activity, without a turnover or headcount threshold. If a listed incident happens, such as ransomware, a data breach or a compromised email account used for fraud, you must report it within six hours of becoming aware. Set up the process before you need it.
What counts as "noticing" the incident for the six-hour clock?
The clock starts when you notice the incident or are notified about it, not when it began. If a customer tells you at 10 a.m. that your website is serving malware, the report is due by 4 p.m. The CERT-In FAQ issued after the directions clarifies that preliminary information is acceptable within six hours, with details to follow.
How do we actually send the report?
Use the incident reporting form on cert-in.org.in and email it to incident@cert-in.org.in; a toll-free number and fax are also listed on the site. Include your organisation details, the designated point of contact, the type of incident, affected systems, when it was noticed and what you have done. Keep the sent email and any acknowledgement.
What logs must be kept, and where?
Logs of all your ICT systems, meaning servers, firewalls, network devices, cloud consoles, applications and endpoints where feasible, for a rolling period of 180 days, maintained within Indian jurisdiction. The directions require them to be provided to CERT-In on request. Cloud services with log export to India-hosted storage satisfy this if configured.
Does reporting to CERT-In replace the DPDP Act breach notification?
No. They are separate duties to separate bodies. CERT-In handles cyber incidents under the IT Act; the Data Protection Board handles personal data breaches under the DPDP Act, which also requires notifying affected individuals. A ransomware incident with customer data taken triggers both, plus a police complaint if you want an FIR.
If you want help with this
- CERT-In directions compliance · The April 2022 CERT-In directions apply to every organisation in India. Six-hour incident reporting, 180-day logs, synchronised clocks and KYC duties for providers. We make them workable and show you are meeting them.
- 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.
- 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.
Keep reading
CERT-In: Its Role, Incident Reporting and the Six-Hour Rule
CERT-In is the agency a company calls when its servers are encrypted, not the one a victim calls when a UPI payment goes wrong. Here is what...
Ransomware Response Plan: The Playbook for Indian SMEs
Ransomware at a 60-person company is a bad week, not the end, if the first hour is handled right. Isolate, preserve, report, decide, restore...
Business Email Compromise: How Accounts Teams Get Fooled
No malware, no hacking of the bank. Just an email that looks right, sent at the right moment, to the person who pays the bills. How BEC work...
DPDP Act 2023 Compliance Checklist for Indian Businesses
Twelve things an Indian business has to be able to show under the DPDP Act, in the order to do them, with the section behind each and the pe...