CERT-In 6-Hour Incident Reporting: A Practical Guide for SOC Teams
CERT-In's 2022 Directions require listed cyber incidents to be reported within six hours and logs kept for 180 days. What applies, and the SOC process to meet it.

CERT-In's six-hour reporting rule has applied since 2022, yet many incident response plans still assume a day to work out what happened. Six hours leaves no time to find out who owns the decision.
This guide covers what the CERT-In Directions of 28 April 2022 require, what CERT-In's FAQs clarified, and the SOC process that gets an initial report out on time.
What the Directions Require
The Directions were issued under Section 70B(6) of the IT Act. The parts that shape a SOC are:
| Requirement | What it says |
|---|---|
| Report within 6 hours | Listed cyber incidents must be reported to CERT-In within six hours of noticing them or being told of them |
| Keep logs for 180 days | Logs of all ICT systems must be enabled and kept securely for a rolling 180 days, and provided to CERT-In with a report or on request |
| Synchronise clocks | Systems must use the NTP servers of NIC or NPL, or servers traceable to them |
| Name a point of contact | Organisations must designate a point of contact to interface with CERT-In |
They apply to service providers, intermediaries, data centres, body corporates and government organisations. CERT-In's FAQs confirm that individuals are not covered.
Data centres, VPS, cloud and VPN service providers have an extra duty to keep validated subscriber records for five years after a registration is cancelled or withdrawn. CERT-In's FAQs exclude enterprise and corporate VPNs from this.
Which Incidents Must Be Reported
The Directions list the incident types that must be reported. They include targeted scanning or probing of critical networks and systems, compromise of critical systems or information, unauthorised access to IT systems or data, data breaches, data leaks and attacks on IoT devices, alongside ransomware, phishing, denial of service and attacks on applications, servers and cloud.
The list is wider than CERT-In's earlier 2013 rules, so check your own incident categories against the current list in the Directions rather than an older run book.
What CERT-In's FAQs Clarified
CERT-In published FAQs in May 2022. Four answers change how you plan:
- The first report can be partial. You report what you know at the time and send additional information later within a reasonable time.
- Logs can sit outside India if they can be produced to CERT-In within a reasonable time.
- Clocks do not have to be set to IST. Cloud providers' native time services are acceptable, as long as they don't deviate from NIC or NPL time.
- Where several organisations are affected, the one that notices the incident is responsible for reporting it.
The Six-Hour Process, Hour by Hour
| Window | What has to happen | Who owns it |
|---|---|---|
| 0 to 1 hour | Alert triaged and confirmed as a real incident. Clock start recorded | SOC L1 and L2 |
| 1 to 3 hours | Incident mapped to a reportable category, scope estimated, evidence preserved | SOC L2 or incident lead |
| 3 to 5 hours | Reporting decision made and initial report drafted with what is known | CISO or named deputy |
| By 6 hours | Initial report sent to CERT-In by the method on its website. Time sent recorded | Point of contact |
| After | Follow-up information sent as it becomes available. Logs provided if requested | Incident lead |
Three things make or break this:
- A pre-approved decision owner. If the only person who can approve the report is the CISO and the CISO is on a flight, you miss the window. Name a deputy in writing.
- A drafted template. Keep a report template with your organisation details and point of contact filled in, so only the incident fields remain.
- Category mapping in the SIEM. Tag detection rules with the CERT-In incident type they relate to, so L1 analysts know at triage that the clock may be running.
The 180-Day Log Requirement Is a SIEM Sizing Decision
CERT-In's FAQs give examples of the logs in scope: firewall, IPS, SIEM, web, database, mail, FTP, proxy, VPN and SSH logs, event logs of critical systems and ATM switch logs, recording both successful and unsuccessful events.
Keeping all of that for a rolling 180 days is usually the expensive part. Check three things:
- Coverage. Is every system in that list actually sending logs, including database access logs that a SIEM often never sees?
- Retention. Does your SIEM licence and storage hold 180 days of searchable data, or does older data roll into an archive you have never restored?
- Future overlap. The DPDP Rules 2025 require logs of access to personal data to be kept for at least one year from 13 May 2027. If you are resizing storage for CERT-In, size for the year now. Our DPDP compliance checklist covers that requirement.
How CERT-In Fits With Other Indian Reporting Clocks
| Clock | Deadline | Applies from |
|---|---|---|
| CERT-In listed cyber incidents | 6 hours | Already in force |
| DPDP personal data breach, detailed report to the Board | 72 hours | 13 May 2027 |
Regulated entities have their own clocks on top of these. For BFSI, our CERT-In threat report analysis maps the SEBI and RBI timelines alongside them, and our guide to CERT-In's 12-hour patch window covers remediation deadlines.
Run at least one tabletop exercise timed against the six-hour clock before you need it.
FAQ
When does the CERT-In six-hour clock start?
From noticing the incident or having it brought to your notice. The Directions of 28 April 2022, issued under Section 70B(6) of the IT Act, require listed cyber incidents to be reported to CERT-In within six hours of that point.
Do we need full details within six hours?
No. CERT-In's FAQs say you can report the information available at the time, and send additional information later within a reasonable time. The six-hour deadline is for the initial report.
Which logs must be kept for 180 days?
Logs of all ICT systems, kept securely for a rolling 180 days. CERT-In's FAQs give examples including firewall, IPS, SIEM, web, database, mail, proxy, VPN and SSH logs and event logs of critical systems, covering both successful and unsuccessful events.
Must the logs be stored in India?
The Directions say within Indian jurisdiction. CERT-In's FAQs add that logs can be stored outside India as long as they can be produced to CERT-In within a reasonable time.
What is the penalty for not reporting?
Section 70B(7) of the IT Act provides for imprisonment of up to one year, a fine of up to ₹1 lakh, or both. MeitY's FAQs say the power will be used reasonably and where non-compliance is deliberate.
How does the CERT-In rule interact with DPDP breach reporting?
They are separate obligations. CERT-In's six-hour rule covers listed cyber incidents and applies today. From 13 May 2027, the DPDP Rules also require personal data breaches to be reported to the Data Protection Board and affected individuals without delay, with a detailed report to the Board within 72 hours.
Questions About Your Own Setup?
Six hours only works if someone is watching around the clock. If you want to talk through your SOC coverage or SIEM log retention, see our managed SIEM services or get in touch.
About the Author
Saurabh Pande is Co-Founder of Cyberaube Technologies with 13+ years of experience across enterprise security platforms including IBM Security, CyberArk, and QRadar. He has interviewed and placed 2,500+ cybersecurity professionals across SIEM, PAM, and IAM disciplines, and advises BFSI organizations on security operations strategy and compliance readiness.