Scroll to top

CERT-In Compliance

  • Home
  • CERT-In Compliance

"6 hours to report. 180 days in India. Criminal liability for non-compliance."

CERT-In Compliance Incident Reporting

The 6-hour CERT-In reporting window starts at first detection — not when you finish your incident assessment. Automated detection and pre-approved templates are essential.

CERT-In Directive 2022 — Automated Compliance Before the 6-Hour Clock Starts

The CERT-In directive (April 2022) requires: reporting 20 categories of cyber incidents within 6 hours of detection; maintaining ICT system logs for 180 days within Indian jurisdiction; synchronizing all system clocks with NTP servers traceable to India's NPL; and maintaining verifiable user identities across all ICT systems. Non-compliance is a criminal offence under Section 70B(7) of the IT Act 2000 — punishable by up to one year imprisonment. VinfraSec implements all four requirements as automated, IaC-enforced controls.

Key Capabilities

20-Category Incident Detection & CERT-In Reporting

SIEM-based automated detection for all 20 CERT-In incident categories — ransomware, data breaches, unauthorized access, DoS, SCADA attacks, and more — with pre-approved reporting templates ready before an incident occurs.

180-Day Log Retention in India (Immutable WORM)

Centralized log aggregation with Azure Log Analytics (Central India / South India) or AWS CloudWatch + S3 Object Lock (Mumbai). Immutable retention enforced by IaC policy — logs cannot be deleted or modified before the 180-day period expires.

NTP Synchronization with NIC Servers

All servers, VMs, containers, network devices, and workstations synchronized with NIC's NTP servers (time.nic.in) via Terraform and Ansible. Drift alerts notify when any device falls out of sync — protecting log correlation integrity.

ICT Audit Trail Engineering

Complete audit logging for all privileged actions, authentication events, API calls, and data access — timestamped, tamper-evident, and searchable. Evidence packages ready for CERT-In in hours, not days.

Verifiable System Identity

Every user, system, and service has a traceable identity — IAM roles, managed identities, certificate-based authentication. No anonymous accounts. VPN users are logged with their real identity even through NAT.

6-Hour Data Response Capability

Pre-authorized CERT-In data response procedures with designated responders, evidence collection runbooks, and escalation protocols — so your organization can respond to CERT-In data requests within the required 6-hour window.

Why the 6-Hour Clock Cannot Be Managed Manually

The 6-hour CERT-In reporting window starts at the moment of first detection — not when you finish your incident assessment. VinfraSec implements SIEM-based automated detection with pre-approved reporting templates, so the 6-hour clock is met even at 3am during a ransomware incident.

Non-compliance is a criminal offence under Section 70B(7) of the IT Act 2000 — with imprisonment up to one year for responsible officers. The more significant business risk is reputational damage and prolonged regulatory scrutiny from a CERT-In investigation.

Free Consultation

Common questions

Answers checked against the rules in force in October 2026. For the full picture, read The CERT-In Directions explained.

What incidents must be reported to CERT-In within 6 hours?

Any of the 20 incident types in Annexure I of the CERT-In Directions of 28 April 2022, reported within 6 hours of noticing the incident or being told about it. They include targeted scanning or probing of critical networks, compromise of critical systems, unauthorised access to IT systems, website defacement, malware and ransomware, identity theft, spoofing and phishing, DDoS attacks, data breaches and data leaks, and attacks on IoT, cloud, and AI or machine-learning systems.

What log retention do the CERT-In Directions require?

ICT system logs must be kept securely for a rolling 180 days within Indian jurisdiction, and provided to CERT-In when it asks for them.

Who must comply with the CERT-In Directions, and who has extra duties?

Service providers, intermediaries, data centres, body corporates and government organisations. Data centres, VPS providers, cloud service providers and VPN service providers must also keep validated subscriber records for 5 years, and virtual asset service providers, exchanges and custodian wallet providers must keep KYC and transaction records for 5 years.

Which time source do the CERT-In Directions require?

System clocks must be synchronised to the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to NTP servers traceable to them.

What is the penalty for not complying with the CERT-In Directions?

Not complying with the CERT-In Directions can be prosecuted under Section 70B(7) of the IT Act. The penalty is imprisonment of up to one year, a fine of up to ₹1 lakh, or both.

Ready to Automate Your CERT-In Compliance?

We'll assess your incident reporting capability, log retention architecture, NTP configuration, and ICT audit trail against CERT-In directive requirements and deliver a prioritized gap report — at no charge.