makautnotes

1.6 Cyber Security of Critical Infrastructure☆

Not asked yet⏱ 4 min

When the Lights Go Out


Critical Infrastructure

Critical infrastructure is the set of systems and assets so vital that their failure would seriously harm national security, the economy, public health or safety. Critical information infrastructure (CII) is the computer systems that run them.

CII and protected systems in the IT Act

SCADA and ICS

Sectors

Why they are targeted

  1. Huge impact: one attack can hurt millions of people at once.
  2. Old systems: many SCADA systems were built decades ago, without security.
  3. Now connected: once isolated, these systems are now linked to office networks and the internet.
  4. Hard to patch: a power plant can't be shut down every week for updates.
  5. Attractive to states and terrorists (→ 1.5).

Threats

Real attacks

  1. Stuxnet (2010): damaged centrifuges at an Iranian nuclear plant (→ 1.5).
  2. Ukraine power grid (2015): about 230,000 people without power for 1–6 hours.
  3. Colonial Pipeline (May 2021): ransomware shut down the largest fuel pipeline in the US for about five days; the company paid about 4.4 million US dollars in ransom.
  4. Mumbai outage (2020): a suspected cyber sabotage, still disputed.

Consequences: one failure spreads

flowchart TD
    P["<b>Power grid fails</b>"]:::red --> T["<b>Telecom, internet</b><br>go down"]:::amber
    P --> H["<b>Hospitals, water pumps</b><br>on backup power"]:::amber
    T --> B["<b>UPI, ATMs, banking</b><br>stop"]:::red
    H --> S["<b>Public safety</b><br>at risk"]:::red
    classDef amber fill:#d6a24424,stroke:#d6a24480
    classDef red fill:#d0707024,stroke:#d0707080

Protecting Critical Infrastructure

Measures inside each organisation

  1. Risk assessment: find the most critical systems and their weak points (→ 4.9).
  2. Segmentation and air gaps: keep control systems separate from office networks and the internet.
  3. Monitoring: intrusion detection on control networks, watched 24 × 7 (→ 6.7).
  4. Patching and secure settings, planned around maintenance windows.
  5. Strong access control: MFA, least privilege, no shared passwords.
  6. Incident response and backups: a tested plan to restore operations quickly.
  7. Staff training, including against phishing.
  8. Public–private partnership: private companies run most infrastructure, so they share threat information with the government.

National-level protection

  1. NCIIPC (National Critical Information Infrastructure Protection Centre): created under Section 70A on 16 January 2014; a unit of NTRO; the national nodal agency for protecting CII.
  2. CERT-In (formed 2004; statutory under Section 70B): handles cyber incidents nationally. Since 2022, organisations must report specified incidents to it within 6 hours.
  3. Sector CERTs, such as those for the power sector, handle incidents in their own sector.
  4. National Cyber Security Policy 2013: called for NCIIPC, a 24 × 7 CERT-In and the training of 5 lakh cyber security professionals.
⚡ Quick recall
  • Critical infrastructure? → systems whose failure harms national security, economy, health, safety
  • CII? → the computer systems that run them · IT Act Section 70 · protected system: up to 10 years
  • Sectors? → power · banking and finance · telecom · transport · government · strategic enterprises · (health, water, defence)
  • Why targeted? → huge impact · old systems · now connected · hard to patch · state and terror interest
  • Real attacks? → Stuxnet 2010 · Ukraine 2015 · Colonial Pipeline 2021 · Mumbai 2020 (suspected)
  • Protection? → risk assessment · segmentation, air gaps · monitoring · patching · access control · IR and backups · training · partnership
  • National? → NCIIPC (70A, 2014, NTRO) · CERT-In (70B, 6-hour reporting) · sector CERTs · NCSP 2013
Unit 1 · 0/8