·The Hindu·15 marks·250–350 words

Should cloud service providers that serve governments and hospitals be regulated as critical infrastructure? Critically analyse.

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
  1. Case for CII designation
  2. Concerns and limits
  3. Way forward

Section 70 of the IT Act, 2000 defines Critical Information Infrastructure (CII) as any computer resource whose incapacitation would have a debilitating impact on national security, the economy, public health or safety [1]. The recent global Microsoft 365 outage stopped governments and hospitals at the same moment. Cloud providers now meet this test in practice, which argues for targeted, not blanket, regulation.

Case for CII designation

  • Systemic risk: a single faulty upgrade at one provider takes down thousands of users at once. The World Bank warns that relying on one or a few providers raises vulnerability across a whole sector [2].
  • Public-service continuity: hospital records, emergency communication and e-governance files sit on private servers, so a vendor outage becomes a public-health failure.
  • Regulatory precedent: RBI's 2025 outsourcing Directions already cover cloud computing services [3] and require an exit strategy [4]. Hospitals and ministries have no such duty.
  • Cyber spillover: CERT-In warned that the 2024 CrowdStrike-linked outage was being used for phishing [5]. An operational failure can open the door to an attack.

Concerns and limits

  • Affordability: shared cloud keeps enterprise software cheap. Heavy compliance could burden small hospitals and municipalities.
  • Jurisdiction: hyperscalers are headquartered abroad and run global architectures, so Indian rules are hard to enforce.
  • Misplaced focus: NCIIPC places the basic responsibility for protecting CII on the agency running it [6]. The user's resilience matters as much as the vendor's.
  • False comfort: if every institution's backup is another of the same few providers, firm-level rules leave market concentration untouched [2].

Way forward

  • Designate critical public workloads (hospitals, emergency services, key ministries) as CII, rather than whole providers.
  • Write exit plans, tested offline fallbacks and pre-named backup channels into public cloud contracts, following RBI's model [4].
  • Require providers to report major outages to CERT-In, which should issue anti-phishing alerts as soon as an outage begins [5].
  • Have CERT-In, NCIIPC and RBI jointly map provider concentration across critical sectors [2].

Cloud concentration brings efficiency, but it can turn one vendor's error into a national disruption. A calibrated CII regime based on workloads, combining provider accountability with resilience on the user's side, would keep cloud services affordable. It would also protect the right to health and good governance, in line with SDG 9's goal of resilient infrastructure.

Sources

  1. 1Information Technology Act, 2000, Section 70 (India Code): statutory definition of Critical Information Infrastructure
  2. 2World Bank Digital Finance: Monitoring system-level concentration and interconnectedness (Outsourcing): reliance on a few providers raises systemic risk; supervisors should assess concentration across the system
  3. 3RBI (All India Financial Institutions – Managing Risks in Outsourcing) Directions, 2025: cloud computing services covered as outsourced IT services
  4. 4RBI (Payments Banks – Managing Risks in Outsourcing) Directions, 2025: exit-strategy and cloud-usage provisions
  5. 5CERT-In Current Activity CICA-2024-3308: Phishing campaign targeting CrowdStrike users: global outage exploited for phishing
  6. 6National Critical Information Infrastructure Protection Centre (NCIIPC): nodal agency under Section 70A; basic responsibility for protecting CII lies with the agency running it

More from this note