India compliance

CERT-In 6-hour incident reporting: a runbook for Indian companies

CERT-In's 2022 directions give most organisations in India six hours to report specified cyber incidents. That only works if the decision to report is made in the first hour.

Short answer

The CERT-In 6 hour incident reporting rule comes from directions issued on 28 April 2022: service providers, intermediaries, data centres, body corporates and government organisations in India must report specified cyber security incidents to CERT-In within six hours of noticing them. The same directions require 180 days of ICT logs kept in India and clocks synchronised to NIC or NPL servers.

Key takeaways

  • Six hours runs from when you notice the incident or it is brought to your notice.
  • Only incident types listed in the directions' annexure are reportable, but the list is broad.
  • Keep ICT logs for a rolling 180 days within Indian jurisdiction.
  • Synchronise system clocks to NIC or NPL NTP servers so timelines hold up.

What the directions require

  • Report specified cyber incidents to CERT-In within six hours of noticing them or being told about them.
  • Keep logs of all ICT systems for a rolling 180 days, within Indian jurisdiction, and provide them to CERT-In on request.
  • Synchronise ICT system clocks with the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL).
  • Designate a point of contact to interface with CERT-In.

Which incidents are reportable

The annexure to the directions lists the incident types. They include targeted scanning of critical networks, compromise of critical systems, unauthorised access to IT systems and data, website defacement, malicious code attacks, attacks on servers, identity theft and phishing, denial-of-service attacks, data breaches and data leaks, and attacks on cloud and IoT systems. Read the full list: it is wider than many teams expect.

A six-hour clock, hour by hour

Time from noticingWhat happens
0 to 1 hourTriage: confirm it is an incident and check it against the annexure list
1 to 2 hoursDecision to report, by the named decision-maker or deputy
2 to 5 hoursComplete the report with what is known; do not wait for root cause
Before 6 hoursSubmit to CERT-In and record the submission time
After submissionSend updates as the investigation progresses

The most common failure is waiting for the investigation to finish before reporting. The directions expect a timely report with the facts available, followed by updates.

Checklist

CERT-In reporting readiness

0 of 7 done

How it fits with other obligations

CERT-In reporting sits alongside sector rules, such as RBI and SEBI incident reporting, and the DPDP Act's breach reporting to the Data Protection Board once it applies. One incident can trigger several reports with different clocks, so keep a single incident record and track each notification from it.

Put this into practice on QULDEX

Frequently asked questions

How quickly must cyber incidents be reported to CERT-In?

Within six hours of noticing the incident or of it being brought to the organisation's notice, under CERT-In's directions of 28 April 2022.

How long must logs be kept under the CERT-In directions?

For a rolling period of 180 days, within Indian jurisdiction.

Sources

  1. Directions under sub-section (6) of section 70B of the Information Technology Act, 2000 (28 April 2022), CERT-In
  2. FAQs on the Cyber Security Directions of 28 April 2022, CERT-In
  3. Information Technology Act, 2000 (section 70B), India Code