Changeflow GovPing Data Privacy & Cybersecurity FISA 702 Reauthorization Stalls in Congress as ...
Routine Notice Added Final

FISA 702 Reauthorization Stalls in Congress as Stopgap Expires April 30

Favicon for iapp.org IAPP Privacy News
Detected
Email

Summary

U.S. House Speaker Mike Johnson's attempts to secure a five-year reauthorization of FISA Section 702 surveillance authorities failed on April 17, 2026, when a coalition of 20 dissenting Republicans joined most Democrats to block the measure. Congress instead passed a 10-day stop-gap measure expiring April 30. Johnson subsequently released updated legislation titled the Foreign Intelligence Accountability Act, proposing a three-year reauthorization with reforms including monthly Civil Liberties Protection Officer reviews of U.S. person queries, attorney-level approval requirements replacing field supervisor approvals, and expanded congressional access to FISA Court proceedings.

“In the pre-dawn hours of 17 April, Johnson's attempts to facilitate a five-year reauthorization crumbled when a coalition of 20 dissenting Republicans joined most Democrats to block the reauthorization.”

IAPP , verbatim from source
Published by IAPP on iapp.org . Detected, standardized, and enriched by GovPing. Review our methodology and editorial standards .

About this source

GovPing monitors IAPP Privacy News for new data privacy & cybersecurity regulatory changes. Every update since tracking began is archived, classified, and available as free RSS or email alerts — 48 changes logged to date.

What changed

The article describes the failed Congressional vote on FISA Section 702 reauthorization and the introduction of new proposed legislation. The revised Foreign Intelligence Accountability Act would reauthorize Section 702 for three years (down from the failed five-year proposal) and includes reforms such as monthly civil liberties reviews by the Civil Liberties Protection Officer, attorney-level approval requirements for U.S. person queries, expanded congressional access to FISA Court proceedings, GAO technical audits, and strengthened criminal liability for FBI employees who knowingly violate querying procedures.

Technology companies operating under U.S. surveillance authorities should monitor ongoing FISA legislative developments, as enhanced oversight mechanisms and accountability requirements in proposed reforms could affect compliance obligations if enacted. Government contractors and entities subject to national security directives may face additional reporting and procedural requirements.

Archived snapshot

Apr 25, 2026

GovPing captured this document from the original source. If the source has since changed or been removed, this is the text as it existed at that time.


OPINION Published

24 April 2026

Subscribe to IAPP Newsletters

Contributors:

Cobun Zweifel-Keegan

CIPP/US, CIPM

Managing Director, D.C.

IAPP

Editor's note

The IAPP is policy neutral. We publish contributed opinion pieces to enable our members to hear a broad spectrum of views in our domains.

Around midnight last Thursday, things began to fall apart for U.S. House Speaker Mike Johnson, R-La. The embattled speaker had been gearing up to clear a familiar legislative hurdle but again found himself falling short on votes.

October will mark 25 years since the USA PATRIOT Act reformed the country's foreign intelligence authorities, adding controversial surveillance powers under Section 702 of the Foreign Intelligence Surveillance Act, with sunset provisions designed to make sure Congress would periodically reconsider whether the security benefits are worth the privacy tradeoffs.

At least six times since then, Congress has agonized over how and whether to extend the authorities, with legislative debates growing increasingly heated as the post-9/11 bipartisan consensus faded into history.

The actual contours of the law have evolved significantly over the decades. Much of FISA was made permanent in 2006, but the most controversial surveillance provisions continued to have expiration dates, a can for Congress to periodically kick down the road.

Each refrain of the FISA fight feels the same, but different. It is the same because it inevitably seems to draw to a last-minute crisis, with the intelligence community warning of disastrous consequences if it loses the authorities under Section 702. It is different because the political terrain shifts each time.

This time around, likely sensing the resistance from his Freedom Caucus wing of the Republican party, President Donald Trump put the stakes bluntly in a social media post, "I am willing to risk the giving up of my Rights and Privileges as a Citizen for our Great Military and Country."

As it happens, many House lawmakers were not so keen to make this tradeoff again. In the pre-dawn hours of 17 April, Johnson's attempts to facilitate a five-year reauthorization crumbled when a coalition of 20 dissenting Republicans joined most Democrats to block the reauthorization. As Punchbowl News put it, "On every issue in front of Congress, (Republicans seem) to be locked in a circular firing squad."

Instead, Congress passed a 10-day stop-gap measure, which expires 30 April, less than a week from today.

The coalition of legislators advocating for enhanced civil liberties protections under FISA make for strange bedfellows.

The far-right Freedom Caucus has focused its attention on calls for a warrant requirement, a reform that is viewed by congressional leadership and the intelligence committees as a fatal obstruction to the celerity of modern intelligence practices. Progressive Democrats and the Hispanic caucus, meanwhile, have been focusing more on the government's ability to acquire sensitive information from data brokers. This is likely a non-starter for Republicans. Like Hamlet, Johnson would rather bear those ills he has than fly to others that he knows not of.

The original Johnson-authored compromise attempted to introduce a new type of audit and a requirement for FBI attorney authorization for queries, but these were dismissed by reformers as fake warrants that merely codify the status quo without providing a substantive judicial check.

The updated text, released yesterday and titled the Foreign Intelligence Accountability Act, would reauthorize Section 702 for three years. The proposal includes targeted reforms to the provision that strengthen oversight and accountability.

For starters, the bill proposes a monthly civil liberties review of every U.S. person query by the Civil Liberties Protection Officer within the Office of the Director of National Intelligence, which can then be escalated to the inspector general. Additionally, instead of allowing field supervisors to approve U.S. person queries, the update requires attorney approval.

It also mandates an update to the Foreign Intelligence Surveillance Court procedures allowing for specified members of Congress and staff to have access to "any proceeding" of the court and the review court. The language seems similar to the requirement in the current 2024 reauthorization, the Reforming Intelligence and Securing America Act, which allowed access for top-level Congress members, but the new text explicitly requires revocation of the existing procedures, which suggests Congress feels obstructed in the current implementation.

The Comptroller General in the U.S. Government Accountability Office would also be given new authority to perform a technical audit of Section 702 targeting mechanisms to ensure, as implemented, they are "appropriately limiting" targeting "to non-United States persons located outside of the United States." The audit would result in a report to the intelligence committees within a year of enactment of the law. Finally, the bill would strengthen criminal liability for individual intelligence officers. FBI employees who "knowingly and willfully" violate querying procedures would face criminal prosecution.

Reportedly, the updated text has won some skeptics over.

Rep. Warren Davidson, R-Ohio, who wrote on social media, "Collectively, this set of reforms provides robust privacy protections for American citizens. Congress should bank this win and reauthorize Section 702. Then, we should swiftly begin gutting the unmitigated surveillance state left growing unchecked during these 702 fights."

Others remain unconvinced, including privacy-focused lawmakers like Sen. Ron Wyden, D-Ore., who extolled his colleagues not to "fall for fake reforms" in the new bill that amount to a "rubber stamp for Trump and Kash Patel to spy on Americans without a warrant," and Sen. Rand Paul, R-Ky., who reportedly will force the Senate to vote individually on a warrant amendment as a condition of agreeing to speed up consideration of the bill.

Rep. Scott Perry, R-Pa., who used to chair the Freedom Caucus, also said the bill still doesn't go far enough. "I didn't take an oath to defend FISA," he wrote on social media. "I didn't take an oath to defend the intelligence community."

Bipartisan negotiating threads to reauthorize Section 702 are sparse, but Rep. Jim Himes, D-Conn., is keeping the door open to brokering a deal for the sake of common sense.

"Three months from now, if FISA 702 is dark and there’s a bomb in Grand Central, there will be very little doubt in my mind … that that occurred because we shut down our most important counterintelligence,” Himes told Politico, adding he doesn't blame Democratic colleagues' opposition to a clean extension, but "I just see with some granularity — actually, more granularity than pretty much anybody around here — what the risks are that we face."

As with so much on the Hill these days, FISA reauthorization will come down to the wire. Meanwhile, the battles are illustrative for predicting the remainder of this Congressional term. The same political tensions between and among the parties are reflected in other tech policy debates, including on AI, privacy, and children’s protections.

The center cannot hold, and the fractures are multiplying.

Please send feedback, updates and compounding errors to cobun@iapp.org.


This article originally appeared in The Daily Dashboard and U.S. Privacy Digest, free weekly IAPP newsletters. Subscriptions to this and other IAPP newsletters can be found here.

This content is eligible for Continuing Professional Education credits. Please self-submit according to CPE policy guidelines.

Submit for CPEs

Contributors:

Cobun Zweifel-Keegan

CIPP/US, CIPM

Managing Director, D.C.

IAPP

Tags:

Law and regulation Surveillance U.S. federal regulation Privacy

Related Stories

### A view from DC: Can AI governance catch up to innovation? 17 April 2026

OPINION

### A view from DC: The federal plan to modernize — and preempt — financial privacy rules 10 April 2026

OPINION

### A view from DC: As chatbots go mainstream, new laws proliferate 27 March 2026

OPINION

### Notes from the IAPP Canada: The IAPP Canada Symposium 2026 is almost here 24 April 2026

OPINION

Get daily alerts for IAPP Privacy News

Daily digest delivered to your inbox.

Free. Unsubscribe anytime.

About this page

What is GovPing?

Every important government, regulator, and court update from around the world. One place. Real-time. Free. Our mission

What's from the agency?

Source document text, dates, docket IDs, and authority are extracted directly from IAPP.

What's AI-generated?

The summary, classification, recommended actions, deadlines, and penalty information are AI-generated from the original text and may contain errors. Always verify against the source document.

Last updated

Classification

Agency
IAPP
Instrument
Notice
Branch
Executive
Legal weight
Non-binding
Stage
Final
Change scope
Minor

Who this affects

Applies to
Technology companies Government agencies
Industry sector
5112 Software & Technology
Activity scope
Surveillance law compliance National security oversight Intelligence collection
Geographic scope
United States US

Taxonomy

Primary area
Data Privacy
Operational domain
Compliance
Compliance frameworks
GDPR CCPA/CPRA
Topics
National Security Sanctions

Get alerts for this source

We'll email you when IAPP Privacy News publishes new changes.

Free. Unsubscribe anytime.

You're subscribed!