When CERT-In issued its Directions in April 2022, the six-hour reporting window made headlines and caused real worry among Indian companies. The text itself is short: eight pages, including annexures. This article explains what it actually requires, who it applies to, and how to get ready, based on the official document (CERT-In Directions under Section 70B(6), 28 April 2022). It is practical guidance, not legal advice; for edge cases, read the text with your counsel.
Who do the CERT-In Directions apply to?
The Directions are addressed to "service providers, intermediaries, data centres, body corporate and Government organisations". In practice, "body corporate" covers most companies, which is why the Directions are relevant to far more than ISPs and data centres. The Directions became effective 60 days after they were issued.
The six main requirements
1. Report listed incidents within 6 hours
Entities must "mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within 6 hours of noticing such incidents or being brought to notice about such incidents." Reports can be sent by email to incident@cert-in.org.in, by phone on 1800-11-4949 or by fax on 1800-11-6969, and CERT-In publishes reporting formats on its website.
Note the trigger: the clock starts when you notice the incident or someone brings it to your notice, not when the attack began.
2. Keep logs for 180 days, within India
All covered entities must "mandatorily 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 with an incident report or when directed. CERT-In's FAQ on the Directions adds that logs may also be stored outside India, as long as they can be produced to CERT-In in reasonable time.
3. Synchronise clocks
ICT systems must connect to the NTP server of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to NTP servers traceable to them. Entities spanning multiple geographies may use other accurate time sources, provided they do not deviate from NPL and NIC. Accurate time is what makes logs from different systems usable together in an investigation.
4. Designate a Point of Contact
Each entity must designate a Point of Contact to interface with CERT-In and send the details (name, designation, organisation, address, email, mobile and office phone) to info@cert-in.org.in in the format in Annexure II, keeping it updated.
5. Respond to CERT-In orders
When CERT-In directs, the entity must take action or provide information, potentially in near real time and within a specified timeframe. Failure is treated as non-compliance.
6. Extra duties for infrastructure and virtual asset providers
Data centres, VPS providers, cloud service providers and VPN service providers must register and keep, for 5 years or longer, validated customer names, period of hire, allotted IPs, email and IP used at registration, purpose of hiring, validated address and contact numbers, and ownership pattern. Virtual asset service providers, exchanges and custodian wallet providers must keep KYC information and financial transaction records for five years.
Which incidents must be reported?
Annexure I lists 20 categories. Grouped for clarity:
| Group | Incident types listed in Annexure I |
|---|---|
| Intrusion and access | Targeted scanning or probing of critical networks; compromise of critical systems; unauthorised access to IT systems or data; unauthorised access to social media accounts |
| Malware | Virus, worm, Trojan, bots, spyware, ransomware, cryptominers; attacks through malicious mobile apps; fake mobile apps |
| Web and application | Website defacement or intrusion; attacks on applications such as e-governance and e-commerce |
| Infrastructure | Attacks on database, mail and DNS servers and network devices; DoS and DDoS; attacks on critical infrastructure, SCADA, OT and wireless networks; IoT attacks; cloud attacks |
| Data | Data breach; data leak |
| Fraud and identity | Identity theft, spoofing and phishing; attacks affecting digital payment systems |
| Emerging technology | Big data, blockchain, virtual assets, robotics, 3D/4D printing, drones; artificial intelligence and machine learning systems |
The list is broad. "Targeted scanning" and "phishing attacks" are on it, so a reasonable internal policy is needed to decide what counts as reportable in your context. A cautious policy is: when in doubt, report, then update. CERT-In's FAQ also gives criteria for what should be reported within the 6 hours, including severe intrusions, ransomware, data breaches and data leaks, and incidents affecting human safety (CERT-In FAQs, May 2022).
What happens if you do not comply?
The Directions state that failure to furnish information or non-compliance may invite punitive action under sub-section (7) of Section 70B of the IT Act and other applicable laws. Beyond penalties, the practical risk is that an incident handled late and without logs is far harder to investigate, insure or defend.
How does this sit with the DPDP Act?
If an incident involves personal data, the DPDP framework adds separate duties: intimation to the Data Protection Board and to each affected person, with a detailed report to the Board within 72 hours under the DPDP Rules, 2025 once those provisions commence (DPDP Rules, 2025). The two regimes run in parallel. One incident can require a CERT-In report in 6 hours and DPDP intimations as well. We cover the DPDP side in detail on our DPDP compliance page.
Three common misunderstandings
- "Our cloud provider handles it." Your provider has its own obligations, but logs of your applications and accounts, and the decision to report an incident affecting your business, remain yours.
- "We will report once we know the full picture." Waiting for certainty is how six hours become six days. CERT-In's FAQ says you may report the information available at the time and send additional details later within reasonable time.
- "We have logs, so we are compliant." Logs that roll over after 30 days, or cannot be searched and handed over when CERT-In asks, do not meet the intent of the Directions.
CERT-In readiness checklist
- Name your Point of Contact and a deputy, and send the Annexure II details to CERT-In.
- Write a one-page reporting procedure: who decides an incident is reportable, who sends the report, and the template to use.
- Turn on logging for servers, network devices, firewalls, VPN, identity systems, cloud accounts and key applications.
- Store logs for 180 days in India, protected against tampering, and test that you can actually retrieve them.
- Set NTP on all systems to NIC or NPL sources, or traceable equivalents, and monitor drift.
- Brief management that a 6-hour clock exists, so nobody delays a report for an approval chain.
- Run a tabletop exercise: simulate a ransomware or data leak at 7 p.m. on a Friday and time the report.
- Check vendors: if your cloud, SOC or hosting provider holds your logs, confirm location and retention in the contract.
- If you are a VPS, cloud, VPN or data centre provider, verify your customer records meet the 5-year requirement.
A practical tip on the 6-hour window
Six hours is not enough to finish an investigation, and the Directions do not expect it. What you need in six hours is a clear initial report: what was noticed, when, which systems, what you have done so far, and a contact. Prepare the template now with fields pre-filled, so the report on the day takes minutes, not a committee meeting.
How Cehpoint can help
Cehpoint's virtual CISO service sets up the CERT-In compliance framework for you: Point of Contact, reporting procedure and templates, log and time-sync configuration, and tabletop exercises with management. Our Managed SOC provides the monitoring and India-resident log retention that make the 6-hour window achievable in practice.