The Emerging Innovative Border Technologies Act directs the Secretary of Homeland Security, through CBP and the DHS Science and Technology (S&T) office, to deliver a comprehensive plan within 180 days that identifies, integrates, and lays out deployment pathways for emerging technologies relevant to border security. The statutorily enumerated technologies include AI and machine learning, LIDAR and hyperspectral sensors, optical and cognitive radar, fiber-optic sensing, unmanned aerial systems, advanced surveillance and nonintrusive inspection tools, and other novel systems.
Beyond a tech inventory, the bill requires the plan to explain how CBP’s Innovation Teams operate, how pilots will transition into formal acquisition programs of record, what procurement authorities apply or are missing, privacy and community impact assessments, legacy program phase-outs with cost estimates, and metrics to evaluate success. It also authorizes CBP Innovation Teams and compels annual reporting to the relevant congressional committees on pilots, operations, and transition status—creating a structured pathway from commercial R&D to fielded border capabilities with oversight hooks for Congress and DHS leadership.
At a Glance
What It Does
Requires DHS to submit a detailed plan within 180 days that identifies candidate technologies, explains how CBP Innovation Teams will evaluate and transition them, and sets out procurement, scaling, and program-of-record timelines. It also authorizes CBP Innovation Teams to operate, requires operating procedures and strategic goals, and mandates annual reporting to congressional homeland security committees.
Who It Affects
Directly affects U.S. Customs and Border Protection, the DHS Science and Technology Directorate, DHS acquisition and program offices, and companies (including small and disadvantaged businesses) that develop sensors, AI, UAVs, inspection systems, and related technologies. Border communities and privacy advocates are affected indirectly through required privacy and security impact assessments.
Why It Matters
Creates a formal mechanism to move emerging commercial technologies into CBP operations and to identify gaps in procurement authorities and funding needs. It changes how pilots are governed—requiring metrics and transition plans—so vendors, acquisition officers, and oversight staff will need to account for accelerated fielding and Congressional transparency.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill makes two related demands. First, within six months DHS must deliver a single, comprehensive plan to the House and Senate homeland security committees that catalogs emerging technologies relevant to border operations and lays out how CBP and DHS S&T will identify, adapt, and field them.
That plan must be more than a list: it must describe specific programs, objectives, timelines, costs, metrics, and how pilots will scale into programs of record.
Second, the statute formalizes and authorizes CBP Innovation Teams: small, mission-focused units charged with researching and adapting commercial and government technologies for border missions. The Commissioner must require each team to adopt detailed operating procedures that clarify roles across CBP and DHS, set strategic goals with projected costs and timeframes, and include a metric tracking the rate at which pilots transition into programs of record.
The bill also requires an initial CBP Innovation Teams report within 180 days and then annual updates describing pilots, which technologies proved successful, and transition progress.The plan’s required contents are comprehensive. DHS must assess existing procurement authorities and say whether new authorities are needed, identify technologies used elsewhere in government that CBP could adopt, propose how to scale pilots, estimate costs to retire or replace legacy systems, and produce privacy and security impact assessments for border communities.
It must also inventory recent advances across manned and unmanned aircraft sensors, multiple surveillance form factors, nonintrusive inspection modalities, tunnel detection, communications gear, and related fields, and propose ways to incentivize private-sector development and collaboration with labs, universities, and small businesses.Practically, the statute creates a predictable reporting cadence and a checklist for conversion of prototypes into sustained capabilities. It compels CBP and DHS S&T to align R&D, procurement, and fielding plans, but it does not itself appropriate funds or rewrite federal procurement laws.
The emphasis on metrics, transition plans, and cost estimates is intended to reduce stove-piped pilots that never scale, while giving Congress the information to assess whether CBP has the authorities and resources to adopt the technologies it identifies.
The Five Things You Need to Know
The Secretary of Homeland Security must submit a detailed plan to the House and Senate homeland security committees within 180 days of enactment identifying candidate emerging technologies and deployment pathways.
The plan must analyze procurement authorities, state whether additional authorities are needed, and include cost estimates for phasing out legacy border technology programs replaced by new systems.
The Commissioner of CBP is authorized to maintain one or more CBP Innovation Teams and must require each team to adopt operating procedures, strategic goals, projected costs, timelines, and metrics for transitioning pilots into programs of record.
CBP must provide an initial report on Innovation Team activities within 180 days and annual reports thereafter that include pilot descriptions, success determinations, documented capability gaps addressed, and status of transitions to programs of record.
The statute requires an assessment of privacy and security impacts on border communities and a technology inventory covering AI/ML, LIDAR, hyperspectral sensors, optical/cognitive radar, unmanned systems and counter-UAS, mobile and tower surveillance, nonintrusive inspection technologies, tunnel detection, and communications equipment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the act’s name as the "Emerging Innovative Border Technologies Act." This is a standard, formal opening that has no operative effect but frames the bill’s focus on innovation and emerging technology for border operations.
Plan submission: scope and deadline
Imposes a 180-day deadline for the Secretary, acting through CBP and DHS S&T, to deliver a plan to Congress that identifies and sets out how to integrate emerging technologies into border security operations. The provision explicitly lists technology categories (AI/ML, LIDAR, hyperspectral sensors, optical/cognitive radar, fiber-optic sensing, nanotech, imaging/identification systems, UAVs, etc.), making the inventory requirement broad and technology-agnostic but bounded by enumerated categories.
Required plan contents: procurement, scaling, privacy, and costs
Lists 13 substantive elements the plan must contain: how CBP uses Innovation Teams; assessments of contributions from those teams; team composition and coordination with acquisition offices and DHS partners; technologies used elsewhere in government that CBP could adopt; analysis of CBP procurement authorities and gaps; plans to move pilots into programs of record; program descriptions with objectives and timelines; privacy and security impact assessments for border communities; legacy program phase-out and cost estimates; and coordination with DHS S&T on R&D and private-sector engagement. This section ties together acquisition, oversight, privacy, and budgeting considerations into a single reporting obligation.
Technology categories to be inventoried
Specifies an inventory of recent advances across several capability areas including manned-aircraft sensors and communications, unmanned aerial systems and counter-UAS, various surveillance platforms (mobile, tower, unattended sensors, lighter-than-air), nonintrusive inspection tech (including muon tomography), tunnel detection, and communications equipment (radios, LTE broadband, miniature satellites). For acquisition and program managers, this is a directed market scan tied to mission needs rather than a free-form R&D wishlist.
CBP Innovation Teams: authority, procedures, and reporting
Authorizes CBP to maintain one or more Innovation Teams to research and adapt commercial and other technologies for CBP missions. The Commissioner must require teams to adopt operating procedures specifying roles, partner protocols, and rapid transition protocols; set planning and strategic goals with projected costs, timeframes, and KPIs; and report on activities. CBP must submit an initial Innovation Teams report within 180 days and annual reports thereafter to the same congressional committees, including copies of procedures, pilot summaries and success determinations, and transition status to programs of record—giving Congress visibility into both experiments and lifecycle planning.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- U.S. Customs and Border Protection operational units — receive a mandated process to identify capability gaps, formal pathways to scale pilots into programs of record, and required metrics and cost estimates that can justify resourcing decisions.
- DHS Science and Technology Directorate and federal labs — gain a clearer mandate to coordinate R&D with CBP requirements, widening opportunities to move research into operational use and to influence acquisition priorities.
- Private-sector vendors and startups (including small and disadvantaged businesses) — obtain a structured engagement and potential incentives to develop mission-relevant products, plus clearer signals about what technologies CBP values and how pilots may convert to procurements.
- Congressional homeland security committees — get standardized, periodic information (initial plan and annual Innovation Team reports) that improves oversight of technology adoption, procurement gaps, and budgetary implications.
Who Bears the Cost
- CBP and DHS acquisition/program offices — must develop operating procedures, metrics, and transition plans and absorb the administrative and program management burden of scaling pilots into programs of record, potentially requiring reallocation of staff and funds.
- Federal budget and program accounts — the bill requires cost estimates and phase-out plans but does not appropriate funds, so agencies may need to reprogram existing resources or request new funding to implement recommended transitions.
- Small vendors and integrators — while offered engagement opportunities, they may face technical and compliance costs to meet government transition requirements, security vetting, and integration standards before becoming viable program suppliers.
- Border communities and civil liberties stakeholders — face increased surveillance exposure if recommended technologies are fielded; addressing these impacts will impose costs on CBP (for mitigation measures, privacy protections, or community outreach) and on oversight mechanisms.
Key Issues
The Core Tension
The bill forces a choice between speed and oversight: it pushes CBP to identify and rapidly transition commercial innovations into operational capabilities to close capability gaps, but doing so quickly risks inadequate privacy safeguards, weak acquisition scrutiny, potential programmatic waste, and unclear funding—so the primary dilemma is how to reconcile operational agility with accountable, well-resourced procurement and civil‑liberties protections.
The bill creates a disciplined pathway from pilot to program of record, but it stops short of providing funding or changing acquisition law. That produces a practical implementation gap: agencies will produce costed transition plans and identify authority shortfalls, but moving from plan to purchase will still depend on separate budget and procurement processes.
The statute’s requirement to analyze procurement authorities is meaningful, yet it does not itself grant new authorities or timelines for acquiring classified or export-controlled systems, which could stall fielding for some technologies.
Privacy and operational secrecy create another tension. The requirement for privacy and security impact assessments is explicit, but the bill does not define standards, community consultation procedures, or remedies if impacts are found significant.
Simultaneously, several technologies listed (advanced imaging, identification systems, persistent surveillance) may require operational confidentiality. Reconciling transparency for impacted communities and Congress with legitimate security protections will require policy work not mandated by the statute.
Finally, the law asks CBP to incentivize private-sector development and increase engagement with small businesses and labs, but it leaves open how to avoid vendor lock-in, protect against rapid obsolescence, and ensure rigorous independent validation of effectiveness before committing large acquisition dollars.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.