Every defense ministry now has counter-UAS on its agenda. Most still define it by a threat model that the war in Ukraine has already made obsolete.

Executive Summary

  • Counter-UAS (C-UAS) is the discipline of detecting, identifying, and defeating hostile unmanned aircraft. The threat, however, has outrun the textbook definition.
  • Legacy C-UAS was built for a single piloted drone with a jammable link. Autonomous swarms have neither a pilot to target nor a single signal to sever.
  • The decisive layer is no longer the drone. It is the AI coordination stack that commands it. HokuQ operates at that layer.

Counter-UAS (counter unmanned aircraft systems) describes the technologies and doctrine used to detect, track, identify, and defeat hostile drones. For a decade, that definition was adequate: the threat was a piloted or remotely operated aircraft with a communications link you could detect and disrupt.

That threat has changed faster than the doctrine describing it. Autonomous drone swarms, coordinated by onboard AI, have no pilot to neutralise and no single signal to sever. Understanding what counter-UAS means in 2025 requires understanding why the systems built for the old definition now fail against the new one.

What Counter-UAS Traditionally Covers

Traditional counter-UAS rests on three functions: detect the drone, identify whether it is a threat, and defeat it before it reaches its objective.

Detection uses sensors to find the aircraft. Identification distinguishes a hostile drone from a bird or a friendly platform. Defeat is the act of stopping it. Around these three functions, an entire industry of sensors and effectors has grown.

The assumption underneath all of it is a human-operated threat: an aircraft flown or directed by a person, dependent on a link to that person. Break the link or remove the operator, and the threat falls. That assumption no longer holds.

Why the Definition Is Now Obsolete

An autonomous swarm has no pilot to target and no single command signal to sever. It removes the two things traditional counter-UAS was designed to exploit.

Modern attack drones increasingly carry onboard intelligence. They navigate, adjust, and coordinate without continuous human control. A swarm of them shares behaviour across the group, so disabling one changes nothing about the rest.

The Shahed-class drones used at scale in Ukraine, and the layered drone-and-missile attacks in the Red Sea, demonstrate the pattern: cheap, numerous, and autonomous enough that the human-in-the-loop the old doctrine assumed simply is not there to attack.

The Layer the Old Systems Cannot Reach

What drives an autonomous swarm is not a pilot or a link. It is an AI coordination stack. That stack is the attack surface no legacy system targets.

A swarm behaves as a system because software coordinates it. That coordination layer (the logic that turns a hundred individual drones into a single adaptive threat) is where the swarm's capability actually lives. It is also the layer no detection sensor or conventional effector engages.

This is the gap that defines modern counter-UAS. Defeating the swarm means defeating the intelligence that commands it, not chasing each airframe individually.

What This Means for Procurement

A counter-UAS capability that only addresses individual drones is buying yesterday's war. The question to ask vendors is whether they engage the coordination layer at all.

Decision-makers evaluating counter-UAS should look past the count of sensors and effectors and ask a harder question: what does this system do against an autonomous swarm with no pilot and no single signal? If the answer is framed entirely around individual airframes, it answers a threat that is already fading.

HokuQ exists to address the layer the legacy market does not: the quantum-secure AI coordination stack that drives the swarm. The doctrine is simple to state. Defeat what controls the drones, not merely the drones.