Mecverse Logo
Book demo
India IT rules

CERT-In 6-hour cyber incident reporting rules

Since June 2022, any Indian organisation that runs computers for its business must report specified cyber incidents to CERT-In within 6 hours of noticing them. CERT-In treats a company, firm or sole proprietorship as a 'body corporate', so this includes a small office. The duty comes from CERT-In's Directions of 28 April 2022 under section 70B(6) of the IT Act. Twenty incident types are listed, from phishing and ransomware to data leaks and hacked social-media accounts. Individual citizens are not covered.

The 6-hour clock starts when you notice the incident or someone tells you about it. You can report with incomplete information and send the rest later. Email incident@cert-in.org.in (phone 1800-11-4949). CERT-In's form is optional. Your duty to report cannot be passed to an IT vendor by contract, and an NDA does not stop you reporting.

Two technical rules apply to everyone covered. Keep logs of all ICT systems for a rolling 180 days within Indian jurisdiction, and synchronise system clocks to the NIC or NPL time servers or to a source traceable to them. You must also name a Point of Contact for CERT-In. Data centres, VPS, cloud and public VPN providers must additionally keep validated subscriber records for 5 years.

Ignoring a direction under section 70B(7) can mean imprisonment up to one year, a fine up to ₹1 crore (raised from ₹1 lakh by the Jan Vishwas Act from 30 November 2023), or both. CERT-In says it will use this power reasonably, where non-compliance is deliberate. MSMEs had until 25 September 2022 to comply. As of 16 November 2026, CERT-In has not amended or replaced the Directions.

General information from the primary sources linked below, not legal or tax advice. Check your own situation with a lawyer or chartered accountant.

The rules, with sources

The law

Directions No. 20(3)/2022-CERT-In dated 28 April 2022 under sub-section (6) of section 70B of the Information Technology Act, 2000, relating to information security practices, procedure, prevention, response and reporting of cyber incidents for Safe & Trusted Internet; read with the Information Technology (The Indian Computer Emergency Response Team and Manner of Performing Functions and Duties) Rules, 2013, CERT-In's FAQs (May 2022) and CERT-In's extension notice dated 27 June 2022

Effective date

60 days after issue on 28 April 2022, so late June 2022. MSMEs got until 25 September 2022. Data centres, VPS, cloud and VPN providers also had until 25 September 2022 for the 'validated name' and 'validated address and contact numbers' parts of the subscriber register.

Sources disagree: The Directions say only 'effective after 60 days from the date on which it is issued'; no calendar date is printed. 28 April + 60 days gives 27 June 2022. Most secondary sources say 28 June 2022, and the 27 June 2022 extension notice still describes the Directions as 'to become effective', which fits 28 June. Publish it as 'late June 2022 (60 days after 28 April 2022)' rather than picking one day.

Reporting deadline

Within 6 hours of noticing an incident, or of someone bringing it to your notice

When the 6-hour clock starts

When you notice the incident or someone tells you about it, not when it happened. CERT-In says an incident that went undetected for a long time is still reportable within 6 hours of noticing it.

Partial reports are allowed

Send what you know within 6 hours and follow up with the rest 'within reasonable time'

Who must comply

Service providers, intermediaries, data centres, body corporates and government organisations. Individual citizens are not covered.

Does a small firm or sole proprietor count as a 'body corporate'?

Yes. CERT-In uses the s.43A IT Act definition, which covers any company, firm, sole proprietorship or other association of individuals in commercial or professional activity.

Number of reportable incident types

20 types are listed in Annexure I (items i–xx). They cover scanning or probing, system compromise, unauthorised access, website defacement, malware including ransomware, server and DNS attacks, phishing and identity theft, DoS/DDoS, attacks on critical infrastructure and OT, application attacks, data breach, data leak, IoT, digital payments, malicious or fake mobile apps, social-media account takeover, cloud, emerging tech (Big Data, blockchain, drones and similar) and AI/ML.

How to report

Email incident@cert-in.org.in, phone 1800-11-4949 or fax 1800-11-6969. CERT-In's incident form is optional: you can put the details in the email itself.

Incident reporting form

CERT-In publishes a one-page form (certinirform.pdf). Using it is optional, and the reporter can be the affected entity or someone reporting on its behalf.

ICT log retention

Logs of all ICT systems must be enabled and kept securely for a rolling 180 days within Indian jurisdiction, and handed to CERT-In with an incident report or on order

Sources disagree: FAQ Q35 softens 'within Indian jurisdiction': 'The logs may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time.' FAQ Q36, however, says service providers offering services to users in India must maintain logs 'in Indian jurisdiction'. The binding text is the Direction; the FAQ calls itself 'not a legal document'.

Which logs

Examples CERT-In gives: firewall, IPS, SIEM, web, database, mail, FTP and proxy server logs, event logs of critical systems, application logs, SSH and VPN logs. Record both successful and unsuccessful events.

Clock synchronisation (NTP)

Sync all ICT system clocks to NIC or NPL NTP servers, or to NTP servers traceable to them. CERT-In lists samay1.nic.in, samay2.nic.in and time.nplindia.org. Clocks do not have to be set to IST.

Cloud users and NTP

Customers may keep using their cloud provider's native time service. If you run your own NTP server, its source must not deviate from NPL/NIC.

Point of Contact

Every covered entity must designate a Point of Contact and send their name, designation, organisation, address, email, mobile, office phone and fax to info@cert-in.org.in (Annexure II format), and keep it updated

Subscriber records for data centres, VPS, cloud and VPN providers

Keep validated customer names, hire period, IPs allotted, email/IP/timestamp at registration, purpose, validated address and contact numbers, and ownership pattern for 5 years or longer after the registration is cancelled or withdrawn

Corporate VPNs

The VPN subscriber-record rule does not apply to enterprise or corporate VPNs. It covers providers of 'Internet proxy like services' to the general public.

Virtual asset (crypto) providers

VASPs, virtual asset exchanges and custodian wallet providers must keep KYC and transaction records for 5 years

Penalty

Section 70B(7) IT Act: imprisonment up to 1 year, or a fine up to ₹1 crore, or both, for failing to provide information or comply. The fine cap was ₹1 lakh until the Jan Vishwas (Amendment of Provisions) Act, 2023 substituted 'one crore' for 'one lakh', in force from 30 November 2023. CERT-In's FAQ says the power will be used 'reasonably', when non-compliance is deliberate.

Sources disagree: CERT-In's May 2022 FAQ still quotes a fine of up to 'one lakh rupees'. That text predates the Jan Vishwas Act, 2023, which raised the cap to ₹1 crore from 30 November 2023.

Outsourced or vendor incidents

Whoever notices the incident must report it. The obligation cannot be shifted to a vendor by contract.

NDAs do not block reporting

The statutory reporting duty overrides contractual confidentiality clauses (s.81 IT Act)

Amendments through November 2026

None found. CERT-In's Directions page (footer: 'Last Updated On November 16, 2026') still lists only three documents: the 28 April 2022 Directions, the May 2022 FAQs and the 27 June 2022 extension.

Related voluntary guidance for MSMEs

CERT-In's '15 Elemental Cyber Defense Controls for MSMEs' (Version 1.0 dated 01.09.2025) contains 15 controls and 45 recommendations. It suggests a yearly baseline audit by a CERT-In empanelled auditor. Its wording is permissive ('may'); it is not a direction.

Not verified

  • Exact calendar effective date (27 vs 28 June 2022). The Directions give only '60 days'.
  • Whether CERT-In now runs an online incident-reporting portal in addition to email, phone and fax (the Directions and FAQ name only email, phone and fax)
  • Any reported prosecution or penalty actually imposed under s.70B(7) for breaching the 2022 Directions
  • Whether the NIC/NPL NTP hostnames listed in the May 2022 FAQ (samay1.nic.in, samay2.nic.in, time.nplindia.org) are still the current ones

Verified against the linked sources on 16 November 2026.

At a glance

The 20 incident types that must be reported to CERT-In within 6 hours (Annexure I to the 28 April 2022 Directions)
#Incident type (verbatim)Plain-English categorySource
iTargeted scanning/probing of critical networks/systemsNetwork/system intrusionCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
iiCompromise of critical systems/informationNetwork/system intrusionCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
iiiUnauthorised access of IT systems/dataUnauthorised accessCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
ivDefacement of website or intrusion into a website and unauthorised changes such as inserting malicious code, links to external websites etc.Website attackCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
vMalicious code attacks such as spreading of virus/worm/Trojan/Bots/Spyware/Ransomware/CryptominersMalwareCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
viAttack on servers such as Database, Mail and DNS and network devices such as RoutersServer/network-device attackCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
viiIdentity Theft, spoofing and phishing attacksIdentity/phishingCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
viiiDenial of Service (DoS) and Distributed Denial of Service (DDoS) attacksAvailability (DoS/DDoS)CERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
ixAttacks on Critical infrastructure, SCADA and operational technology systems and Wireless networksCritical infrastructure/OT/wirelessCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xAttacks on Application such as E-Governance, E-Commerce etc.Application attackCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xiData BreachData breach/leakCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xiiData LeakData breach/leakCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xiiiAttacks on Internet of Things (IoT) devices and associated systems, networks, software, serversIoTCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xivAttacks or incident affecting Digital Payment systemsPaymentsCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xvAttacks through Malicious mobile AppsMobile appsCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xviFake mobile AppsMobile appsCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xviiUnauthorised access to social media accountsSocial mediaCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xviiiAttacks or malicious/ suspicious activities affecting Cloud computing systems/servers/software/applicationsCloudCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xixAttacks or malicious/suspicious activities affecting systems/ servers/ networks/ software/ applications related to Big Data, Block chain, virtual assets, virtual asset exchanges, custodian wallets, Robotics, 3D and 4D Printing, additive manufacturing, DronesEmerging techCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)
xxAttacks or malicious/ suspicious activities affecting systems/ servers/software/ applications related to Artificial Intelligence and Machine LearningAI/MLCERT-In Directions No. 20(3)/2022-CERT-In dated 28.04.2022 (PDF)

Checklist for a small business

  • Name a CERT-In Point of Contact and email their details (name, designation, organisation, address, email, mobile, office phone) to info@cert-in.org.in in the Annexure II format; update it when the person changes.
  • Write a one-page incident runbook. Name who decides 'is this one of the 20 types?', who sends the email to incident@cert-in.org.in, and the 6-hour deadline counted from when you notice the incident.
  • Save CERT-In's incident form (certinirform.pdf) and the 20-item list where on-call staff can find them. A partial report within 6 hours is acceptable.
  • Turn on logging for firewall, VPN, mail, web/app servers, Active Directory/endpoint and cloud consoles, and keep at least 180 days on a rolling basis, stored so it can be produced from India.
  • Point every server, firewall, NAS and domain controller at samay1.nic.in / samay2.nic.in / time.nplindia.org (or a cloud-native time service). Record the time zone in logs.
  • Add a clause to IT vendor and AMC contracts requiring them to tell you immediately about any incident they notice on your systems. Each party that notices an incident must report it, and the obligation cannot be contracted away.
  • If you resell hosting, VPS or cloud, keep validated customer identity, IP allocation and contact records for 5 years after the account ends.
  • Optionally, benchmark against CERT-In's 15 Elemental Cyber Defense Controls for MSMEs (Sept 2025) and consider an annual baseline audit by a CERT-In empanelled auditor.

Common mistakes

Want a second pair of eyes on your office machines?

Mecverse's IT AMC in Lucknow covers laptops, desktops and printers with quarterly preventive visits and unlimited remote software support, and starts with a free written inspection of each machine. Reporting to CERT-In stays your duty, whoever maintains your systems.

See IT AMC plans →

Common questions