By Dr. Kimberly Jill Elenberg and William King, BG (Ret.)
For decades, CBRNE risk was treated as episodic: a reactor accident, a derailment, a laboratory mishap. Planning frameworks assumed discrete events, clear authorities, intact infrastructure, and time to deliberate. Exercises were bounded. Scenarios were sequential. Decision timelines were measured in hours or days.
That world no longer exists.
Today’s CBRNE risk environment is continuous, distributed, and increasingly shaped by conflict. Hazards emerge not only from accidents, but from deliberate action—often exploiting the seams between physical infrastructure, cyber systems, and human response. The result is a class of events that unfold faster than traditional response frameworks were designed to handle.
Chernobyl: A Deliberate Strike on Nuclear Infrastructure
In February 2025, a low-cost unmanned aerial system carrying a high-explosive warhead struck the New Safe Confinement (NSC) structure over Reactor Four at the Chernobyl Nuclear Power Plant. The drone punctured the outer cladding, ignited fires inside insulation layers never designed for flame or water exposure, and forced emergency crews into weeks of improvised repair work under radiological constraints.
The International Atomic Energy Agency later delivered a stark assessment: the structure had lost its primary confinement function. While radiation levels outside the shelter remained stable, the NSC could no longer be relied upon to confine radioactive material.
This was not an accident. It was a deliberate strike on nuclear infrastructure.
Chernobyl as a Live-Fire Systems Test
Chernobyl is often invoked as a historical warning about secrecy, complexity, and technological overconfidence. In 2025, it became something else entirely: a real-world systems test conducted under wartime conditions. In a single night, multiple long-standing assumptions failed. Post-accident nuclear infrastructure proved targetable. Containment systems faced hostile loads they were never designed to withstand. Emergency response frameworks written for accidents proved insufficient for attack. From a CBRNE perspective, this was not a nuclear safety issue in isolation. It was a compound hazard involving explosives, radiological material, degraded sensing, responder exposure risk, and time-compressed decision-making. The failure was not confined to a single component; it emerged from interactions across systems.
Chernobyl is not an outlier. It is part of a broader shift in how CBRNE risk manifests in contested environments. Across Europe, low-cost sabotage has disrupted transportation, energy systems, and industrial facilities. In Ukraine, the destruction of the Kakhovka Dam forced emergency improvisation to maintain cooling water for the Zaporizhzhia Nuclear Power Plant. Radiation monitoring stations have been destroyed by shelling. Offsite power has been repeatedly lost. Cyber and electronic warfare have degraded situational awareness.
These events share three defining characteristics. They are cheap to execute and expensive to mitigate. They exploit interdependencies across physical, cyber, and human systems. And they compress decision timelines beyond the limits of human-only response.
Why Autonomy Is Now Central to CBRNE Response
Autonomy, in the CBRNE context, is the capability of a system to perceive its environment, assess conditions, and execute bounded actions or recommendations without continuous human direction, in accordance with predefined standards, constraints, and authority thresholds.
In practice, autonomy enables CBRNE systems to operate under hazardous, degraded, or time-compressed conditions by accelerating sensing, analysis, prediction, and coordination—while remaining accountable to human oversight, validated models, and established doctrine.
Autonomy must be embedded throughout the CBRNE response stack, not as a single tool but as a layered capability. However, as autonomy and AI are increasingly embedded in CBRNE detection and response, standards have moved beyond technical reference documents. They now function as strategic infrastructure—governing what systems are trusted, how decisions are made, and whether autonomous capabilities can be deployed at scale across agencies and borders.
Without standards, there is no shared trust. Without shared trust, autonomy cannot scale.
The Lesson Chernobyl Leaves Us
CBRNE risk is no longer episodic; it is continuous and contested. Autonomy is no longer an enhancement but a prerequisite for a timely response. Standards are no longer paperwork exercises; they are operational infrastructure, determining whether systems perform reliably when failure carries strategic consequences. If governments, regulators, and operators respond by updating standards and training to reflect conflict conditions, binding autonomy to demonstrable performance, and treating test data as shared national infrastructure, they gain something essential in crisis: confidence.
Not certainty. Confidence.
