Since 2022, a CA firm that suffers a serious cyber incident has a legal duty to tell India’s national cyber agency, CERT-In, within six hours of noticing it. Few small firms know this, and fewer are set up for it. This post explains CERT-In’s six-hour rule in plain terms: who it applies to, what counts, how to report, and the two quieter duties that come with it (keeping logs and setting clocks).
This is a summary for awareness, not legal advice. Confirm how the rules apply to your firm with a legal advisor, and check cert-in.org.in for the current reporting formats and contacts.
Where the rule comes from
On 28 April 2022 CERT-In issued Directions under Section 70B(6) of the IT Act. They took effect 60 days later, on 27 June 2022, and CERT-In later extended the date to 25 September 2022 for MSMEs. Paragraph (ii) says that service providers, intermediaries, data centres, body corporates and government organisations “shall mandatorily report cyber incidents” listed in the annexure “within 6 hours of noticing such incidents or being brought to notice about such incidents”.
Does it apply to a CA firm?
CERT-In’s own FAQ on the Directions (May 2022, Q25) answers this by quoting Section 43A of the IT Act: a body corporate “means any company and includes a firm, sole proprietorship or other association of individuals engaged in commercial or professional activities”. A CA partnership or proprietorship is engaged in professional activities, so the safe reading is that the duty applies to you.
The duty is also yours alone. Asked whether reporting can be contracted out to a partner, CERT-In replied that “the obligation of reporting of cyber incident is neither transferrable nor indemnified or dispense with” (FAQ Q13). If your IT vendor notices the incident and reports it, that does not cover your own report.
What counts as a reportable incident
Annexure I of the Directions lists 20 types of incident. The ones a CA office is most likely to meet are:
- Unauthorised access of IT systems or data: someone signs in to your server who should not.
- Malicious code attacks, including ransomware, viruses and trojans.
- Data breach and data leak: client files copied out or exposed.
- Attacks on servers (database, mail, DNS) and on network devices such as routers.
- Identity theft, spoofing and phishing attacks.
- Compromise of critical systems or information, and unauthorised access to social media accounts.
FAQ Q30 narrows it a little. Incidents from the list should be reported within six hours when they are of a severe nature (such as intrusion or ransomware), when they are data breaches or data leaks, or when they are “large-scale or most frequent incidents such as intrusion into computer resource”. In practice that means a ransomware note on the server, a successful sign-in from someone who should not have one, or client data turning up where it should not be. Failed password attempts that your server turns away are the background noise of the internet; keep their logs, but they are not usually what this rule is about. Where the line falls is a judgement. If you are unsure, take advice quickly and lean towards reporting.
When the six hours start
The clock runs from when you notice the incident, or are told about it, not from when it began and not from when you are ready (FAQ Q24). A staff member calling at 8 pm to say the Tally data will not open, with odd file extensions everywhere, is the moment to write down the time.
How to report
Paragraph (ii) of the Directions names three channels:
- Email: [email protected]
- Phone (toll-free): 1800-11-4949
- Fax (toll-free): 1800-11-6969
CERT-In publishes an incident reporting form. You do not need every field filled to meet the deadline: FAQ Q30 says entities “may provide information to the extent available at the time of reporting”, with the rest sent later. You may see an “incident.cert-in.org.in” reporting portal mentioned online; that address does not exist, so use the email, phone or fax above and check CERT-In’s website for any change.
Paragraph (iii) of the Directions also asks you to name a point of contact for CERT-In. Send that person’s name, designation, firm, address, email, mobile and office phone to [email protected], and update it when it changes.
The quieter duties: logs and clocks
Keep 180 days of logs
Paragraph (iv) requires logs of all ICT systems to be kept securely for a rolling 180 days within Indian jurisdiction, and handed to CERT-In with an incident report or when asked. FAQ Q35 adds that copies may also be kept outside India, as long as you can produce them in reasonable time. FAQ Q37 says both successful and unsuccessful events should be recorded.
For a Windows server, that means the Security, System and Application logs. Windows overwrites these when they reach their size limit, which on a busy server can be days, not months. A simple approach is a daily export to separate storage that you keep for at least 180 days, for example a scheduled task that runs this PowerShell line as an administrator:
wevtutil epl Security "D:\LogArchive\Security-$(Get-Date -Format yyyy-MM-dd).evtx"
Repeat for System and Application, and make sure the folder exists and is not on the server’s own system disk alone. Our posts on Windows event logs and the recommended audit policy explain what should be in those logs in the first place.
Synchronise clocks with NIC or NPL
Paragraph (i) asks you to synchronise system clocks with the time servers of the National Informatics Centre or the National Physical Laboratory, or servers traceable to them. FAQ Q43 lists samay1.nic.in, samay2.nic.in and time.nplindia.org. On a standalone (workgroup) server, an administrator can set this with:
w32tm /config /manualpeerlist:"samay1.nic.in samay2.nic.in" /syncfromflags:manual /update
w32tm /resync
w32tm /query /status
In a domain, set it only on the domain controller that holds the PDC emulator role; the other machines take their time from the domain.
What happens if you do not comply
Section 70B(7) of the IT Act provides for imprisonment of up to one year, a fine of up to ₹1 crore, or both. The fine limit was raised from ₹1 lakh by the Jan Vishwas (Amendment of Provisions) Act 2023, with effect from 30 November 2023. Some consolidated copies of the IT Act online still show the old figure.
A second duty arrives from May 2027. Under the DPDP Act 2023 and DPDP Rules 2025, a personal data breach must be reported to the Data Protection Board and to each affected person without delay, with a detailed report to the Board within 72 hours. That runs alongside CERT-In reporting, not instead of it.
Prepare this week, not during the incident
- Name a Security Officer and a deputy. Write their mobile numbers down on paper.
- Send your point-of-contact details to [email protected].
- Save CERT-In’s contacts and the reporting form offline, with your IT vendor’s, lawyer’s and insurer’s numbers.
- Start the daily log export and set the server clock.
- Fill in the unchanging parts of a report in advance: firm name and address, contact, server names, operating system, internet provider.
- Rehearse for 30 minutes with the partners: “the server is encrypted at 9 pm on a Saturday. Who does what?”
Our free Six-Hour Rule playbook, on the security resources page, turns this into an hour-by-hour plan with a report template you can fill in today. For the wider response (contain, recover, learn), read our guide to incident response.
Where monitoring fits
The six hours start when you notice. A firm that finds out from a ransom note on Monday morning has already lost most of its choices. Prixl Warden watches the server’s event logs and emails you about serious events as they happen, such as a successful sign-in after repeated failures, a new account, the audit log being cleared or the firewall being turned off. It keeps 30 days of the security events it watches. That is not the 180 days of complete Windows log files CERT-In refers to, so keep the log export above as well.
Start your 30-day free trial and get the alerts that start your clock early, not late.
