The bill tasks the Secretary of Defense to stand up a bilateral United States–Israel Defense Technology Cooperation Initiative that accelerates joint research, testing, and the transition of Israeli-origin and jointly developed technologies into U.S. military systems. It directs DoD to create frameworks for collaborative R&D, licensing, joint ventures, and U.S.-based co-production while coordinating across relevant DoD components and other federal agencies.
The initiative is positioned as a practical vehicle to speed deployment of capabilities (from counter‑UAS to AI and missile defense), strengthen defense industrial ties, and preserve the U.S. qualitative military edge. The law also requires periodic briefings and public, unclassified updates and authorizes multi‑year funding to support stand‑up and early activities.
At a Glance
What It Does
The bill directs the Secretary of Defense, with concurrence of Israel’s Minister of Defense, to establish a cooperative initiative to identify operationally useful Israeli‑origin and jointly developed technologies and accelerate their transition into U.S. programs of record. It also tasks DoD with creating industrial cooperation frameworks—licensing, joint ventures, and U.S.-based co‑production—and coordinating with existing DoD innovation offices.
Who It Affects
Affected parties include DoD acquisition and requirements offices, innovation and prototyping organizations (e.g., Defense Innovation Unit, DARPA, Missile Defense Agency), U.S. and Israeli defense firms, universities and research labs engaged in bilateral projects, and federal export‑control and trade agencies required to clear technology flows.
Why It Matters
This creates a formal channel meant to shorten the path from foreign innovation to U.S. fielding and to encourage co‑production inside the U.S. For acquisition and industrial planners, it can reshape sourcing, IP negotiations, and export‑control workflows between two allied defense ecosystems.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 3 is the engine: it requires the Secretary of Defense, with the concurrence of Israel’s Minister of Defense, to establish the United States‑Israel Defense Technology Cooperation Initiative. The Initiative is not a single program office on paper but a mandate to coordinate joint activity across research, prototyping, test and evaluation, and industrial cooperation.
That includes identifying Israeli‑origin or jointly developed technologies that have operational utility and mapping pathways to integrate them into U.S. systems and programs of record.
The bill lists substantive activity types the Initiative must pursue: collaborative research with government, industry, and academia; transition plans to procurement and acquisition pathways; and frameworks for joint ventures, licensing agreements, and U.S.-based co‑production or manufacturing partnerships with Israeli industry. It also requires DoD to protect sensitive technology and information while pursuing those activities and to align the Initiative with existing DoD organizations and working groups to avoid duplication.The Initiative’s technical scope is explicit: counter‑unmanned systems, anti‑tunneling, missile and air defense (the bill even references “Golden Dome for America”), AI, quantum and autonomy, directed energy, cyber/electronic warfare, biotech and medical defense, network integration and contested logistics, and defense industrial base cooperation.
The Secretary must coordinate Initiative activities with the Secretaries of State and Commerce and other relevant agencies to ensure compliance with export controls and other laws.Reporting and transparency are substantive obligations. DoD must deliver an interim briefing or written update to congressional defense committees within 180 days describing stand‑up steps, early coordination with Israeli counterparts, initial technology priorities, designated DoD leads, and any prototyping or integration actions.
Annual unclassified reports (with classified annexes permitted) must follow, describing activities, progress toward shared security objectives, technologies transitioned into acquisition, industry partnerships, and recommendations for future priorities and authorities. The bill also directs DoD to publish periodic unclassified updates online to the maximum extent practicable, subject to protection of classified and controlled information.Finally, Section 5 authorizes funding—$150 million for each of fiscal years 2027 through 2029—to carry out the Initiative.
That is an authorization, not an appropriation; how much is actually provided depends on subsequent appropriations and DoD prioritization.
The Five Things You Need to Know
The Secretary of Defense must establish the Initiative with the concurrence of Israel’s Minister of Defense—formalizing a bilateral leadership role rather than a unilateral U.S. program.
The statute names ten technical domains (including counter‑UAS, anti‑tunneling, AI/quantum/autonomy, directed energy, cyber/electronic warfare, and missile/air defense such as a “Golden Dome for America”).
DoD must provide an interim briefing to congressional defense committees within 180 days of enactment and then submit annual unclassified reports (classified annexes allowed).
The bill requires DoD coordination with the Secretaries of State and Commerce and lists specific DoD partners to align with (for example, Defense Innovation Unit, DARPA, Missile Defense Agency, Irregular Warfare Technical Support Directorate, and U.S. Space Command).
Congress authorized $150 million per year for fiscal years 2027–2029 to carry out the Initiative; those funds must still be appropriated.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s formal name: the United States‑Israel FUTURES Act of 2026 (United States‑Israel Framework for Upgraded Technologies, Unified Research, and Enhanced Security Act of 2026). Practically, this is the label policymakers and implementers will use when referencing program guidance and appropriations language.
Sense of Congress
Sets out congressional findings and purpose: it frames Israel as a strategic technology partner and argues that accelerating joint innovation and technology integration serves U.S. security and industrial interests. This prefatory language signals congressional intent to prioritize Israel‑U.S. technology pathways when DoD develops implementation guidance and budgets.
Establishment of the United States‑Israel Defense Technology Cooperation Initiative
Directs the Secretary of Defense (with concurrence from Israel’s Minister of Defense) to establish the Initiative and defines its core activities—identifying Israeli‑origin technologies for U.S. integration, conducting collaborative research (government, private sector, academic), enabling transition to procurement, and creating joint licensing/co‑production frameworks. It also specifies a non‑exhaustive list of technical domains and requires DoD to coordinate with and align existing components and working groups to avoid duplication. For implementers, this section is a blueprint: stand‑up requires cross‑component coordination, legal review for transfers/contracts, and operational security safeguards.
Reporting and public transparency
Imposes reporting deadlines and transparency obligations. DoD must brief Congress within 180 days on initial steps and then submit annual unclassified reports (with classified annexes allowed) covering activities, transitioned technologies, partnerships, and resource needs. The Secretary must also post periodic unclassified updates online as practicable while protecting classified or export‑controlled information. This creates dual accountability: formal oversight through Congress plus public facing summaries to signal progress to industry and foreign partners.
Authorization of appropriations
Authorizes $150 million per fiscal year for FY2027–FY2029 to carry out the Act. The authorization establishes a funding expectation for initial years but does not itself obligate funds—Congressional appropriations decisions and DoD budgeting priorities will determine actual resourcing and pacing of Initiative activities.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense 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. military program offices and warfighters — by gaining a dedicated channel to scout and integrate Israeli‑origin technologies more rapidly into programs of record, potentially shortening fielding timelines for capabilities such as counter‑UAS, missile defense, and autonomy.
- Israeli defense firms and research institutions — by creating structured pathways to licensing, joint ventures, and U.S. co‑production that can expand market access and create U.S.-based manufacturing and supply relationships.
- U.S. defense industry and domestic manufacturers — by opening co‑production and manufacturing partnerships that could bring foreign innovation into U.S. supply chains and create new domestic jobs and subcontracting opportunities.
- U.S. research universities and labs — by formalizing collaborative research opportunities and potential funding flows that link academic research directly to transition pathways.
- Congress — by receiving formal interim and annual reporting, plus public updates, which strengthens oversight and gives appropriators data to shape future budgets and authorities.
Who Bears the Cost
- Department of Defense components and program offices — must divert time and planning to stand up and coordinate Initiative activities, absorb implementation overhead, and compete for limited acquisition dollars and personnel attention.
- U.S. taxpayers — through potential appropriations to fund the Initiative and any associated procurement or co‑production investments, including the $150 million annually authorized for FY2027–29.
- Export control and licensing agencies (State and Commerce) — will face increased workload vetting transfers, licenses, and cross‑border IP arrangements to ensure compliance with ITAR/EAR and national security reviews.
- Small U.S. firms partnering with Israeli companies — may face compliance burdens (security, IP, supply chain vetting) and the need to meet U.S. co‑production requirements, adding time and cost to participation.
- DoD acquisition offices — may face pressure to accelerate integration of foreign technologies into programs of record, creating schedule and integration risk if engineering, testing, or certification steps are shortened.
Key Issues
The Core Tension
The central dilemma is speed versus control: the bill seeks to accelerate the movement of foreign innovation into U.S. military systems and incentivize co‑production, but doing so requires loosening or re‑engineering existing safeguards (export controls, IP rules, procurement norms) that were designed to manage national security risk—finding a way to get capability into the field quickly without compromising sensitive technologies or legal controls is the policy problem at the heart of implementation.
The bill is implementation‑heavy but light on procedural detail. It mandates an Initiative and funding authorization, but it leaves critical operational questions to DoD and implementing regulations: how technologies are selected, how intellectual property is allocated when Israeli and U.S. entities co‑develop, and how export controls and Buy‑American/FAR requirements will interact with cross‑border co‑production.
Those policy choices will materially affect whether the Initiative delivers speed without compromising supply‑chain integrity or U.S. legal requirements.
Transparency versus security is another tension. The Act requires public, unclassified updates to the extent practicable while allowing classified annexes.
That balances congressional and industry interest in visible progress with operational security, but it creates ambiguity about what meaningful public metrics will be available for industry planning. Finally, the statute authorizes $150 million per year for three years—a useful down‑payment—but authorization alone does not guarantee appropriations.
DoD will still need to prioritize this Initiative against other modernization demands and must develop internal authorities and processes for licensing, procurement, and co‑production that comply with existing law.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.