BrainParrot

Beyond Kudankulam’s fence, a cybersecurity challenge

GS3Full notePublished: · Updated:

Source: The Hindu, 27 October 2026

Summary

  • Files linked to the Kudankulam nuclear power project in Tamil Nadu surfaced on a dark-web portal after a ransomware attack. The leak was reported on July 15, 2026.
  • The files were held by a contractor's third-party data centre, not by the plant operator. The article argues this shows India's critical-infrastructure cyber policy has not kept pace with a security perimeter that now extends well beyond the plant fence.
  • It stresses that there is no public evidence the reactors or their control and safety systems were accessed. The real issue is who is responsible for protecting sensitive information once it leaves the operator's hands.

UPSC relevance: GS3 — Internal Security: cyber security, critical infrastructure; S&T

Key facts for Prelims

  • Sec. 70 IT Act: "protected system" (CII); Sec. 70A: NCIIPC; Sec. 70B: CERT-In. NCIIPC sits under NTRO (PMO); CERT-In sits under MeitY.
  • CERT-In's 2022 directions made prompt reporting of cyber incidents mandatory (six-hour window; logs kept for 180 days).
  • The Digital Personal Data Protection Act does not generally cover engineering drawings and other technical data that contain no personal data.
  • The ransomware group named in the article is World Leaks. Dtrack malware is associated by researchers with North Korea's Lazarus Group.
  • The author's institution is MP-IDSA (Manohar Parrikar Institute for Defence Studies and Analyses).
  • Kudankulam is in Tamil Nadu. NPCIL is the operator.

Data and details

  • Leak reported: July 15, 2026. Posted by World Leaks on its dark-web portal.
  • About 19,000 files, 14.3 GB, covering 2016 to about 2025: engineering drawings, supplier information, inspection records, meeting minutes, insurance documents.
  • Reliance Infrastructure (EPC contractor for Units 3 and 4) confirmed the breach. It said the data sat on a server of its third-party data centre, Yotta, and that the government had been notified.
  • Yotta confirmed ransomware activity on May 29 and said it had been contained. By June the attackers were claiming the data and demanding a ransom.
  • NPCIL said the information related only to non-nuclear infrastructure and was unrelated to nuclear safety systems.
  • The article notes that a ransomware group's claims are not evidence, since such groups routinely inflate what they hold. It adds that nothing in the public domain suggests reactors or control and safety systems, which are isolated from the Internet by design, were accessed.
  • 2019 precedent: Dtrack malware was found on a computer on the plant's Internet-facing administrative network. NPCIL first dismissed the reports, then confirmed the infection while saying the critical internal network was isolated. The article notes the two incidents are not technically linked, but in both the core held and the exposure was at the periphery.
  • Expansion: Kudankulam to 6,000 MW. Smart grids, digital public infrastructure, private defence and space under Atmanirbhar Bharat, and government data moving to commercial cloud all widen the exposure.
  • Analyst Nickolas Roth of the Nuclear Threat Initiative is cited. Such documents may reveal how systems can be accessed.

Static–dynamic linkage

  • Critical Information Infrastructure (CII) protection in India rests on the IT Act, 2000. Section 70 covers "protected systems", Section 70A the national nodal agency (NCIIPC) and Section 70B CERT-In.
  • Obligations are tied to the operator of the protected system. Once data goes to contractors, subcontractors, cloud or data-centre providers, protection depends mainly on contracts. This is the supply-chain gap.
  • Security by perimeter (air-gaps, segmentation) does not cover the wider ecosystem of vendors and hosts that holds sensitive drawings, schedules and credentials.

Syllabus mapping: GS3 – Internal Security: cyber security, protection of critical infrastructure; GS3 – S&T: nuclear energy, IT; GS2 – Governance/regulation.

Background primer

NCIIPC (National Critical Information Infrastructure Protection Centre)

What it is:
India's national nodal agency for safeguarding Critical Information Infrastructure.
Founded:
Created under Section 70A of the IT Act, 2000 by a gazette notification on January 16, 2014, as a unit under the National Technical Research Organisation (NTRO).
Mandate:
CII means a computer resource whose incapacitation or destruction would debilitate national security, the economy, public health or public safety. It provides threat intelligence, situational awareness, alerts and vulnerability information to CII organisations. It follows up on compliance with the IT (Information Security Practices & Procedures for Protected Systems) Rules, 2018. It also issues IT and OT security guidelines and promotes baseline controls, including supply-chain safeguards.
Why it matters:
Systems whose failure would damage national security or the economy need a specialised, security-agency-linked body. A general incident-response agency is not enough for them.

CERT-In (Indian Computer Emergency Response Team)

What it is:
The national agency designated under Section 70B of the IT Act for responding to cyber security incidents.
Founded:
Set up in January 2004 and functioning under the Ministry of Electronics and IT (MeitY). The IT (Amendment) Act, 2008 (in force 27 Oct 2009) designated it the national agency under Section 70B.
Mandate:
Collects, analyses and disseminates information on cyber incidents, issues advisories and coordinates emergency containment. Its 2022 Directions require covered entities to report specified incidents within six hours of noticing them and to retain ICT logs for 180 days.

NPCIL / Kudankulam Nuclear Power Project

Additional context

  • Under Section 70, unauthorised access to a protected system can attract imprisonment of up to ten years and a fine.
  • India has a National Cyber Security Coordinator under the National Security Council Secretariat to coordinate among agencies.
  • The MHA created the Indian Cybercrime Coordination Centre (I4C) to handle cybercrime in a coordinated way.

Mains dimensions

  • Accountability gap: The operator can say its systems were not breached, the contractor can blame the host, and the host can blame the malware. Sensitive documents still reach the dark web. The key question is who is responsible once data leaves the operator's control.
  • Legal design: A "protected system" belongs to the infrastructure, so obligations fall on the operator. Downstream protection is largely contractual. The DPDP Act does not reach non-personal technical data.
  • Strategic risk without direct access: The leaked material can help adversaries identify contractors, craft phishing targets and find the weakest subcontractor route. Assessment must therefore ask how information could be misused later, not only what was taken.
  • Policy lag: Seven years after the 2019 Dtrack incident, the article argues the lesson of the ecosystem's security was not taken systematically. It says cyber policy built for a state-built-and-controlled system no longer fits one that relies on private contractors, subcontractors and commercial infrastructure.
  • Way forward (article's five steps):
  • Security obligations should follow the data, with defined standards, liability and audit clauses in procurement contracts.
  • Real data classification, so contractors hold only the data needed, for only as long as needed.
  • Third-party risk assessment and red-team exercises on the vendor ecosystem, replacing annual compliance certificates.
  • Zero-trust for projects of national importance.
  • A single national framework for critical-infrastructure supply-chain security, converging CERT-In, NCIIPC, sectoral regulators and operators, assigning responsibility before a breach. The article says the route to this, whether new legislation or a creative reading of the IT Act, "can wait".
  • Caution: Reassurances from NPCIL should be taken seriously, but they address the reactor and not the wider ecosystem.

Possible Mains question

**GS3 (Internal Security), 15 marks:** "The protection of critical infrastructure can no longer be confined to the physical and network perimeter of the operator. Discuss in the context of the recent data breach linked to a nuclear power project, and suggest a framework for securing supply chains."

Related topics

  • IT Act 2000 (Sections 66F, 70, 70A, 70B); IT (Protected Systems) Rules 2018
  • Digital Personal Data Protection Act 2023 and its scope
  • National Cyber Security Policy; National Cyber Security Coordinator; I4C
  • Nuclear regulation: Atomic Energy Act 1962, AERB, Civil Liability for Nuclear Damage
  • Zero-trust architecture, air-gapping, ransomware, supply-chain attacks

Topics: GS3Sci & Tech

How we write and check these notes →

All current affairs of 27 October 2026 → · UPSC Current Affairs