Prodigy Legal Logo

Guide · Technology law

CERT-In Cyber Incident Reporting: The 6-Hour Rule

On 28 April 2022, the Indian Computer Emergency Response Team (CERT-In) issued directions under section 70B(6) of the Information Technology Act, 2000. They require organisations to report specified cyber security incidents within six hours of noticing them, keep logs in India, and sync their clocks to Indian time sources.

Many companies now face two reporting regimes after a breach: CERT-In, and the Data Protection Board under the DPDP Act. This guide explains both and how to prepare for them together.

Who the directions apply to

The directions apply to service providers, intermediaries, data centres, body corporates and government organisations. 'Body corporate' includes any company, firm or association of individuals carrying on commercial or professional activities. In practice, almost every Indian company with IT systems is covered, along with foreign companies serving users in India. CERT-In's FAQs on the directions explain how it reads their scope; read them alongside the directions.

The core duties

DutyWhat the directions require
6-hour reportingReport the incident types listed in Annexure I to CERT-In within 6 hours of noticing them or being told about them.
Point of contactDesignate a point of contact to interface with CERT-In, and share their details in the specified format.
Log retentionEnable logs of all ICT systems and keep them securely for a rolling period of 180 days, within Indian jurisdiction.
Clock synchronisationConnect to the NTP server of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to servers traceable to them.
Information on requestProvide information and assistance when CERT-In asks, within the time it specifies.
Customer records (some providers)Data centres, VPS and cloud service providers and VPN providers must keep specified customer information for 5 years.
KYC records (virtual assets)Virtual asset service providers, exchanges and custodian wallet providers must keep KYC and transaction records for 5 years.

Which incidents must be reported

Annexure I lists the incident types. They include targeted scanning or probing of critical networks, compromise of critical systems, unauthorised access to IT systems or data, website defacement and malicious code on websites, malware and ransomware attacks, identity theft and phishing, denial of service attacks, attacks on servers, data breaches and data leaks, attacks on IoT devices, attacks on cloud computing systems, and unauthorised access to social media accounts. Read the full list; it is broader than many teams expect.

Six hours runs from when you notice the incident, not when you finish investigating it. Send what you know and update later. Reports go to CERT-In through the channels it publishes on its website, in the format it specifies.

How CERT-In fits with DPDP breach reporting

The DPDP Act, 2023 and the DPDP Rules, 2025 create a separate duty. Under section 8(6) of the Act and the Rules, a data fiduciary must inform each affected data principal and the Data Protection Board of a personal data breach without delay, and send the Board a detailed report within 72 hours of becoming aware of it, or a longer period if the Board allows. The detailed report covers the facts, circumstances and reasons for the breach, steps taken to mitigate risk, the findings about the person who caused it, remedial measures, and the reports made to affected people.

The two regimes are independent. Reporting to CERT-In does not satisfy the DPDP duty, and the reverse is also true. A ransomware attack on a database of customer records will usually need both: a CERT-In report within 6 hours, and DPDP notices to the Board and to affected people.

CERT-In directionsDPDP Act and Rules
TriggerAny listed cyber security incident, with or without personal dataAny personal data breach
Who reportsService providers, intermediaries, data centres, body corporates, governmentThe data fiduciary
To whomCERT-InThe Data Protection Board and each affected data principal
WhenWithin 6 hours of noticingWithout delay; detailed report to the Board within 72 hours
LawSection 70B, IT Act, 2000Section 8(6), DPDP Act, 2023 and the DPDP Rules, 2025

Preparing before an incident

  • Write one incident response plan that covers both CERT-In and DPDP reporting, with named owners.
  • Appoint and register your CERT-In point of contact, and keep a deputy.
  • Confirm that logs from all systems, including cloud and SaaS tools, are kept for 180 days in India.
  • Check NTP settings on servers and cloud instances.
  • Prepare report templates for CERT-In, the Data Protection Board and affected users.
  • Make vendors and processors tell you of incidents quickly enough for you to meet the 6-hour window.
  • Run a tabletop exercise at least once a year.

How we help

Prodigy Legal prepares incident response plans, reviews vendor contracts for breach notice terms, and advises during an incident on what to report, to whom and when. The Tech & IP monthly plan includes IT Act and CERT-In compliance and the DPDP compliance programme, with the senior lawyer on call for urgent matters.

Frequently asked questions

Does the 6-hour CERT-In rule apply to small companies?

The directions apply to body corporates generally, without a size threshold. CERT-In extended the compliance date for micro, small and medium enterprises when the directions were introduced, but did not exempt them.

Can we store logs outside India if we keep a copy?

The directions require logs to be maintained within Indian jurisdiction for 180 days. Logs may also exist elsewhere, but the Indian copy must be available to CERT-In. Read CERT-In's FAQs for how it applies this to cloud services.

Is a personal data breach reportable to CERT-In and the Data Protection Board?

Often both. A data breach is a listed incident under the CERT-In directions, and a personal data breach must also be reported under the DPDP Act and Rules. Plan to meet both timelines.

What is the penalty for not reporting to CERT-In?

Section 70B(7) of the IT Act provides for imprisonment of up to one year, a fine of up to one lakh rupees, or both, for failing to provide information or comply with directions.

Last reviewed: 2026-11-22. This guide gives general information about Indian law for companies. It is not legal advice, and every matter turns on its own facts.

Send us a message

CallWhatsApp