Directions · Cyber incidents · India
CERT-In compliance: 6-hour reporting, 180-day logs and audits
CERT-In compliance means following the Directions CERT-In issued on 28 April 2022 under Section 70B(6) of the IT Act. Service providers, intermediaries, data centres, body corporates and government bodies must report 20 types of cyber incident within 6 hours, keep ICT logs in India for 180 days and sync clocks to NIC or NPL.
What you need to know about CERT-In
Who must comply with CERT-In directions?
The Directions name service providers, intermediaries, data centres, body corporates and government organisations.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What do the CERT-In directions require?
The CERT-In directions require you to report listed cyber incidents within six hours, keep 180 days of ICT logs in India, synchronise clocks to NIC or NPL, name a Point of Contact and answer CERT-In's requests.
6-hour reporting
20 incident types in Annexure I.
In QULDEX: Six-hour timers180-day logs in India
All ICT systems, kept securely.
In QULDEX: Retention evidence per systemNTP synchronisation
NIC, NPL or traceable sources.
In QULDEX: Time-source evidencePoint of Contact
Respond to CERT-In directions on time.
In QULDEX: PoC and request logSubscriber records
DC, VPS, cloud and VPN providers, 5 years.
In QULDEX: Record checksKYC records
Virtual asset providers, 5 years.
In QULDEX: Record checksWhat are the CERT-In directions and reportable incidents?
The six directions, the 20 reportable incident types (grouped) and the audit guidance. Select any one to see what it requires and how QULDEX handles it.
Showing up to 6 per group. Search, filter, or open a group to see all 16.
The six directions 7
Dir. (i)Clock synchronisationApplies to everyoneConnect to the NTP servers of NIC or NPL, or servers traceable to them, to synchronise all ICT system clocks.
In QULDEXTime-source settings are evidence per system.
- Typical evidence
- NTP configuration
- Maps to
- ISO 27001 A.8.17
Dir. (ii)Report incidents within 6 hoursApplies to everyoneReport the cyber incidents listed in Annexure I to CERT-In within 6 hours of noticing them or being told about them.
In QULDEXEvery incident starts a six-hour timer with the Annexure I type recorded.
- Typical evidence
- Incident reports
- Maps to
- ISO 27001 A.5.24–A.5.26
Dir. (iii)Point of contact and information on requestDesignate a Point of Contact for CERT-In and provide information or take action when CERT-In directs, within the time it sets.
In QULDEXThe PoC record and CERT-In requests are logged with deadlines.
- Typical evidence
- PoC registration, request log
Dir. (iv)Logs for 180 days in IndiaApplies to everyoneEnable logs of all ICT systems and keep them securely for a rolling 180 days within Indian jurisdiction.
In QULDEXLog retention and location are evidenced per system.
- Typical evidence
- Log retention settings
- Maps to
- ISO 27001 A.8.15
Dir. (v)Subscriber records (DCs, VPS, cloud, VPN)Data centres, VPS, cloud and VPN providers record validated subscriber details, IPs, purpose and ownership for 5 years.
In QULDEXRecord-keeping is a control with sample checks.
- Typical evidence
- Subscriber records
Dir. (vi)KYC for virtual asset providersVirtual asset service providers, exchanges and custodian wallets keep KYC and transaction records for 5 years.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
- Typical evidence
- KYC and transaction records
Sec. 70B(7)Penalty for non-complianceFailure to provide information or comply can attract action under Section 70B(7) of the IT Act: imprisonment up to one year, a fine up to ₹1 lakh, or both.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Reportable incidents (Annexure I) 6
Annex I (i–iii)Scanning, compromise, unauthorised accessTargeted scanning of critical systems, compromise of critical systems or information, and unauthorised access to IT systems or data.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Annex I (iv–vi)Defacement, malware, server attacksWebsite defacement or intrusion, malicious code including ransomware, and attacks on servers and network devices.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Annex I (vii–viii)Phishing and DoSIdentity theft, spoofing and phishing, and DoS or DDoS attacks.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Annex I (ix–x)Critical infrastructure and applicationsAttacks on critical infrastructure, SCADA, OT and wireless networks, and on applications such as e-governance and e-commerce.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Annex I (xi–xii)Data breach and data leakData breaches and data leaks.
In QULDEXA personal-data breach also triggers DPDP duties, tracked on the same record.
- Maps to
- DPDP Act Sec. 8(6)
Annex I (xiii–xx)IoT, payments, apps, cloud, emerging techAttacks on IoT, digital payment systems, malicious or fake mobile apps, social media accounts, cloud systems, blockchain and virtual assets, and AI and ML systems.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Audits 3
Audit 2025Comprehensive Cyber Security Audit Policy GuidelinesCERT-In's July 2025 guidelines set a national, evidence-based approach to cyber security audits by empanelled auditors.
In QULDEXAudits run in the audit workspace with evidence-based workpapers.
- Typical evidence
- Audit report
EmpanelmentCERT-In empanelled auditorsMany sector regulators require audits by CERT-In empanelled auditing organisations.
In QULDEXAuditor details and scope are recorded per audit.
- Typical evidence
- Auditor engagement
FAQsCERT-In FAQs on the DirectionsCERT-In's FAQs of May 2022 clarify scope, reporting and log questions.
In QULDEXQULDEX gives this direction an owner, evidence and a review date, and links it to the incident and log controls you already run.
Nothing matches that search.
Direction numbers follow CERT-In Directions No. 20(3)/2022-CERT-In of 28 April 2022; incident types follow its Annexure I. Summaries are QULDEX paraphrases.
How do you comply with the CERT-In directions?
Name a Point of Contact, fix log retention and time sync, and build a six-hour reporting process you have actually tested. Most organisations need 1 to 3 months.
Designate the Point of Contact
Send PoC details to CERT-In in the Annexure II format and keep them current.
Fix logging and retention
Enable logs on all ICT systems and keep 180 days within India.
Synchronise clocks
Point systems at NIC or NPL NTP servers or traceable sources.
Build six-hour reporting
Map Annexure I types to your incident categories and set up the reporting workflow.
Test it
Run a tabletop exercise to prove a report can go out within six hours.
Keep it running
Every incidentReport within 6 hoursRolling180 days of logsYearlyCyber security audit where required
Durations are QULDEX planning ranges.
Which records do the CERT-In directions need?
Keep these ready for CERT-In and for auditors.
| Record | Direction | Where it lives in QULDEX |
|---|---|---|
| Point of Contact registration | (iii), Annexure II | Evidence vault |
| Incident reports to CERT-In | (ii) | CAPA automation |
| Incident classification against Annexure I | (ii) | CAPA automation |
| Log retention evidence (180 days, in India) | (iv) | Evidence vault |
| NTP configuration | (i) | Evidence vault |
| Subscriber records (DC, VPS, cloud, VPN) | (v) | Evidence vault |
| KYC and transaction records (virtual assets) | (vi) | Evidence vault |
| Cyber security audit reports | Audit guidelines | Audit workspace |
Record names are QULDEX recommendations based on the Directions.
How long does CERT-In compliance take and what drives the effort?
Most organisations need 1 to 3 months. Log retention across many systems, especially cloud and SaaS, takes longest.
Where the time goes
Bars show the upper end of each range on one scale (3 months = full width).
What changes the effort
- Number of ICT systems: each needs logs and time sync
- Cloud and SaaS: log location and retention need checking
- Provider type: DC, cloud, VPN and VPS providers keep subscriber records
- Other regulators: RBI and SEBI add their own reporting
- Existing SOC: makes six-hour reporting realistic
How ready are you for the CERT-In directions?
Check these eight things first. Nothing you enter leaves this page.
How CERT-In maps to the RBI directions, SEBI CSCRF, DPDP and ISO 27001
CERT-In reporting is the common layer under India's sector rules: RBI and SEBI both require CERT-In notification, and a personal-data breach also triggers DPDP duties.
CERT-In vs DPDP breach reporting
| CERT-In Directions 2022 | DPDP Act 2023 | |
|---|---|---|
| What triggers it | 20 types of cyber incident | Any personal data breach |
| Report to | CERT-In | Data Protection Board and affected people |
| Deadline | 6 hours from noticing | As the DPDP Rules set |
| Applies to | Service providers, intermediaries, DCs, body corporates, government | Data Fiduciaries |
| Penalty | Up to 1 year or ₹1 lakh fine (Sec. 70B(7)) | Up to ₹200 crore for breach notification failures |
| In QULDEX | QULDEX runs one incident record that drives both reports, each with its own deadline. | |
India incident and log crosswalk
| CERT-In Directions | RBI Directions 2026 | SEBI CSCRF | ISO 27001:2022 | Shared evidence |
|---|---|---|---|---|
| (ii) 6-hour reporting | 6-hour DAKSH reporting | RS.MA | A.5.24–A.5.26 | Incident reports |
| (iv) 180-day logs | C-SOC monitoring | PR.DS, DE.CM | A.8.15 | Log retention |
| (i) NTP sync | Baseline controls | PR | A.8.17 | NTP settings |
| (iii) Point of Contact | CISO | GV.RR | 5.3 | PoC record |
| Audit guidelines | IS audit | Cyber audit | 9.2 | Audit reports |
Indicative mapping for planning, not legal advice.
How QULDEX runs CERT-In compliance from log retention to six-hour reports
QULDEX is CERT-In compliance and audit management software built from EGV Group's audit delivery, used by organisations in India, their advisors and the CERT-In empanelled auditors who test them. Pick your role to see who does what.
For companies, providers and government bodies.
- ContactRegister the PoCPoC record with update reminders
- LogsKeep 180 days in IndiaRetention evidence per system
- TimeSync clocksNTP evidence per system
- IncidentsReport within 6 hoursSix-hour timers and Annexure I types
- RequestsAnswer CERT-InRequest log with deadlines
- AuditHost the auditControlled evidence sharing
For security consultants and internal audit.
- ContactCheck registrationStatus across entities
- LogsReview coverageCoverage gaps listed
- TimeCheck sourcesExceptions listed
- IncidentsAdvise on reportingDecision record per incident
- RequestsDraft responsesResponse tracking
- AuditPrepare the packAn audit-ready pack
For CERT-In empanelled auditing organisations.
- ContactPlanScope in a standard format
- LogsSample logsView-only evidence with download control and an access log
- TimeVerifyConfiguration samples
- IncidentsReview reportingIncident history with audit trail
- RequestsReviewRequest history
- AuditAuditFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →CERT-In questions people ask
What are the CERT-In directions?
Directions issued on 28 April 2022 under Section 70B(6) of the IT Act, 2000, covering incident reporting, log retention, clock synchronisation, a Point of Contact and record-keeping for some providers. They took effect 60 days after issue.
What must be reported to CERT-In within 6 hours?
Any of the 20 incident types in Annexure I, including unauthorised access, ransomware and other malicious code, data breaches and leaks, DoS attacks, phishing, and attacks on cloud, payment, IoT or AI systems.
How long must logs be kept under the CERT-In directions?
Logs of all ICT systems must be kept securely for a rolling 180 days within Indian jurisdiction and provided to CERT-In with incident reports or on request.
Who must comply with the CERT-In directions?
Service providers, intermediaries, data centres, body corporates and government organisations. Data centre, VPS, cloud and VPN providers, and virtual asset providers, have extra record-keeping duties.
What is the penalty for not following CERT-In directions?
Action under Section 70B(7) of the IT Act: imprisonment of up to one year, a fine of up to ₹1 lakh, or both, plus other applicable laws.
Go deeper on CERT-In
References
- CERT-In Directions No. 20(3)/2022-CERT-In under Section 70B(6), 28 Apr 2022. cert-in.org.in
- CERT-In FAQs on the Directions, May 2022. cert-in.org.in
- CERT-In Comprehensive Cyber Security Audit Policy Guidelines, 25 Jul 2025. cert-in.org.in
- Information Technology Act, 2000, Section 70B. indiacode.nic.in
- Digital Personal Data Protection Act, 2023. meity.gov.in
Reviewed by
Page history
- : Page first built: the six directions, Annexure I incident types, audit guidance and readiness check
Prove you can report within six hours
Answer a short readiness check and get a gap summary across the six directions. No sales call needed to see the result.