C-UAS, short for counter-unmanned aircraft systems, is the set of technologies and procedures used to detect, track, identify, and, when legally authorized, defeat drones that threaten people, facilities, or airspace. The demand signal behind that definition is stark: unauthorized drone incursions over NFL games rose from 67 in the 2018 season to 2,845 in 2023, and the commander of US Northern Command says the military currently defeats only about a quarter of the drones it detects over US installations.
We believe the gap between those two numbers is the defining airspace security problem of this decade. Drones have outpaced the rules and the tools meant to manage them, and every security team, from stadium operators to base commanders, is now being asked the same question: what is in the air above us, and what can we lawfully do about it? This guide answers both parts.
The terms C-UAS, CUAS, counter-drone, and counter-UAS all describe the same discipline. The Department of Homeland Security defines a counter-unmanned aircraft system as a system or device capable of lawfully and safely disabling, disrupting, or seizing control of an unmanned aircraft. In practice, a complete C-UAS capability spans four functions:
The first three functions are open to any organization in the United States. The fourth is tightly restricted by federal law, which is why understanding the legal landscape matters as much as understanding the technology.
No single sensor reliably detects every drone. Modern programs layer complementary technologies, because each one covers a blind spot in the others:
The hard engineering problem is fusing those feeds into one coherent picture instead of four separate alarms. That is the role of a command and control platform: correlate sensor data, filter false positives, and present an operator with a single track per aircraft. Our AirGuard platform was built around exactly that fusion problem, unifying radar, RF, and Remote ID into one operating picture across our hardware layers.
This is where most C-UAS conversations go wrong. Drones are aircraft under federal law, and the FAA warns that private parties who jam, spoof, or shoot at them expose themselves to federal criminal liability, including statutes covering aircraft sabotage and interference with radio communications.
Congress carved out narrow exceptions in the Preventing Emerging Threats Act of 2018, codified at 6 U.S.C. 124n, which gives the Departments of Homeland Security and Justice authority to detect and mitigate credible drone threats to covered facilities and assets. The Departments of Defense and Energy hold parallel authorities for their own installations. According to the Congressional Research Service, those authorities have been extended through September 30, 2031, but they still do not extend to state or local law enforcement, stadium operators, utilities, airports, or corporate security teams.
The practical consequence: for nearly every organization outside those four federal departments, mitigation is off the table. Detection, tracking, identification, and coordinated response with law enforcement are the lawful playbook. That is not a consolation prize. Knowing the drone's track and the pilot's location in real time is what turns an invisible problem into an actionable one.
For the agencies that do hold authority, mitigation itself spans a spectrum of methods. Electronic options include jamming the control and navigation links or taking over the aircraft's command channel. Kinetic options range from net capture to interceptor drones to directed energy. Each carries collateral risk: jamming can disrupt legitimate communications nearby, and a defeated drone still has to land somewhere. Those tradeoffs are a large part of why Congress has moved slowly in expanding who may use them, and why the authorized agencies pair every mitigation tool with the same detection layers civilian operators use.
Three storylines have pushed counter-UAS from a niche concern to a national priority this year.
Military bases are being probed at home. In March 2026, security forces at Barksdale Air Force Base, home to B-52 bombers, observed waves of 12 to 15 drones with long-range control links and resistance to jamming operating over sensitive areas for a week. A Department of Defense Inspector General report published in January found that more than 20 conflicting policies left a large percentage of installations without clear authority to deploy counter-drone systems.
The policy response is accelerating. In December 2025, the Secretary of Defense signed policies that expanded base commanders' defensive areas and classified any unauthorized drone surveillance over installations as a threat. Congress is weighing parallel expansions for civilian agencies and major events.
Civilian venues face the same curve. The NFL's security chief told Congress that drone incursions during games grew more than fortyfold in five seasons, and with the 2026 FIFA World Cup in US stadiums this summer, venue operators are under pressure to field detection coverage now. The battlefield-to-backyard dynamic is one we explored in The Asymmetric Airspace: tactics proven in conflict zones migrate to domestic airspace faster than regulation can follow.
Because mitigation authority is reserved to federal agencies, we advise every civilian security team to build around detection first. A credible program has four elements:
Organizations that field this stack today are not just buying awareness. They are building the evidentiary and operational foundation they will need if Congress extends mitigation authority to additional users, as pending legislation proposes.
C-UAS stands for counter-unmanned aircraft systems. It covers the technologies and procedures used to detect, track, identify, and, when legally authorized, mitigate drones that pose a threat to people, facilities, or airspace. You will also see CUAS, C-UAV, and counter-drone used interchangeably.
No. Drones are aircraft under federal law, and private individuals or companies that shoot at, jam, spoof, or otherwise interfere with one in flight can face federal criminal exposure under multiple statutes. If a drone is creating a safety or security concern, the lawful response is to document the activity, use detection data to locate the operator, and contact law enforcement.
Congress has granted mitigation authority to a limited set of federal departments: DHS and DOJ under 6 U.S.C. 124n for designated covered facilities and assets, plus DOD and DOE for their own installations. State and local law enforcement, airports, stadiums, utilities, and private security teams currently hold no mitigation authority, although pending legislation proposes extending limited authority to vetted state and local agencies.
Detection is the sensing half of C-UAS: finding, tracking, and identifying drones using RF sensors, radar, Remote ID receivers, and cameras. Mitigation is the defeat half: stopping the aircraft through electronic or physical means. Detection is legal for any organization in the United States today. Mitigation is restricted to the authorized federal agencies listed above, which is why civilian C-UAS programs are built detection-first.
C-UAS is no longer a defense acronym. It is a civilian operations requirement arriving on the same curve that took drones from toys to tools to threats in under a decade. The organizations handling it well share one trait: they started measuring their airspace before they had an incident, not after.
We believe airspace awareness is becoming as fundamental to physical security as cameras and access control. The technology to see your airspace exists today, it is legal everywhere in the United States, and it gets more valuable with every incursion it records.
Interested in complete situational awareness over your airspace? Contact our team today to schedule a demo.