Module 3 · CERT-In 2022 Directions — The 6-Hour Reporting Reality

Manish Garg
Manish Garg Associate of (ISC)² · RingSafe
May 14, 2026
5 min read
Read as
100% Free

No signup. No paywall. No catch. One of our 10 most-requested practitioner modules — published in full so anyone can learn for free. We earn through consulting, not by gating knowledge.

See all 10 free modules →

Why this module exists. CERT-In’s April 2022 Directions (under Section 70B of the IT Act) imposed novel and operationally significant obligations on Indian entities — including the 6-hour incident reporting rule, mandatory log retention, KYC for VPN providers, and incident-reporting cooperation. This module is the practitioner-level operational guide.

Why this module exists. Three years on, most Indian enterprises are still uncertain about which CERT-In Directions apply to them, what counts as a reportable incident, and what the reporting workflow looks like. This module is the operational answer.

What the Directions actually require

  1. Time synchronisation to NTP servers run by NIC or NPL (or NTP servers traceable to those). Network logs must use this synchronised time.
  2. Incident reporting to CERT-In within 6 hours of noticing or being notified about a cyber incident.
  3. Log retention for 180 days rolling, for systems in Indian jurisdiction. Logs must be enabled and retained for the listed system types.
  4. KYC for VPN, virtual private server, cloud, crypto-exchange providers (the controversial provision; mostly affected providers, not enterprise users).
  5. Designated Point of Contact registered with CERT-In, with name, designation, email, phone.
  6. Cooperate with CERT-In for incident response — provide logs, system access, support analysis.
DPDP Act in your stack?

Get a DPDP gap assessment

Free 30-minute call. We map your data flows against DPDP §8 obligations and tell you exactly which gaps to fix first. Auditor-defensible output.

Book DPDP scoping call Replies in 4 working hrs · India-only · Senior consultants