Section 622 Would Lock US-Israel Intelligence Sharing Into Law — What It Means

A provision buried deep inside the Senate’s 2027 intelligence funding bill would mandate expanded intelligence sharing with Israel — and make it nearly impossible for any future president to say no.

When did Congress decide that a foreign government’s access to American intelligence should be harder to revoke than a presidential pardon? That question is no longer hypothetical. It is the precise legal architecture that Section 622 of the Intelligence Authorization Act for Fiscal Year 2027 is designed to build — and most Americans have no idea it exists.

The bill, introduced by Senator Tom Cotton (R-Ark.) on May 20, 2026, was approved by the Senate Intelligence Committee and placed on the Senate calendar. It has bipartisan support and is expected to pass by the end of the year. Yet the provision at its center has received almost no scrutiny from major media outlets, despite raising fundamental questions about executive authority, counterintelligence risk, and the limits of congressional power.

What Does Section 622 Actually Say?

The provision is titled “United States-Israel Intelligence Sharing Enhancement.” It would require the president, acting through the Director of National Intelligence and, when necessary, the Secretary of Defense, to “expand and enhance intelligence sharing with the Government of Israel.” The list of subjects covered is sweeping: cybersecurity threats, terrorism, sanctions evasion, missile proliferation, unmanned systems, air and space domain awareness, and adversarial technology — encompassing, by most readings, virtually every major intelligence priority in the Middle East.

Crucially, Section 622 would amend the National Security Act of 1947 itself by inserting a new Section 1115. That is not a policy memo. That is statute. Any president wishing to reduce, suspend, or limit intelligence sharing under this mandate would need to identify “a specific and identifiable national security concern” — and then file a report to Congress within fifteen days, detailing not only the reason but also the specific categories of intelligence withheld and the anticipated regional security impact.

When intelligence sharing with a foreign government becomes harder to stop than a war authorization, Americans should ask who is really running U.S. foreign policy.

Is This a Security Partnership — or a One-Way Street?

Here is a detail supporters rarely mention. Neither Section 622 nor its companion provision in the House — Section 224 of the FY 2027 National Defense Authorization Act — requires Israel to provide reciprocal access to its intelligence, technology, or software as a condition of expanded cooperation. There is no certification requirement. No benchmarks. No conditions tied to resolving past disputes over technology access.

Those omissions matter. Israel negotiated unique accommodations within the F-35 program that were unavailable to many other foreign operators. There have been documented disputes over access to source code and other sensitive systems. Section 622 sweeps all of that aside. It mandates American generosity without requiring Israeli reciprocity. In any other context, Congress would call that a bad deal.

A law that mandates what America gives and says nothing about what America receives is not a security partnership — it is a subsidy.

“If the president of the United States cannot restrict intelligence sharing with a foreign government without filing a fifteen-day report to Congress justifying every category of information withheld, who exactly is in charge of American national security?”

What Are the Counterintelligence Risks?

The timing of Section 622 is difficult to ignore. The provision was advancing through committee at the same moment the Pentagon’s Defense Intelligence Agency elevated its counterintelligence threat assessment for Israel to “critical” — the highest possible designation. That assessment reflects a documented and serious concern within U.S. defense and intelligence agencies about Israeli espionage directed at American officials and classified material.

The most notorious historical case is Jonathan Pollard, a U.S. Naval intelligence analyst who transferred large volumes of classified material to Israel. American officials described the damage as severe. Israel honored Pollard as a hero upon his release. Section 622 contains no new counterintelligence conditions beyond a general reference to protecting “sources and methods.” It does not address the DIA’s elevated threat designation. It does not require Israel to resolve past disputes as a condition of expanded access.

$81.9 billion. That is the National Intelligence Program budget for FY 2026, per the Director of National Intelligence. The question Section 622 forces Americans to ask: how much of that is now effectively promised to a foreign government by statute? [federal disclosure, DNI public statement, June 2025]

Who Benefits — and Who Pays the Price?

Congress has a legitimate role in setting foreign policy frameworks. No reasonable person disputes that. The United States and Israel share genuine strategic interests, and intelligence cooperation between allies is not inherently controversial. What is controversial is converting that cooperation from an executive-discretion arrangement into a statutory mandate — removing the president’s routine flexibility to manage counterintelligence exposure in real time, in response to facts on the ground that Congress cannot always anticipate.

The fifteen-day reporting requirement sounds like accountability. In practice, it functions as a political enforcement mechanism. Any president who attempts to recalibrate the relationship — even in response to a confirmed espionage case — will face immediate organized opposition in Congress, armed with the specific details of what was withheld. That is not oversight. That is a tripwire.

What Do Supporters of This Policy Actually Believe?

Supporters of Section 622 argue, not without foundation, that intelligence cooperation with Israel has produced concrete benefits for American national security. Israel has provided intelligence on Iranian nuclear activities, Hezbollah operations, and regional missile threats. The bill’s preamble states that sharing has “saved United States personnel and property in the region.” Proponents contend that formalizing the relationship through statute provides stability and signals to adversaries that the partnership cannot be easily disrupted.

That argument deserves a serious response. Strategic stability matters. Adversaries do probe alliances for breakpoints, and ambiguity can invite miscalculation. These are legitimate considerations. But they do not answer the core objection, which is not whether to share intelligence with Israel — it is who gets to decide how much, when, and under what conditions. Embedding that decision in statute, with a reporting mechanism designed to impose political costs on any deviation, does not strengthen American security. It weakens American sovereignty. The executive branch exists precisely because foreign policy requires the kind of real-time, fact-specific judgment that legislation cannot provide. Section 622 does not enhance the partnership. It handcuffs the partner responsible for American interests.

Is Congress Giving Away Power It Was Never Meant to Hold?

There is a constitutional irony at the center of this debate that has received almost no attention. Congress has, in recent decades, surrendered significant portions of its own authority — over trade, over war powers — to the executive branch. Section 622 runs in the opposite direction, with Congress using legislation to micromanage an intelligence relationship in a domain that by its nature demands executive flexibility, secrecy, and adaptability. The result is the worst of both worlds: congressional interference in a domain it cannot fully see, combined with a mechanism that locks future executives into a political trap.

What kind of Congress strips the president’s flexibility to protect American secrets — while simultaneously demanding a fifteen-day briefing if he tries to take it back?

This is not a partisan issue. Critics of Section 622 include voices from across the political spectrum who share a single, simple concern: American intelligence should serve American interests, managed by American officials accountable to the American people — not locked into a statutory arrangement with a foreign government that the DNI cannot adjust without a congressional report.

The Question That Demands an Answer

Section 622 is not a headline. It is 192 pages into a funding bill, past the sections on Chinese product limitations, biological intelligence, and Indo-Pacific cooperation. It was approved in committee without the public debate it deserves. It is expected to pass before the end of 2026.

The real question is not whether intelligence cooperation with Israel is valuable. It is whether any foreign government’s access to American secrets should be written into the National Security Act of 1947 in a way that strips the executive branch of the flexibility it needs to protect the American people — and whether voters are going to find out about it before it becomes law.

The question Americans should be asking their senators right now is the one Washington has not yet answered: when did protecting a foreign government’s access to American intelligence become more important than protecting the Americans who generated it?

Key Questions This Story Raises

1. If the DIA has elevated Israel’s counterintelligence threat to “critical,” why does Section 622 contain no new counterintelligence conditions for expanded sharing?
2. Why does neither Section 622 nor its House companion require Israel to provide reciprocal intelligence or technology access as a condition of the mandate?
3. What does it mean for American sovereignty when a future president must file a congressional report — detailing every category of intelligence withheld — before restricting a foreign government’s access to American secrets?

Think others need to hear about this? Share the article and join the conversation. Still have questions? Subscribe to The Town Hall for daily coverage of the stories Washington hopes you miss. Want to make your voice count? Contact your senator directly at senate.gov and ask where they stand on Section 622 of S.4615.