If you followed Congress over the past month, you probably heard about the debates.
Lawmakers argued over whether Army installations should once again carry their previous names. They debated whether Congress should formally designate the Pentagon as the Department of War, revisited officer promotion policies, military fitness standards, and other issues centered on the military’s identity and traditions.
But while Congress debated what America’s military should be called, it was also advancing legislation that could shape how future presidents manage one of America’s closest strategic relationships—and how deeply the United States integrates with a foreign ally in defense technology and intelligence.
Over the past month, The Salty Soldier has been tracking two separate proposals.
The first is Section 219 of the House’s Fiscal Year 2027 National Defense Authorization Act (NDAA), which would establish a framework for expanding U.S.-Israel cooperation in artificial intelligence, missile defense, cyber capabilities, manufacturing, and other emerging military technologies.
The second is Section 622 of the Senate’s Intelligence Authorization Act (IAA), which would expand intelligence sharing with Israel while establishing statutory procedures governing when a future president could reduce that cooperation.
Neither proposal has become law and both can still be changed.
Yet one month after The Salty Soldier first reported on Section 622, the Senate language remains unchanged while Section 219 continues advancing through the House.
Viewed together, the proposals raise questions extending beyond Israel itself.
How closely should the United States integrate with allies in defense technology and intelligence?
Who should decide when those relationships change and should Congress establish permanent frameworks that future presidents inherit?
The House’s National Defense Authorization Act establishes military policy and defense programs.
The Senate’s Intelligence Authorization Act governs America’s intelligence agencies.
Each follows its own legislative process, but together they provide a broader picture of how Congress is approaching the future of U.S.-Israel security cooperation.
On June 4, the House Armed Services Committee approved the FY2027 National Defense Authorization Act by a bipartisan 44-12 vote, sending the legislation to the full House.
While lawmakers spent hours debating military installation names, the proposed designation of the Pentagon as the Department of War, officer promotions, and fitness standards, another provision advanced with comparatively little public discussion.
Section 219.
The proposal would establish a United States-Israel Defense Technology Cooperation Initiative, expanding cooperation in areas including artificial intelligence, missile defense, cyber capabilities, autonomous systems, biotechnology, defense manufacturing, and other emerging military technologies. It also encourages joint research, industrial partnerships, co-production, and the potential integration of Israeli-developed technologies into U.S. military acquisition programs.
One of the legislation’s strongest supporters is the American Israel Public Affairs Committee (AIPAC).
Following committee approval, AIPAC publicly praised the measure, calling it an important step toward strengthening U.S.-Israel defense cooperation in technologies expected to define future warfare.
That support also highlights AIPAC’s growing influence in Washington.
Since expanding into direct campaign spending in 2022, AIPAC and its affiliated political committees have become among the nation’s largest outside political spenders. According to Federal Election Commission data compiled by OpenSecrets and other campaign finance organizations, the organization and its affiliated committees spent approximately $127 million during the 2024 federal election cycle, while continuing significant spending during the 2026 cycle.
Those figures do not establish that campaign spending determines legislative outcomes.
They do, however, provide important context for understanding why legislation involving Israel has historically attracted broad bipartisan support.
AIPAC also highlighted another provision approved by the committee: approximately $750 million for cooperative U.S.-Israel defense programs, including missile defense, counter-unmanned systems, subterranean operations, and emerging technologies.
Supporters argue those investments strengthen the United States by accelerating battlefield innovation, improving missile defense, expanding joint research, and enhancing interoperability between two long-standing security partners.
The proposal also reflects Israeli Prime Minister Benjamin Netanyahu’s publicly stated goal of moving the U.S.-Israel relationship “from aid to partnership,” shifting the focus toward shared technology development, manufacturing, and defense industry cooperation.
Critics, however, argue the legislation raises a broader policy question: How should Congress evaluate whether long-term strategic partnerships continue producing reciprocal benefits for the United States?
Opposition to Section 219 came from a bipartisan group of lawmakers who argued the proposal deserved a standalone debate rather than being incorporated into the annual defense bill.
During the House Armed Services Committee’s June 4 markup, Rep. Ro Khanna (D-Calif.) introduced an amendment to strike what was then Section 224 from the legislation, questioning why Congress was being asked to further expand military cooperation with Israel at a time of growing public debate over U.S. policy in the region.
Khanna argued that if Congress wanted to expand military assistance or deepen defense cooperation with Israel, lawmakers should vote on that question directly rather than embedding it within the broader National Defense Authorization Act. He also questioned how much of the legislative language originated with Israeli officials, noting that Prime Minister Benjamin Netanyahu had publicly urged Congress to move the relationship “from aid to partnership.”
The amendment was ultimately rejected during committee consideration after members from both parties defended the provision.
House Armed Services Committee Ranking Member Adam Smith (D-Wash.), while criticizing Netanyahu’s leadership and expressing concern over Israel’s wars in Gaza, Lebanon, and Iran, nevertheless opposed removing the section.
“I do not like his leadership of Israel or where he is going,” Smith said before arguing that the proposal largely coordinated existing defense technology programs rather than creating an entirely new partnership.
Other members argued the United States benefits directly from Israeli battlefield experience and technology development.
Rep. Jared Golden (D-Maine) said the provision “will ultimately help save American lives” and rejected claims that it would merge the U.S. and Israeli militaries.
After the bill left committee, Rep. Thomas Massie (R-Ky.) announced he would introduce a floor amendment to remove the provision. Rep. Ro Khanna joined that effort, along with Reps. Jim McGovern (D-Mass.), Jesús “Chuy” García (D-Ill.), and Rashida Tlaib (D-Mich.).
That vote never occurred.
The House Rules Committee did not make the amendment in order for floor consideration, and before the House could begin debating the NDAA, the chamber failed to adopt the procedural rule governing consideration of the bill. As a result, no floor debate or recorded vote on Section 219 has taken place.
Massie has since said he intends to offer the amendment again when House consideration of the NDAA resumes.
For now, Section 219 remains in the House version of the NDAA.
But it represents only half of the legislative picture.
While the House has been considering expanded defense technology cooperation, the Senate has continued advancing a separate proposal focused on intelligence sharing.
Last month, The Salty Soldier reported on Section 622 of the Senate’s Intelligence Authorization Act, introduced by Sen. Tom Cotton (R-Ark.). The provision would expand intelligence sharing between the United States and Israel while establishing statutory procedures governing when a future president could reduce that cooperation.
Thirty days later, that language remains unchanged.
The Senate Intelligence Committee approved the bill in May, but the legislation has not yet received a vote before the full Senate. Like the House NDAA, it remains subject to amendment before any final version can become law.
Unlike Section 219, which focuses on defense technology and industrial cooperation, Section 622 addresses intelligence relationships.
Together, however, the two proposals would expand cooperation across two of the most sensitive areas of national security: military technology and intelligence.
The House and Senate proposals were developed independently.
Yet Congress’s own nonpartisan research arm now discusses them as part of the same broader legislative landscape.
In its July 2026 report, Israel: Major Issues and U.S. Relations, the Congressional Research Service (CRS) reviews both the House Defense Technology Cooperation Initiative and the Senate’s intelligence-sharing proposal alongside missile defense cooperation and other pending U.S.-Israel defense authorities.
CRS does not recommend whether Congress should approve the legislation.
Instead, its analysis places the proposals within a broader congressional effort to expand cooperation across defense technology, intelligence, missile defense, artificial intelligence, cybersecurity, manufacturing, and other emerging military capabilities.
Viewed through that lens, Section 219 and Section 622 appear less like isolated provisions and more like complementary pieces of a larger legislative approach to the U.S.-Israel security relationship.
Supporters view these proposals as strengthening one of America’s closest allies while improving U.S. military readiness.
Critics see a broader constitutional question.
Not simply whether the United States should cooperate with Israel—but who should decide how that relationship evolves in the future.
Historically, presidents have exercised broad discretion over foreign policy, allowing each administration to reassess intelligence relationships, defense cooperation, and diplomatic priorities as national interests and global conditions change.
Congress, however, also possesses constitutional authority to establish national policy through legislation.
The two bills approach that balance differently.
Section 219 establishes a framework for expanding defense technology cooperation but does not prevent a future administration from changing defense policy.
Section 622 goes further.
Rather than simply encouraging intelligence sharing, it would establish statutory procedures governing when a president may reduce that cooperation. Under the current language, a president seeking to suspend or limit intelligence sharing would generally need to determine that specific national security considerations justified the decision and notify Congress.
Supporters argue those requirements provide stability for an important intelligence partnership.
Critics argue they make it more difficult for future presidents to adjust that relationship should America’s strategic interests change.
That debate extends well beyond Israel.
Throughout his second administration, President Donald Trump has repeatedly argued that trade agreements, military alliances, defense commitments, and other international relationships should be continually evaluated according to whether they continue producing reciprocal benefits for the United States.
Whether one agrees with that philosophy or not, it raises an important policy question.
If trade agreements and defense partnerships are expected to demonstrate continuing value to the American people, should long-term intelligence and defense technology partnerships be evaluated under similar principles?
And if they should, who should make that determination?
Congress through permanent statutory frameworks?
Or future presidents exercising their constitutional authority over foreign policy?
Interestingly, Section 219 itself acknowledges the importance of demonstrating benefits to the United States.
The legislation requires the Department of War to publish periodic public updates explaining, to the maximum extent practicable, how the initiative contributes to United States technological and military supremacy while protecting classified information.
What it does not require is a recurring assessment of whether those benefits remain reciprocal over time or whether future administrations should reconsider the relationship if strategic circumstances evolve.
Whether Congress ultimately approves Section 219, Section 622, both, or neither remains uncertain.
The House and Senate must still complete their legislative work before negotiators reconcile any differences into a final package.
What has become clearer over the past month, however, is that the debate extends far beyond military installation names or what the Pentagon should be called.
Those debates concern the military’s identity.
Sections 219 and 622 concern its future mission.
Together they raise larger questions about how closely the United States should integrate with one of its closest allies, how permanent those relationships should become, and how much flexibility future presidents should retain to reassess them as America’s interests evolve.
Those are questions that deserve as much public attention as the culture-war debates that dominated the headlines.
© 2026 The Salty Soldier. All rights reserved. Reproduction without written consent is strictly prohibited.
