Discuss the role and limitations of CERT-In in ensuring the resilience of India's digital public and private infrastructure.
New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →In this answer
The Indian Computer Emergency Response Team (CERT-In) is India's nodal agency for cyber incidents. Its directions of 28 April 2022 were issued under Section 70B(6) of the IT Act, 2000 [1]. CERT-In is strong at responding to attacks. Resilience, however, also means keeping services running when systems fail without any attack, and that is where its mandate falls short.
Role of CERT-In
- Mandatory 6-hour reporting: service providers, intermediaries, data centres, body corporates and government organisations must report listed cyber incidents within 6 hours [1].
- Wide coverage: the duty extends to cloud, VPN and data-centre providers, so both public and private networks fall within its reach [1][2].
- Forensic readiness: ICT logs must be kept for a rolling 180 days within India [1].
- Enforcement: non-compliance can lead to penal action under Section 70B(7) [1].
Limitations
- Built around security, not reliability: the directions cover attacks and intrusions but not outages caused by technical faults [3].
- The November 2026 Microsoft 365 outage: a fault in a network-capacity upgrade disrupted IndiGo and Akasa Air customer support, and Air India had to reroute its email. None of this had to be reported [3].
- Fragmented rules: three sets of rules may apply to outages, and each has a gap [3].
- Accountability asymmetry: providers serving lakhs of Indian users explained the cause only in general terms, through a voluntary apology [3].
- No continuity mandate: CERT-In responds to incidents. Unlike RBI, it cannot require firms to keep a tested business continuity and disaster recovery (BCP/DR) plan [4].
- Wrong tool for faults: a 6-hour window designed for threats that can spread would flood CERT-In with routine glitches.
Way Forward
- Digital India Act: add a separate duty to report large outages, triggered by a minimum size of outage and followed by a root-cause report.
- Sector regulators: copy RBI's requirement of tested BCP/DR plans for outsourced IT and cloud services [4], starting with aviation.
- Reduce concentration risk: large buyers should keep a second vendor or fallback route for critical functions.
CERT-In has made reporting and preparing for cyberattacks mandatory, but resilience against technical failures is still left to voluntary disclosure. Splitting the work sensibly would close the gap: CERT-In handles attacks, sector regulators enforce continuity planning, and a new law requires reporting of large outages. That would protect trusted, resilient digital infrastructure in line with the Digital India vision.
Sources
- 1CERT-In Directions under Section 70B(6) of the IT Act, 2000 (No. 20(3)/2022-CERT-In, 28 April 2022): 6-hour reporting, covered entities including cloud and VPN providers, 180-day log retention in India, penalties under Section 70B(7)
- 2PIB: CERT-In issues directions relating to information security practices and reporting of cyber incidents (28 April 2022): scope across public and private entities
- 3The Hindu: "How does India address service outages?" (17 Nov 2026, explainer): technical-fault outages excluded from the directions, three rule-sets each with a gap, Microsoft 365 outage and its effect on airlines, voluntary apology
- 4RBI (Outsourcing of Information Technology Services) Directions, 2023: BCP/DR requirements for outsourced IT, including cloud