CERT-In directions for website owners and hosting providers in India: what applies to you
TL;DR: The Indian Computer Emergency Response Team (CERT-In) issued cyber security directions on 28 April 2022 that took effect on 27 June 2022. They require covered organisations to report listed cyber incidents within six hours, to keep system logs for a rolling 180 days within India, and, for data centres, VPS, cloud and VPN providers, to keep customer registration records for five years. Most of the heavy obligations fall on providers and larger organisations, but a website owner should still keep logs, know the incident reporting route and have a response plan. This is general information, not legal advice, and you should read the official text or ask a lawyer about your own situation.
What the CERT-In directions are
CERT-In is India's national agency for responding to cyber security incidents. Under Section 70B of the Information Technology Act, it can issue directions to service providers, intermediaries, data centres, companies and government bodies. The directions dated 28 April 2022 (No. 20(3)/2022-CERT-In) set rules on reporting incidents and keeping records, and they came into force 60 days later, on 27 June 2022.
They have been discussed mainly for their effect on VPN, cloud and data centre companies. If you run a website on Indian hosting, they affect you indirectly through your provider and directly if your business falls into a covered category.
Who they apply to
The directions address several groups:
- Service providers, intermediaries, data centres, body corporates and government organisations, who must report listed incidents.
- Data centres, VPS providers, cloud service providers and VPN providers, who must register and keep customer information.
- Virtual asset service providers and similar entities, who have record-keeping duties for transactions.
A small business with a website is generally a "body corporate", but how far each duty reaches depends on the wording and your circumstances. Do not assume you are exempt, and do not assume you carry every duty meant for a data centre. When in doubt, read the official text and take professional advice.
The key requirements
| Requirement | What it says | Who it mainly concerns |
|---|---|---|
| Incident reporting | Report listed cyber incidents to CERT-In within 6 hours of becoming aware or being notified | Covered organisations broadly |
| Log retention | Keep logs of ICT systems securely for a rolling 180 days, within Indian jurisdiction, and provide them to CERT-In on request | Covered organisations broadly |
| Customer records | Data centres, VPS, cloud and VPN providers register and keep subscriber information for 5 years after cancellation | Providers |
| Clock synchronisation | Summaries of the directions also describe synchronising system clocks with designated time servers. Check the official text for the exact wording | Covered organisations |
| Providing information | Respond to CERT-In requests for information and assistance | All covered |
The figures above, six hours, 180 days and five years, are the ones to remember. Always confirm current wording and any later clarifications, such as official FAQs, on CERT-In's own website.
What counts as a reportable incident
The directions include a list of incident types. It covers, among others:
- data breaches and data leaks,
- unauthorised access to IT systems or data,
- compromise of critical systems or information,
- targeted scanning or probing of critical networks or systems,
- phishing attacks,
- website defacement or intrusion, and
- unauthorised changes to a website, such as inserting malicious code or links.
For a website owner, the last two are the relevant ones. If your site is defaced or someone injects malicious code into it, that is exactly the sort of event the directions describe. Our guides on the first hour after a WordPress hack and on cleaning a hacked site explain how to respond technically.
What this means if you run a website
The directions do not turn every blogger into a regulated entity, but sensible practice lines up with them.
- Keep logs. Make sure access logs, error logs and, where available, application and security logs exist and are kept. If your host rotates logs after a few days, arrange to store copies for longer. A rolling 180 days is the figure to aim for, within India where the rules apply to you.
- Know how to detect an incident. Use malware scanning, file-change monitoring and alerts. See malware scanning tools for WordPress and server monitoring beyond uptime.
- Write down who reports. Decide in advance who in your business is responsible for reporting, how to reach CERT-In through its official channel, and what information to include. A six-hour clock leaves no time to work it out during an attack.
- Time-stamp consistently. Make sure your servers keep accurate time, because logs with wrong clocks are hard to use.
- Back up and test restores. Recovery speed matters. See how to back up and test a restore.
- Keep plugins, themes and PHP patched, because most website incidents come from known flaws. See the PHP2Shell guide for a recent example.
What this means for hosting providers
A hosting company that runs data centres, VPS or cloud services has the heaviest load: registering and keeping customer information, retaining logs inside India and reporting incidents on its own infrastructure within six hours. As a customer you may be asked for accurate registration details, such as a valid identity and contact information, because the provider must keep them. Providing them accurately helps you, because inaccurate details can delay support and, in some cases, lead to suspension.
Providers also need a process to notify you when something affects your account, and you should know how to reach them quickly. Our guide to choosing web hosting in India and the post on cloud hosting providers in India list support and data-location questions worth asking.
What to ask your hosting provider
- Where are my server, backups and logs stored? Are they in India?
- How long are access and security logs kept, and can I get copies?
- How will you notify me if my account is affected by an incident?
- What is your process for reporting incidents to CERT-In, and what do you need from me?
- What registration information do you keep about me, and for how long?
- Do you provide malware scanning, firewall logs and file integrity monitoring?
A provider that answers these clearly has probably thought about them.
A simple readiness checklist
- Log retention set to at least 180 days, with copies off the server
- Server clocks synchronised and set to the correct time zone
- Malware scanning and alerts in place
- Backups tested, with a restore plan
- Named person for incident reporting, with the official contact route saved
- Incident response checklist written and shared
- Hosting provider's data location and support process confirmed
- Registration details with your host accurate and current
- Plugins, themes, PHP and server software kept patched
Run through this once a quarter.
How CERT-In relates to the DPDP Act
CERT-In's directions are about cyber security incidents and records. The Digital Personal Data Protection Act is about how you collect and handle personal data, including a duty to protect it and to report personal data breaches. The two overlap when an incident exposes personal data: you may have reporting duties under both. For the data protection side, read our guide on the DPDP Act and your hosting obligations, and DPDP cookie consent for WordPress.
Penalties
Failing to comply with a direction under Section 70B can attract penalties under the IT Act, including imprisonment of up to one year, a fine of up to ₹1,00,000, or both, according to legal summaries of the provisions. Other laws may apply as well. Because the consequences are serious, treat the directions as something to read in the original, and take legal advice where your business is clearly covered.
FAQs
What are the CERT-In directions of 2022?
Cyber security directions issued on 28 April 2022 requiring covered organisations to report incidents within six hours, retain logs for 180 days and, for certain providers, keep customer records for five years. They took effect on 27 June 2022.
Do small websites have to report incidents to CERT-In?
The reporting duty applies to covered entities, which can include body corporates. Whether it applies to your site depends on your circumstances, so check the official text and consider legal advice.
What is the 6-hour reporting rule?
Covered organisations must report listed cyber incidents to CERT-In within six hours of becoming aware of them or being notified.
How long must logs be kept?
For a rolling 180 days, securely, within Indian jurisdiction, and available to CERT-In on request.
Does my hosting provider handle this for me?
Providers handle their own obligations, such as customer records and infrastructure logs. You are still responsible for your own application, content and business-level duties.
Is a defaced or hacked website a reportable incident?
Website defacement, intrusion and unauthorised changes such as injected malicious code are on the list of incident types in the directions.
Where can I read the official directions?
On CERT-In's official website, which publishes the directions and related FAQs. Always rely on the official text.
Is this legal advice?
No. This post is general information. Ask a qualified lawyer about your own obligations.
Conclusion
The CERT-In directions put clear numbers on incident response: six hours to report, 180 days of logs and five years of customer records for certain providers. If you run a website in India, the practical response is straightforward: keep logs, monitor for incidents, write down who reports and how, back up and patch. Then confirm with your host where your data and logs live.
HostCloud supports Indian websites with hosting built around local data and responsive support. See the options at https://hostcloud.in.
Sources: