Let me clear up something that confuses a lot of juniors over a cup of chai: in India there are two separate legal tracks for a security incident, and they have different triggers, different recipients and different clocks. One is the CERT-In reporting regime under the Information Technology Act. The other is the personal data protection regime under the Digital Personal Data Protection Act, 2023, usually called the DPDP Act. A single incident can trigger both, one, or neither. A note up front: I am explaining concepts for a technical audience, this is not legal advice, and rules get amended, so check the current text with your legal team.

Track one: CERT-In and the six-hour rule

CERT-In is the Indian Computer Emergency Response Team, the national agency for cyber incidents, working under the Ministry of Electronics and Information Technology. Under section 70B of the IT Act, it can issue directions. The ones most people mean were issued on 28 April 2022 and came into force about two months later.

The headline requirement: service providers, intermediaries, data centres, body corporates and government organisations must report specified cyber security incidents to CERT-In within six hours of noticing them or being notified. The directions include an annexure listing the types, which covers things like compromise of critical systems, unauthorised access to IT systems or data, data breaches and leaks, attacks on servers or applications, ransomware-type events, and targeted scanning or probing of critical networks. Read the actual list rather than relying on memory; it is longer and more specific than most summaries suggest.

Two practical points. First, “noticing” starts the clock, so your detection and triage must be quick enough to recognise a reportable event, and your reporting path must be rehearsed. Waiting for a full investigation is not an option; you can report with what you know and supplement later. Second, reporting goes through the channels CERT-In publishes (an email address and a web form, plus phone). Keep those details in your incident plan.

The same directions add operational duties that security teams feel directly:

  • Maintain logs of ICT systems for a rolling 180 days, and keep them within Indian jurisdiction.
  • Synchronise system clocks to the NTP servers of the National Informatics Centre or the National Physical Laboratory, or sources traceable to them, so timelines line up across organisations.
  • Provide logs and information when CERT-In asks.
  • Designate a point of contact for CERT-In.

Some sectors have their own regulators with additional rules, for example the RBI for banks and regulated payment entities, SEBI for market participants, and IRDAI for insurers. Where both apply, you generally satisfy both.

Track two: the DPDP Act and personal data breaches

The DPDP Act is about digital personal data. Learn its vocabulary, because it is not the same as GDPR’s. The organisation deciding the purpose and means of processing is the Data Fiduciary. The individual whose data it is, is the Data Principal. A company processing on a fiduciary’s behalf is a Data Processor.

Two obligations matter to a security team. The Act requires a Data Fiduciary to protect personal data in its possession by taking reasonable security safeguards to prevent a personal data breach. And, in the event of a breach, it must inform the Data Protection Board of India and each affected Data Principal, in the form and manner the rules prescribe. The penalty schedule in the Act is steep: failure to maintain reasonable security safeguards can attract a penalty up to ₹250 crore, and failure to give the breach notice can attract up to ₹200 crore. These are upper limits, set by the Board’s assessment of the circumstances, not automatic fines.

The detailed Rules under the Act were notified in late 2025, with obligations phased in over a period instead of all at once. As I understand them, they expect breach intimation without delay and a more detailed report to the Board within a set window (72 hours is the figure in the rules as notified), and they list baseline safeguards such as encryption or masking, access control, logging and monitoring, and retention of logs for a minimum period. Confirm the commencement dates and exact wording before you build a compliance plan around them.

How the two tracks differ

CERT-In directionsDPDP Act
Triggered byListed types of cyber incident, regardless of personal dataPersonal data breach
Reported toCERT-InData Protection Board and affected individuals
TimingSix hours from noticingWithout delay, with a detailed report later
Own dutiesLog retention, NTP sync, point of contactReasonable safeguards, notice, consent and rights handling

Example: a ransomware attack on a factory’s control network, with no personal data involved, is a CERT-In matter. A misconfigured storage bucket exposing customer phone numbers is a likely DPDP matter and may also fit CERT-In’s data leak category. Often it is both.

What to prepare before the bad day

  • A one-page decision guide for the on-call analyst: which events need escalation to legal and compliance, and who decides.
  • A pre-filled reporting template with your organisation’s details.
  • A data map: which systems hold personal data, whose, and where. You cannot notify people if you cannot tell who was affected.
  • Logs retained for the required period, in the right place, with accurate clocks.
  • Contract clauses that make vendors and processors tell you quickly about incidents on their side, since their delay becomes your delay.

The pattern to remember is simple. Detect fast, decide who is responsible for the call, report in the shortest timeline that applies, and keep records of what you knew and when. Regulators tend to judge the quality of your process as much as the incident itself.

Leave a Reply

Trending