In April 2022, CERT-In, the Indian Computer Emergency Response Team, issued directions that apply to service providers, intermediaries, data centres, body corporates and government organisations. The text runs to only a few pages. Meeting it is harder, because every requirement depends on something in your IT environment working at the moment an incident happens.
This post turns the core requirements into an operational checklist: what your systems must do, what your team must know and what evidence you should be able to show a client or auditor. It is written for IT heads and founders who want to know whether they could actually comply on a bad day, not just on paper.
Quick answer: Under the April 2022 CERT-In directions, you must report specified cyber incidents to CERT-In within six hours of noticing them, keep logs of your ICT systems for a rolling 180 days within India, synchronise system clocks with NTP servers of NIC or NPL or sources traceable to them, and designate a point of contact. Each one needs working systems and a practised process.
What the directions require, in plain terms
These are the obligations that apply to most organisations, with the evidence that shows each one actually works.
| Requirement | What it means in practice | Evidence to keep |
|---|---|---|
| Six-hour reporting | Report the incident types listed in the directions within six hours of noticing them or being told about them. | Incident register with detection time, report time and a copy of each report. |
| Log retention | Enable logs on all ICT systems and keep them securely for a rolling 180 days within Indian jurisdiction. | Log source inventory, retention settings, storage location and a retrieval test. |
| Time synchronisation | Connect system clocks to NTP servers of NIC or NPL, or to servers traceable to them. | NTP settings for each type of system and drift monitoring output. |
| Point of contact | Designate a person to interface with CERT-In and share their details in the prescribed format. | Named contact, deputy and the date the details were last sent. |
| Assistance on request | Provide information or assistance when CERT-In directs you to, for incident response or prevention. | An owner and a process for handling official requests. |
Data centres, cloud, VPS and VPN service providers, and virtual asset service providers, carry extra record-keeping obligations about their customers and transactions. If your business falls into one of these groups, read those clauses separately with your legal adviser.
Requirement 1: the six-hour reporting clock
The clock starts when you notice the incident or someone brings it to your notice, not when you finish investigating. That changes how you work. You report what you know within six hours, mark what is still unknown and send updates as the investigation progresses.
The directions list the incident types to report. Among others, they include:
- Intrusion: targeted scanning or probing of critical networks or systems, compromise of critical systems or information, and unauthorised access to IT systems or data.
- Website attacks: defacement, intrusion and unauthorised changes such as inserted malicious code or links.
- Malware: malicious code attacks, including ransomware, spyware and bots.
- Infrastructure attacks: attacks on database, mail and DNS servers and on network devices such as routers, and denial of service attacks.
- Fraud and data: identity theft, spoofing and phishing, data breaches and data leaks.
- Newer platforms: attacks on cloud systems, digital payment systems, IoT devices and mobile apps.
Read the full list, the reporting format and the current reporting channels on the CERT-In website.
Checklist for the reporting workflow
- Map each listed incident type to your own systems in a one-page triage guide, so the person on duty can decide quickly.
- Decide with your legal adviser how you will treat borderline cases, such as repeated scanning of a public website, and write the decision down.
- Name who can declare an incident reportable at any hour, plus a deputy.
- Keep a pre-filled draft report with your organisation details in the incident runbook.
- Record detection time automatically in your ticketing system or incident register, so you can show when the clock started.
- Agree a short approval path. Six hours does not leave room for three levels of sign-off.
- Run a drill: start the clock at 11 p.m. on a Saturday and see whether the report would go out on time.
Requirement 2: 180 days of logs, kept in India
Most companies have logs. Few have them centralised, retained for six months and searchable when an investigator needs them. The directions also expect logs to be provided to CERT-In with an incident report or when it asks for them, so retention without retrieval does not help.
- Inventory log sources: firewalls, VPN, identity provider or domain controllers, servers, databases, web servers, email, cloud control-plane logs such as AWS CloudTrail, and admin logs of key SaaS tools.
- Check default retention: appliances and cloud services often keep logs for a shorter period by default. Check each one and forward logs to central storage.
- Keep the retained copy in India: if you use a cloud logging platform, confirm the storage region.
- Protect integrity: restrict who can delete logs, and use append-only or write-once storage where you can.
- Test retrieval: pick a date five months ago and answer a real question, such as who logged in to the accounts server that day.
- Plan storage cost: log volume grows quickly. Filter noisy events, but do not drop required sources to save space.
Requirement 3: synchronised clocks
An incident timeline is only reliable if every system agrees on the time. A firewall that runs seven minutes fast can make an attacker's login appear to happen after the data was copied. The directions require ICT system clocks to connect to the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to NTP servers traceable to them. Organisations with infrastructure in several geographies may use other accurate time sources, as long as they do not deviate from NPL and NIC.
- Point a small number of internal time servers at NIC or NPL sources, and point every other system at those internal servers.
- Include firewalls, switches, hypervisors, storage, CCTV recorders and containers, which are easy to miss.
- For cloud servers, document which time source they use and why it meets the requirement.
- Alert on drift, so a system that falls out of sync is fixed before you need its logs.
Requirement 4: a point of contact who can be reached
Treat the point of contact as a role, not a name. People go on leave, change jobs and switch phone numbers. Choose someone with enough authority to get information from IT, vendors and management quickly, name a deputy, use a monitored shared mailbox and update CERT-In whenever the details change.
Common gaps to check for
A readiness review under our CERT-In compliance service starts with checks like these. You can run them yourself first.
- Logs without search: each server keeps its own logs, but nobody can search across them.
- Vendor blind spots: the website host, ERP provider or payroll SaaS keeps logs you cannot reach, and contracts do not oblige them to share logs or notify you quickly.
- Clock drift: network devices run on their own time, so timelines become guesswork.
- Paper plans: an incident response plan exists, but nobody has practised filing a report.
- Privacy handled separately: personal data breaches also fall under the DPDP Act, which has its own notification duties to the Data Protection Board and affected people as its obligations come into force.
How EthicsComputer can help
Our CERT-In compliance and readiness service covers an applicability and gap review, log retention within India, NTP configuration, a reportable-incident SOP with an escalation matrix, playbooks and tabletop drills. It is readiness and implementation support, not a regulatory audit. If you are dealing with a live incident, our incident response team can help, and our enterprise security assessment reviews your wider security posture.
Could your team file a CERT-In report within six hours tonight?
Tell us about your systems, logging and team, and we will suggest where your readiness work should start.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.