Over the past year, I’ve written in Police1 about a growing vulnerability in public safety and homeland security: the rapid evolution of drone technology and the challenge of developing counter-drone capabilities at the same pace.
Thank you for reading this post, don't forget to follow and signup for notifications!
From weaponized drone attacks near the U.S. border to broader concerns about the nation’s ability to detect and respond to unmanned aerial threats, the warning has been consistent. Drone technology is advancing quickly. The barriers to entry are falling. And the gap between emerging threats and our preparedness to address them remains significant.
The FBI disruption of an alleged multi-phase attack plot targeting the UFC Freedom 250 event on the White House grounds on June 14 brings those concerns into sharper focus. According to federal authorities, the alleged plan involved explosive-laden drones as part of a broader attack designed to create panic and chaos during the event.
| RELATED: FBI: Multiple arrests made in thwarted attacks targeting White House UFC show
The specifics of this case will continue to emerge, and the full scope of the alleged plot remains under investigation. But regardless of how the facts ultimately develop, the incident highlights a broader reality law enforcement leaders can no longer afford to overlook: Hostile drone activity has become part of the modern threat landscape, and many agencies are still working to build the training, policies and operational capabilities needed to address it.
We are no longer talking about a future threat set. This is the operating environment now. Public events, government sites and critical infrastructure are already in that space.
And law enforcement is still catching up.
A counter-drone capability gap we can no longer ignore
Across the country, drones have become a standard tool in policing. They are used every day for search and rescue, crash reconstruction, disaster response and tactical overwatch. The operational value is clear.
The challenge is that drone adoption and counter-drone preparedness have not developed at the same pace.
While agencies have invested heavily in using drones to enhance operations, far fewer have access to the training, authorities, detection capabilities and response frameworks needed to address hostile or unauthorized drone activity.
In many agencies, personnel responsible for drone operations have had limited exposure to adversary use cases, detection limitations or counter-UAS response protocols. In other places, training exists, but it’s still high-level and not fully integrated into incident command structures in a way that reflects how these systems behave during real-world events.
To be clear, this is not a criticism of state, local or federal law enforcement, nor of homeland security professionals. Everyone in this space is working in good faith under very real pressure, trying to keep up with a threat environment that is moving quickly and unevenly. The issue is structural.
| WATCH ON-DEMAND: Protecting major events from drone threats
Training, doctrine, detection capabilities and counter-UAS authorities have not developed at the same pace as the emerging drone threat. As a result, agencies are increasingly expected to secure airspace around critical locations and events without a fully mature framework for detection, integration and response.
At the federal level, there is deep expertise. The challenge is that it doesn’t consistently make its way down to the state, local and campus agencies that are increasingly the first to arrive on scene. That disconnect matters.
Policy delay and structural lag
This is not just about training or technology. There’s also a policy dimension that has been slow to adjust.
For years, the national conversation around drones and counter-UAS has moved more cautiously than the operational reality would suggest it should. Policymakers have had to balance legitimate concerns around airspace safety, privacy and civil liberties with a rapidly expanding set of public safety and adversarial use cases. The result has been delay.
At the same time, counter-UAS authorities have largely remained concentrated at the federal level. That structure exists for understandable reasons tied to airspace control and national security coordination. But in practice, it has also limited how quickly state and local agencies can develop consistent, scalable counter-drone capabilities.
This isn’t about assigning blame. It’s about recognizing that the system has not kept pace with the threat. And the impact is operational. Local agencies are being asked to secure major events, critical infrastructure and large public gatherings without having consistent access to the same tools or authorities needed to fully address the aerial component of those environments.
Procurement without a unified strategy
Procurement is another area where the gaps are showing.
Too often, investments in drone-related and counter-UAS capabilities are driven by immediate operational needs rather than a broader strategy that includes detection, interoperability and long-term counter-UAS planning. As a result, agencies may acquire individual capabilities without developing a comprehensive framework for identifying, tracking and responding to hostile drone activity.
That can create fragmentation across jurisdictions, with varying levels of preparedness, different technology standards and limited interoperability during large-scale incidents or special events.
Layered on top of that is the continued use of foreign-manufactured platforms, including Chinese drones, in public safety and infrastructure environments. While many of these systems are effective and widely used, their presence in sensitive environments continues to raise unresolved questions around supply chain security and long-term dependency.
These are not abstract policy concerns anymore. They are operational considerations.
Why this matters
Taken together, these issues have direct homeland security implications.
If we cannot consistently detect, track and respond to unauthorized or hostile drone activity, then we are leaving gaps around some of the most sensitive parts of the country’s infrastructure and public event security environment.
When you combine uneven training, fragmented procurement and limited operational authorities, you end up with a system that is more reactive than preventive. That’s not sustainable anymore.
What the White House case should trigger
The FBI’s disruption of the alleged plot shouldn’t be treated as just another successful interdiction. It should be a signal. What it reinforces is fairly clear:
- Hostile drone activity is becoming a realistic planning consideration, not a hypothetical one
- High-visibility events remain priority targets
- Drone technology continues to lower the barrier to disruption
- Counter-drone detection and response capabilities remain inconsistent across jurisdictions
The bigger issue isn’t any one case. It’s where this is heading.
Recommendations for law enforcement leaders
If we are serious about closing this gap, a few priorities stand out:
- Treat counter-UAS as core infrastructure: This is not a specialty capability anymore. It needs to be part of standard incident command planning.
- Standardize training across jurisdictions: State and federal partners should expand practical, scenario-based training for local agencies, especially those covering major events and critical infrastructure.
- Build drone threat awareness into ICS training: Airspace awareness and counter-UAS response should be part of how we teach incident command at every level.
- Create clearer procurement standards: Agencies need better frameworks for evaluating systems based on security, interoperability, lifecycle planning and operational risk.
- Revisit supply chain risk in sensitive environments: Where drones are used around critical infrastructure, there needs to be a more serious conversation about long-term dependency and trusted systems.
- Improve federal-to-local knowledge transfer: There is strong expertise at the federal level. The challenge is making it operationally usable at the local level in real time, not just in policy documents.
Final thoughts
The FBI disruption underscores something that can’t be ignored anymore. Drones are not an emerging issue. They are here, operationally, right now.
While progress has been made, particularly in the adoption of drones as public safety tools, the broader system has not fully caught up with the challenges posed by hostile or unauthorized drone activity. Training, policy, procurement and operational integration remain uneven, and that unevenness shows up most clearly at the local level where most real-world incidents are handled.
I said it last year in Police1, and it still holds true today. We are behind. The gap hasn’t closed. If anything, it has widened slightly as the technology has accelerated.
None of this is irreversible. What’s needed now is alignment, consistency and a recognition that counter-UAS is no longer a future planning issue. It is part of day-to-day public safety and homeland security operations, and it needs to be planned, trained and resourced accordingly.
Additional resources
