24/7 local support available.
Guides / Business
Business

CERT-In and a hacked website: what to report and when

October 14, 2026 • 5 min read • HostBible Team

Under the CERT-In Directions of 28 April 2022, listed entities must report defined cyber incidents, including website defacement and malicious code, within 6 hours of noticing them. Whether a small business is covered is not spelled out in the Directions, so here is what the text says and how to act either way.

What does the CERT-In six-hour rule actually say?

The Directions are a document dated 28 April 2022, numbered 20(3)/2022-CERT-In, issued under section 70B(6) of the Information Technology Act, 2000. The relevant paragraph says that any service provider, intermediary, data centre, body corporate and Government organisation must report the cyber incidents listed in Annexure I to CERT-In within 6 hours of noticing them or being brought to notice about them. The clock starts when you notice, or when someone tells you, not when you finish investigating.

The same paragraph names the channels: email to incident@cert-in.org.in, phone on 1800-11-4949 and fax on 1800-11-6969. It also says the reporting methods and formats are published on the CERT-In website and may be updated. As of October 2026 the numbers above are the ones printed in the Directions, so check the CERT-In site for the current format before you rely on them in a real incident.

The Directions take effect 60 days after issue, which puts them in force from late June 2022. Failure to furnish information or to comply may invite action under section 70B(7) of the IT Act and other applicable laws, according to the text. The document does not set out a fine amount, so do not quote one.

Does a small business with a hacked website have to report?

This is the honest answer: it depends on whether you count as one of the listed entities, and the Directions do not make that easy. The duty sits on service providers, intermediaries, data centres, body corporate and Government organisations. A web host or agency is plausibly a service provider. A private limited company running its own site is a body corporate in everyday terms.

The Directions themselves do not define "body corporate", so the text does not settle how it applies to a one-person shop or a sole proprietor. Some law-firm commentary reads the scope broadly, but commentary is opinion, not the regulator, so check CERT-In's own FAQs and guidance. If you are a registered company, the cautious assumption is that you are covered. If you are unsure, ask a lawyer who handles IT law, and do it before an incident rather than during one.

Even if you decide you are outside the rule, reporting is still allowed and CERT-In exists to coordinate responses. Many owners also have a separate reason to act quickly, such as customer data exposure, which touches the DPDP Act 2023.

Which website incidents are on the Annexure I list?

Annexure I is a list of twenty incident types. The ones a typical WordPress or WooCommerce site might meet are these:

  • Defacement of a website, or intrusion into a website and unauthorised changes such as inserting malicious code or links to external websites
  • Unauthorised access of IT systems or data
  • Malicious code attacks, including viruses, bots, ransomware and cryptominers
  • Attacks on servers such as database, mail and DNS servers
  • Identity theft, spoofing and phishing attacks
  • Denial of Service and Distributed Denial of Service attacks
  • Attacks on applications such as e-governance and e-commerce
  • Data breach and data leak
  • Attacks affecting digital payment systems

What should you do in the first six hours?

Write down the time you first noticed the problem, because that is your starting point. Then contain first: change passwords for hosting, WordPress admin, database and email, and take the site offline or behind a maintenance page if it is serving malware or stealing card details. Do not wipe everything yet. Logs and the infected files are your evidence, and CERT-In asks for logs along with a report.

Next, tell your host. They can see server-side logs you cannot, and they may have their own duty to report. Then send your report to CERT-In by email with the basics: who you are, a contact person, the site and IP addresses involved, what you saw, when you noticed it and what you have done so far. A short, accurate first report is better than a polished one after the deadline. You can add detail later.

Cleaning comes after reporting. Our guides on fixing a hacked WordPress site and removing WordPress malware walk through the technical steps, and the WordPress security checklist covers prevention.

What about the 180-day log rule and Indian jurisdiction?

Another paragraph says covered entities must enable logs of all their ICT systems and keep them securely for a rolling 180 days, and that the logs must be maintained within the Indian jurisdiction. They must be provided to CERT-In with an incident report or when ordered. A separate paragraph says covered entities should synchronise system clocks to the NTP servers of the National Informatics Centre or the National Physical Laboratory, or servers traceable to them.

For a small site owner the practical question is what your host retains and where. Ask in writing what access and error logs are kept, for how long, and where they are stored, and whether you can export them. Do not assume a host keeps 180 days of logs in India unless it says so. Ask any provider in writing before relying on it. Where your data physically sits is a related but different topic, covered in our guide to data localisation in India.

This is general information, not legal advice. Confirm whether the Directions apply to you with CERT-In or a qualified professional.

How can you make the next incident easier to handle?

Most of the pain comes from not knowing what happened or when. Keep dated backups you can restore from, turn on login and change logging, and set up uptime monitoring so you notice outages and defacement quickly. Note down in advance who in your business decides to report, and keep the CERT-In contact details somewhere other than the hacked site's own email.

Basics such as SSL and DDoS protection on your hosting plan reduce the odds, but nothing removes them. The six-hour clock is easier to meet when someone already owns the job.

Related guides

Sources and further reading

Want a safer place to rebuild?

If your site was compromised and you are moving to a new host, our team handles the move to a staging copy while your current site stays live.

See free website migration