Federal investment in counter-unmanned aircraft systems is moving from isolated pilots and test events toward planning for sustained, nationwide operations. That shift is visible in DHS documents and activity this year and it has practical implications for agencies and companies that want to build, sell, or operate C-UAS capabilities in the near term.

What DHS is funding and testing DHS Science and Technology has run discrete test events and provided on-site technical support at major public events to evaluate detection and mitigation tools in operational conditions. Those exercises are not marketing exercises. They are a signal that DHS is consolidating operational requirements across components including the Secret Service, Coast Guard, Customs and Border Protection, and the Federal Protective Service. These deployments give vendors and local agencies clear, concrete performance expectations to design toward.

At the same time, DHS moved an important planning document into the public sphere. In late July DHS released a Draft Programmatic Environmental Assessment and a Draft Finding of No Significant Impact for nationwide C-UAS operations, showing intent to scale C-UAS activities and to analyze environmental and compliance impacts ahead of broader deployments. That kind of program-level planning matters because it precedes procurement, training investments, and long-term sustainment funding.

Budget and legislative context Congress has been funding countermeasures at component level for several budget cycles and has signaled interest in reauthorizing and clarifying counter-UAS authorities. Appropriations and committee reports have directed resources to mobile surveillance, counter-UAS, and integrated detection for border and facilities protection, which creates multiple acquisition streams across DHS components. Meanwhile, Congress has also pursued reauthorization and reform legislation to extend counter-UAS legal authorities and set standards for coordination, privacy protections, and FAA engagement. That combination of appropriations language and legislative activity is shaping how DHS prioritizes C-UAS spending.

How funding is likely to flow and where gaps remain Expect funding to follow three tracks: 1) component-led procurements for mission-specific needs such as FPS protection of federal facilities and CBP border monitoring; 2) S&T and testbed investments that evaluate new sensors and mitigation approaches; and 3) program-level investments supporting nationwide policy, environmental compliance, and standards. The Draft PEA shows DHS is preparing the program layer that enables the first two tracks to scale.

But funding alone will not produce effective solutions. Two persistent gaps deserve attention from purchasers and vendors:

  • Sustainment and lifecycle funding. Many agencies have funded initial buys or pilot contracts without locked-in budgets for operator training, software updates, spectrum licensing, and equipment refresh. Procurement plans need to include realistic sustainment lines.
  • Legal, privacy, and interagency frameworks. The House-level reauthorization effort demonstrates the need for clear authorities and interoperability rules before mitigation systems are widely used. Without consistent standards from DHS, DOJ, FAA and Congress, vendors risk building to requirements that change or are legally constrained.

Practical advice for vendors and local agencies

  • Design for auditable privacy protections. Procurement teams are asking for data minimization, retention controls, and demonstrable chain of custody for sensor data. Systems that bake those in will be more competitive in DHS and state procurements.
  • Plan for modular integration. DHS testing emphasizes multi-sensor fusion and integration with command centers. Solutions that plug into common data buses and support open APIs will lower integration risk.
  • Build sustainment into price models. Offer firm-life-cycle packages including operator training, software maintenance, and spare parts, rather than one-off hardware sales. Approving authorities are increasingly sensitive to long-term total cost of ownership.

What to watch next Watch DHS program-level documents and NEPA processes closely. The Draft PEA is a predictable bellwether: when it moves to a final FONSI or similar decision, expect downstream procurement notices, expanded test schedules, and new standards work with the FAA. Also track congressional action on reauthorization and appropriations language because funding streams and legal authorities will determine which components can acquire mitigation tools and under what conditions.

Bottom line Through 2025 DHS has shifted from discrete C-UAS pilots toward programmatic planning and operational testing that prefigure larger investments. Vendors and public safety buyers who align products to privacy-forward policy, modular integration, and lifecycle sustainment will be the ones that convert DHS interest into awarded contracts and long-term deployments.