CERT-In’s six-hour rule: what the 2022 Directions actually require
Every body corporate in India must report twenty incident categories to CERT-In within six hours — plus five continuous obligations, including 180 days of logs.
The CERT-In Directions are the most widely applicable cyber instrument in India and the least often read. They bind every body corporate in the country, not a sector; they have been in force since June 2022; and the obligation most people know about — six-hour incident reporting — is one of six, of which the other five are the ones organisations are usually found short on.
Who this binds
The Directions were issued under sub-section (6) of section 70B of the Information Technology Act, 2000, which empowers CERT-In to call for information and give directions to five classes of entity: service providers, intermediaries, data centres, body corporate and Government organisations. There is no revenue threshold, no sector test and no carve-out for small entities.
“Body corporate” is the phrase that does the work. Practically every company operating in India falls inside it, which is what separates this instrument from the sectoral frameworks: a bank answers to the RBI and to CERT-In, a broker to SEBI and to CERT-In, and a manufacturer with no financial regulator at all still answers to CERT-In.
The six-hour clock
- DORA, initial notification — from classifying it major
- CERT-In
- RBI, on DAKSH
- SEBI, initial notice
- IRDAI, through CERT-In
- IFSCA
- Stock exchanges, if listed and material
- SEBI portal, full details
- NIS2, early warning
- CRA, early warning
- US bank regulators
- IFSCA, interim report
- GDPR, supervisory authority
- NIS2, incident notification
- DORA, intermediate report
- NYDFS, 500.17(a)
- SEC Form 8-K
- IFSCA, root cause analysis
- FTC Safeguards Rule
The reporting obligation is the second of the six directions, and its wording matters more than the number does. An incident must be reported within six hours of noticing it or being brought to notice about it. The clock does not start when the incident began, when it was confirmed, or when the response team finished triaging. It starts at the moment of awareness, however that awareness arrived — including from a customer, a journalist or a researcher.
Reports go to CERT-In by email at incident@cert-in.org.in, by phone on 1800-11-4949 or by fax on 1800-11-6969, with methods and formats published on the CERT-In website and updated from time to time.
Six hours is short enough that it is an operational constraint rather than a reporting one. An organisation that cannot establish, inside six hours, that something has happened and roughly what it is has already failed the timeline regardless of how good its eventual report is. That is the part worth designing for.
What has to be reported
Annexure I lists twenty categories. The list is broader than the phrase “cyber incident” usually implies — it includes targeted scanning of critical systems, which is a precursor rather than a breach, and it reaches technologies that were unusual in 2022:
Intrusion and compromise
- Targeted scanning or probing of critical networks and systems
- Compromise of critical systems or information
- Unauthorised access of IT systems or data
- Website defacement, or intrusion and unauthorised changes such as inserting malicious code or links
- Malicious code attacks — virus, worm, Trojan, bots, spyware, ransomware, cryptominers
- Attacks on servers such as database, mail and DNS, and on network devices such as routers
Identity, availability and data
- Identity theft, spoofing and phishing attacks
- Denial of Service and Distributed Denial of Service attacks
- Data breach
- Data leak
- Unauthorised access to social media accounts
Infrastructure and applications
- Attacks on critical infrastructure, SCADA and operational technology systems, and wireless networks
- Attacks on applications such as e-governance and e-commerce
- Attacks affecting digital payment systems
- Attacks or suspicious activity affecting cloud computing systems, servers, software and applications
Devices and emerging technology
- Attacks on Internet of Things devices and associated systems, networks, software and servers
- Attacks through malicious mobile applications
- Fake mobile applications
- Attacks affecting Big Data, blockchain, virtual assets, virtual asset exchanges, custodian wallets, robotics, 3D and 4D printing, additive manufacturing and drones
- Attacks affecting systems related to Artificial Intelligence and Machine Learning
Two of those categories are worth pausing on. Targeted scanning or probing of critical networks is reportable, and most organisations see it continuously — which makes the definition of “critical” and “targeted” a decision to take deliberately rather than during an incident. And the final category reaches attacks affecting Artificial Intelligence and Machine Learning systems, written into the Annexure in 2022 and increasingly less theoretical.
The five obligations that are not reporting
The reporting clock gets the attention. The other five directions are continuous obligations that either exist in your estate today or do not, and they are what an inspection actually looks at.
| Direction | Who | What |
|---|---|---|
| Clock synchronisation | All five classes | Synchronise all ICT system clocks to NIC or NPL NTP servers, or to sources traceable to them. Entities spanning multiple geographies may use another accurate standard source, provided it does not deviate from NPL and NIC |
| Incident reporting | All five classes | Annexure I incidents, within six hours of noticing or being notified |
| Point of Contact, and response to directions | All five classes | Designate a Point of Contact to interface with CERT-In, in the Annexure II format, kept updated. Provide information, action or assistance when ordered — in the format specified, up to and including near real-time, within the timeframe given |
| Log retention | All five classes | Enable logs of all ICT systems and maintain them securely for a rolling 180 days, within Indian jurisdiction — or abroad if they can be produced to CERT-In in reasonable time, per CERT-In's own FAQ — produced with an incident report or on direction |
| Subscriber records | Data centres, VPS, cloud and VPN service providers | Register and maintain validated subscriber details for five years after the registration is cancelled or withdrawn — names, period of hire, IPs allotted, registration email, IP and timestamp, purpose, validated address and contact numbers, and ownership pattern |
| Virtual asset records | Virtual asset service providers, exchanges and custodian wallet providers | Maintain KYC and financial transaction records for five years, in a form that lets an individual transaction be reconstructed — parties, IP addresses with timestamps and time zones, transaction ID, public keys or equivalent identifiers, accounts, nature, date and amount |
The two that catch people out
Where the logs live. The 180-day retention is unremarkable; the location requirement is not, and the regulator has read it more loosely than its own text. The Directions say logs “shall be maintained within the Indian jurisdiction”. CERT-In's own FAQ then allowed storage outside India, provided the logs can be produced to CERT-In within a reasonable time (Q35) — but kept logs and records of financial transactions for services offered in India within Indian jurisdiction (Q36). A logging pipeline that terminates abroad therefore rests on a clarification rather than the direction itself, and on being able to produce the logs quickly. Keeping a copy in India removes the argument.
Clock synchronisation. It reads like housekeeping and is the reason the rest works: correlating an incident across systems, and producing logs that stand up when CERT-In asks for them, both depend on the timestamps agreeing. It is also trivially auditable, which makes it a poor thing to be found wrong on.
What non-compliance carries
Failure to furnish information when called for, or non-compliance with the directions, may invite punitive action under sub-section (7) of section 70B of the IT Act, 2000, and under other laws as applicable. The Directions state this in terms and do not qualify it by entity size.
The practical exposure is usually not the penalty in isolation. It is that an organisation which cannot produce 180 days of logs, or cannot show when it became aware of an incident, is in a materially worse position in every conversation that follows — with CERT-In, with a sector regulator running its own clock, and with customers under contractual notification terms of their own.
What to have in place before you need it
- A named Point of Contact, registered and current. The Annexure II format is short. An out-of-date PoC means CERT-In's directions arrive at someone who has left, and the timeframe in them runs anyway.
- A decision, taken in advance, about what “critical” means. Several Annexure I categories are scoped by criticality. Deciding which systems and networks are critical during an incident is deciding it badly.
- Evidence of when you became aware. The clock runs from awareness, so the defensible position is a record of when the alert fired or the report arrived — not a reconstruction offered afterwards.
- Logs that are complete, retained 180 days, and in India. Check where they actually live rather than where the architecture diagram says they do.
- One filing plan covering every regulator you answer to. A bank runs the CERT-In clock and the RBI's DAKSH clock simultaneously; an insurer may add IRDAI. Six hours is not long enough to work out who files what.
All five are things a room discovers it has not done at about the four-hour mark. The incident tabletop generator is the cheap way to have that discovery on a Tuesday afternoon instead: it builds a ninety-minute exercise for your entity class, with the six-hour clock falling due inside it.
Where BitScore fits, and where it does not
A security rating does not discharge any part of these Directions. Reporting, logging, clock synchronisation and record retention are internal obligations, and an externally calculated rating has no view of them. Anyone suggesting otherwise is selling something.
What continuous external monitoring changes is the input to the six-hour clock. The clock starts when you notice, and a substantial share of organisations notice through someone else — a customer, a researcher, or the news. Independent observation of your internet-facing estate is one more way of noticing first, which is the only part of the timeline you control.
Read next
- Cyber security regulations in India — the whole picture, and which sector instrument applies on top of this one.
- The RBI Directions of 31 July 2026 — the second six-hour clock, and which of the seven binds you.
- What SEBI's CDSL order says about the assets you forgot to list — what happens when an internet-facing system is not on the inventory.
Read from the CERT-In Directions themselves — No. 20(3)/2022-CERT-In of 28 April 2022, including Annexures I to III. Every instrument cited here was verified against the issuing regulator's own notification on . This page is general information, not legal advice — confirm applicability and current status with your own counsel and compliance function.
Work out your reporting deadlines
Change the inputs and the answer below changes with them.
| Instrument | What you file | Window | Goes to |
|---|---|---|---|
| CERT-In Directions, 2022No. 20(3)/2022-CERT-In | Report the incident to CERT-Inwithin 6 hours of noticing such incidents or being brought to notice about such incidents | 6 hours from noticing, or being brought to noticefrom: noticing, or being brought to notice | CERT-Inincident@cert-in.org.in · 1800-11-4949 |
| RBI Cyber Directions, 2026 — Commercial bankRBI/DoS/2026-27/410 · Ch. V, §Z.1, para 182 | Report the cyber incident on the DAKSH platformshall report cyber incidents within six hours of detection on DAKSH platformOne of seven parallel Directions issued on 31 July 2026, one per entity class. Quote this instrument and its own paragraph number — the numbering differs between them. | 6 hours from detectionfrom: detection | Reserve Bank of Indiadaksh.rbi.org.in |
| SEBI LODR, Reg. 30(6)SEBI LODR Regulations, 2015, as amended 14 July 2026 | Market disclosure of the event, if the KMP determines it is materialtwelve hours from the occurrence of the event or informationPlan on twelve hours, not twenty-four. Limb (ii)’s twelve hours is for an event emanating from within the listed entity, limb (iii)’s twenty-four for one arising outside it, and SEBI has not said which a cyber incident is. Our reading is that a ransomware event, data breach or IT outage emanates from within — the conservative choice. Materiality is the authorised KMP’s determination, not a technical one. | 12 hours from occurrence of a material eventfrom: occurrence of a material event | Stock exchanges |
| SEBI LODR, Reg. 27(2)(ba)SEBI LODR Regulations, 2015, as amended 14 July 2026 | Disclose details of the incident in the quarterly corporate governance reportDetails of cyber security incidents or breaches or loss of data or documents shall be disclosed along with the reportNo materiality test. An incident correctly judged immaterial for Reg. 30 is still reportable here — so this belongs on the post-incident checklist, not the first-24-hours one. | Next quarterly corporate governance report | Stock exchanges |
| DPDP Act, 2023 and DPDP Rules, 2025G.S.R. 846(E) · Rule 7 · G.S.R. 843(E), section 8 | Intimation to affected Data Principals, and a two-stage report to the Data Protection BoardNot in force. Rule 7 falls in the eighteen-month tranche under Rule 1(4), and section 8 commences on the same date — 13 May 2027. There is no DPDP breach clock running on an incident today. Plan and rehearse against it; do not file against it. | Not in force | Data Principals and the Data Protection Board of India |
Indicative, and not legal advice. Whether an instrument applies to a particular entity, and whether an event is a reportable incident, are determinations for your compliance and legal team. Verify every citation against the published text before a notification is filed.
Open the full tool — worked scenarios and the take-away pack →
The instrument record on this site: No. 20(3)/2022-CERT-In
Questions this page answers
- What is India’s six-hour cyber incident reporting rule?
- A requirement in the CERT-In Directions of 28 April 2022, made under section 70B(6) of the Information Technology Act, 2000. Every service provider, intermediary, data centre, body corporate and Government organisation in India must report any of twenty listed categories of cyber incident — data breaches and leaks among them — to CERT-In within six hours of noticing it or being told of it. It has applied since 27 June 2022.
- Does the full incident report have to be filed within six hours?
- No. CERT-In’s own FAQ on the Directions allows an entity to report what it knows at the six-hour mark and send the rest within a reasonable time. What cannot wait is the report itself: the clock runs from noticing the incident, not from finishing the investigation.
- Who must report incidents to CERT-In?
- Service providers, intermediaries, data centres, body corporate and Government organisations — the five classes named in the Directions. There is no revenue threshold, no sector test and no exemption for small entities. “Body corporate” reaches practically every company operating in India, which is what makes this the most widely applicable cyber instrument in the country.
- When does the six-hour clock start?
- At the moment of awareness. The Directions require reporting within six hours of noticing an incident or being brought to notice about it, so the clock does not start when the incident began, when it was confirmed, or when triage finished. Awareness arriving from a customer or a researcher starts it just the same.
- Does reporting to the RBI or SEBI satisfy CERT-In?
- No. These are separate obligations to separate recipients under separate instruments. A bank reporting an incident to the RBI on DAKSH has not thereby reported it to CERT-In, and the two six-hour clocks run concurrently rather than one instead of the other. Decide in advance who files what.
- How long must logs be kept, and where?
- Logs of all ICT systems must be enabled and kept securely for a rolling 180 days, and produced to CERT-In with an incident report or when directed. The Directions say the logs “shall be maintained within the Indian jurisdiction”; CERT-In’s own FAQ later allowed storage outside India, provided the logs can be produced to CERT-In within a reasonable time. Logs and records of financial transactions for services offered in India must stay in India. Keeping a copy in India removes the argument.
- What does non-compliance carry?
- Failure to furnish information when called for, or non-compliance with the Directions, may invite punitive action under sub-section (7) of section 70B of the IT Act, 2000, and under other laws as applicable. The Directions state this in terms and do not qualify it by entity size.