In April 2022, the Indian Computer Emergency Response Team (CERT-In) issued directions under section 70B of the IT Act that changed incident response in India. The best-known requirement: specified cyber incidents must be reported to CERT-In within six hours of noticing them. Few jurisdictions have a shorter clock.
Who it applies to
The directions apply broadly: service providers, intermediaries, data centres, body corporates and government organisations. In practice, most companies operating systems in India should assume they are in scope. Some requirements apply only to specific providers, such as VPN, cloud and data centre operators.
The key requirements
- Report within six hours. Incidents of the types listed in the directions must be reported to CERT-In within six hours of being noticed, or of being brought to your attention.
- Point of contact. Designate a point of contact to liaise with CERT-In and register their details.
- Clock synchronisation. Synchronise system clocks with the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or with servers traceable to them.
- Logs for 180 days. Enable logs of all ICT systems and keep them securely for a rolling 180 days within India, available to CERT-In on request.
- Provider-specific records. Data centres, VPS, cloud and VPN providers must keep certain subscriber information for five years. Virtual asset providers have KYC and transaction-record duties.
Reportable incidents
The directions list incident types including:
- targeted scanning or probing of critical networks and systems;
- compromise of critical systems or information;
- unauthorised access to IT systems or data;
- website defacement, or intrusions such as malicious code injection;
- malicious code attacks, including ransomware and cryptomining;
- attacks on servers (database, mail, DNS) and network devices;
- identity theft, spoofing and phishing attacks;
- denial-of-service attacks;
- attacks on critical infrastructure, SCADA and operational technology;
- data breaches and data leaks;
- attacks on IoT devices, and on applications such as e-governance, e-commerce and digital payments;
- attacks or malicious activity affecting cloud, big data, blockchain, robotics, 3D printing, drones, and AI or ML systems;
- fake mobile apps.
The list is wide. When in doubt, report. An initial report can be brief and updated later.
Readiness checklist
People and process
- Named CERT-In point of contact, plus a deputy, registered and reachable around the clock.
- Incident triage that checks reportability early, as part of the first hour, not after the investigation.
- A pre-filled report template with company details, contacts and systems.
- Authority to report delegated to the security lead, so it doesn't wait for leadership sign-off.
- A combined view of the other clocks you may face: DPDP breach notification, sector regulators (RBI, SEBI, IRDAI) and contractual notices to customers.
Technology
- All servers, network devices and cloud services synced to NIC or NPL time sources (or traceable ones).
- Centralised logging covering ICT systems, with 180 days retained in India and protected from tampering.
- Alerting that surfaces reportable events quickly, such as ransomware indicators, mass data access and defacement.
- Evidence that logging works: test retrieval of a log from 170 days ago.
Aligning with other regimes
Under India's DPDP Rules, a personal data breach must be reported to the Data Protection Board without delay, with a detailed report within 72 hours. A ransomware attack on a customer database can trigger both CERT-In (six hours) and the DPDP Act. Build one incident workflow with several reporting outputs. See our 72-hour DPDP breach playbook.
Practise it
The six-hour clock is only manageable if people have done it before. Include CERT-In reporting in every tabletop exercise, and time how long it takes to produce the first report.
Learn more
Incident management and regulatory reporting are covered in our free CISM track. For a full readiness list, see our ransomware readiness checklist.
Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.
General information, not legal advice. Laws and official guidance change; check the current text before acting.