Skip to main content
Infovion

The CERT-In 6-Hour Rule: What Must Be Reported, How, and How to Be Ready

CERT-In's 2022 Directions give Indian organisations six hours to report 20 kinds of cyber incident and require 180 days of logs kept in India. A plain guide.

Security operations16 November 20268 min readBy Sankalp Deshpande, founder of Infovion Technologies

Short answer: under CERT-In's Directions of 28 April 2022, every service provider, intermediary, data centre, body corporate and government organisation in India must report the cyber incidents listed in the Directions to CERT-In within six hours of noticing them or being told about them, and must keep the logs of all its ICT systems for a rolling 180 days, within Indian jurisdiction. Reports go to incident@cert-in.org.in, by phone to 1800-11-4949 or by fax to 1800-11-6969.

This guide summarises the Directions for planning. It is not legal advice. Read the Directions themselves and CERT-In's FAQs, and take advice on how they apply to you.

Who has to comply

The Directions name five groups: service providers, intermediaries, data centres, body corporates and government organisations. "Body corporate" is wide enough to cover most companies that run computer systems in India. Banks, NBFCs, brokers and insurers have their own regulators' reporting rules as well, and those clocks run separately: telling RBI or SEBI does not count as telling CERT-In.

What the six hours are counted from

The wording is "within 6 hours of noticing such incidents or being brought to notice about such incidents". The clock starts when your organisation becomes aware, including when a customer, vendor or researcher tells you. It does not wait for you to finish investigating. Report what you know, then add to it.

The 20 kinds of incident that must be reported

Annexure I of the Directions lists them:

  1. Targeted scanning or probing of critical networks or systems
  2. Compromise of critical systems or information
  3. Unauthorised access of IT systems or data
  4. Defacement of a website, or intrusion into a website with unauthorised changes such as malicious code or links
  5. Malicious code attacks: virus, worm, Trojan, bots, spyware, ransomware, cryptominers
  6. Attacks on servers such as database, mail and DNS, and on network devices such as routers
  7. Identity theft, spoofing and phishing attacks
  8. Denial of service and distributed denial of service attacks
  9. Attacks on critical infrastructure, SCADA and operational technology systems and wireless networks
  10. Attacks on applications such as e-governance and e-commerce
  11. Data breach
  12. Data leak
  13. Attacks on Internet of Things devices and their systems, networks, software and servers
  14. Attacks or incidents affecting digital payment systems
  15. Attacks through malicious mobile apps
  16. Fake mobile apps
  17. Unauthorised access to social media accounts
  18. Attacks or suspicious activity affecting cloud computing systems, servers, software or applications
  19. Attacks or suspicious activity affecting systems related to big data, blockchain, virtual assets, robotics, 3D and 4D printing, additive manufacturing and drones
  20. Attacks or suspicious activity affecting systems related to artificial intelligence and machine learning

The list is broad on purpose. A successful phishing sign-in, ransomware on one laptop and a defaced website are all on it.

The other duties in the same Directions

DutyWhat the Directions say
LogsEnable logs of all ICT systems and keep them securely for a rolling 180 days, within Indian jurisdiction. Provide them to CERT-In with an incident report or when ordered
ClocksSynchronise all ICT system clocks with the NTP servers of NIC or NPL, or with servers traceable to them
Point of contactDesignate a point of contact for CERT-In and send the details in the format in Annexure II; keep it up to date
Information on requestTake action or provide information when CERT-In orders it, in the format and time it specifies
Data centres, VPS, cloud and VPN providersKeep validated subscriber records for five years or longer

Why six hours is hard

Most of the six hours is usually lost before anyone decides there is an incident. An alert sits in a queue overnight; when it is opened, someone has to work out who the user is, what else happened on that machine, and whether the address has been seen before. Only then does the reporting start, and the report needs a timeline that nobody has written down.

Three things shorten it:

  • Triage every alert when it is raised, at night and on holidays too, so "noticing" and "understanding" happen within minutes of each other.
  • Keep the evidence with the case: the events, the user's history, the enrichment and the verdict in one place, with times in a single time zone.
  • Draft the report from the case, not from memory, and have a named person approve and send it.

A readiness checklist

  • A point of contact is registered with CERT-In, and a deputy knows the process
  • Logging is switched on for servers, endpoints, identity, email, cloud and network devices
  • Logs are kept for 180 days, in India, and someone has tested retrieving a specific day
  • System clocks follow NIC or NPL time
  • Alerts are reviewed around the clock, by people or by automated triage with people approving
  • There is a one-page runbook: who decides it is reportable, who writes, who sends, to which address
  • The reporting format from CERT-In's website is saved where the duty analyst can find it
  • Sector reports (RBI, SEBI, IRDAI) and personal data breach duties are in the same runbook, with their own deadlines
  • The runbook has been rehearsed once with a made-up incident

Where Cyvion fits

Cyvion, our security operations platform, investigates each alert as it arrives, keeps the evidence and timeline in the case, and drafts a CERT-In incident report from it for a person to check and send. It is in early access; the status table lists what is built and what is not. It does not replace your log archive or your decision about what is reportable.

Questions readers ask

What is the CERT-In 6-hour rule?

CERT-In's Directions of 28 April 2022 require service providers, intermediaries, data centres, body corporates and government organisations to report the cyber incidents listed in Annexure I to CERT-In within 6 hours of noticing them or being brought to notice about them.

How do I report an incident to CERT-In?

By email to incident@cert-in.org.in, by phone on 1800-11-4949 or by fax on 1800-11-6969. CERT-In publishes the reporting methods and formats on www.cert-in.org.in.

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

Logs of all ICT systems must be enabled and maintained securely for a rolling period of 180 days, within Indian jurisdiction, and provided to CERT-In with an incident report or when ordered.

Which incidents must be reported to CERT-In?

Twenty types listed in Annexure I, including unauthorised access, website defacement, malware and ransomware, phishing and identity theft, denial of service, data breaches and leaks, and attacks on cloud, payment, IoT and AI systems.

Does reporting to RBI or SEBI satisfy the CERT-In requirement?

No. Sector regulators' reporting rules are separate. A regulated entity generally has to report to its regulator and to CERT-In, each within its own deadline.

When does the six-hour clock start?

When the organisation notices the incident or is told about it by someone else. It does not wait for the investigation to finish.

CERT-InIncident reportingSOCCompliance

Found this useful? See more guides like this in your Google results.

Add Infovion as a preferred source on Google

See Cyvion work on your own alerts

Cyvion investigates every alert, shows its evidence and drafts the incident report. Early access, with a demonstration on a call.

Keep reading