H.R. 5062 (119th)Bill Overview

Pipeline Security Act

Transportation and Public Works|Administrative law and regulatory proceduresComputer security and identity theft
Cosponsors
Support
Lean Democratic
Introduced
Aug 29, 2025
Discussions
Bill Text
Current stageCommittee

Ordered to be Reported by the Yeas and Nays: 22 - 0.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

This bill amends the Implementing Recommendations of the 9/11 Commission Act of 2007 to assign and codify responsibility for securing pipeline transportation and pipeline facilities to the Transportation Security Administration (TSA), in consultation with the Cybersecurity and Infrastructure Security Agency (CISA). It directs TSA to develop and update cybersecurity and security guidelines consistent with the NIST Cybersecurity Framework, promulgate directives or regulations as needed, share information with relevant stakeholders, assess and inspect implementation by owners and operators, and identify and rank security risks.

Why people may split

Scope and scale of federal authority: liberal and centrists view accept expanded federal leadership; conservative view sees mission creep and prefers limited federal intervention.

Watch point

Relative to its intended legislative type, this bill clearly assigns and codifies administrative responsibilities to TSA for pipeline physical and cybersecurity, provides multiple operational mechanisms and near-term deadlines, integrates with existing statutes and standards, and establishes oversight through reporting and GAO review.

This bill amends the Implementing Recommendations of the 9/11 Commission Act of 2007 to assign and codify responsibility for securing pipeline transportation and pipeline facilities to the Transportation Security Administration (TSA), in consultation with the Cybersecurity and Infrastructure Security Agency (CISA).

It directs TSA to develop and update cybersecurity and security guidelines consistent with the NIST Cybersecurity Framework, promulgate directives or regulations as needed, share information with relevant stakeholders, assess and inspect implementation by owners and operators, and identify and rank security risks.

The Administrator must convene at least one industry day within one year, produce a personnel strategy within 180 days addressing cybersecurity expertise and resource needs, and report at least biennially to relevant congressional committees.

Passage60/100

On content alone, this is a focused, technical security bill that codifies and clarifies federal responsibility and contains oversight and consultative features—characteristics that favor enactment. The absence of explicit new funding and the potential for industry pushback or competing jurisdictional claims (e.g., DOT/PHMSA roles) are the main barriers. If kept narrow and non-controversial in any further amendments, it has a reasonably high chance of passage.

CredibilityPartially aligned

Relative to its intended legislative type, this bill clearly assigns and codifies administrative responsibilities to TSA for pipeline physical and cybersecurity, provides multiple operational mechanisms and near-term deadlines, integrates with existing statutes and standards, and establishes oversight through reporting and GAO review. It leaves important implementation details—funding, enforcement authority, detailed inspection protocols, and safeguards for information sharing—largely to subsequent rulemaking or agency discretion.

Contention55/100

Scope and scale of federal authority: liberal and centrists view accept expanded federal leadership; conservative view sees mission creep and prefers limited federal intervention.

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agenciesFederal agencies

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Federal agenciesCentralizing responsibility at TSA with CISA consultation could improve federal coordination, standardize cybersecurity…
  • Potential benefitImplementation of NIST-aligned guidelines, inspections, and directives could reduce the likelihood of successful cybera…
  • Federal agenciesNew TSA responsibilities and the required personnel strategy may spur hiring of cybersecurity and security specialists…
Likely burdened
  • Potential burdenOperators (especially smaller companies) could face increased regulatory compliance costs from new directives, inspecti…
  • Federal agenciesThe statute centralizes federal authority for pipeline security at TSA and could create duplication or jurisdictional f…
  • Federal agenciesTSA implementation will require funding, staffing, and technical expertise; absent explicit appropriations in the bill,…
03 · Why people split

Why the argument around this bill splits.

Scope and scale of federal authority: liberal and centrists view accept expanded federal leadership; conservative view sees mission creep and prefers limited federal intervention.
Progressive80%

A mainstream liberal/left-leaning observer would likely view this bill positively as a concrete federal step to strengthen cybersecurity and physical protection of critical energy infrastructure.

They would appreciate codifying TSA responsibilities, use of NIST standards, information-sharing provisions, and required oversight reports and GAO review.

They would watch for whether the bill includes adequate resources, transparency, labor protections, and civil liberties safeguards during inspections and information-sharing.

Leans supportive
Centrist65%

A centrist/moderate observer would generally view the bill as a pragmatic step to fill a gap in federal responsibility for pipeline security, but would be attentive to implementation, costs, and institutional coordination.

They would welcome use of NIST guidance and required reporting, while wanting clarity about how TSA’s new responsibilities will coordinate with CISA, PHMSA, and state regulators.

They would also be cautious about unfunded mandates or mission creep and would favor measurable metrics, timelines, and cost estimates.

Split reaction
Conservative30%

A mainstream conservative observer would be wary of expanding TSA’s role into pipelines, viewing this as potential federal overreach and mission creep for an agency historically focused on transportation security checkpoints and aviation.

They would be concerned about increased regulatory burdens on energy infrastructure, possible compliance costs passed to consumers, and duplication with CISA, PHMSA, or state regulators.

At the same time, they would acknowledge the need to protect critical infrastructure from real security threats, so an approach that minimizes new regulations and respects industry and state roles could be acceptable.

Likely resistant
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood60/100

On content alone, this is a focused, technical security bill that codifies and clarifies federal responsibility and contains oversight and consultative features—characteristics that favor enactment. The absence of explicit new funding and the potential for industry pushback or competing jurisdictional claims (e.g., DOT/PHMSA roles) are the main barriers. If kept narrow and non-controversial in any further amendments, it has a reasonably high chance of passage.

Scope and complexity
52%
Scopemoderate
24%
Complexitylow
Why this could stall
  • No explicit appropriation or funding mechanism is included; whether Congress will fund TSA to fulfill new responsibilities is uncertain and could affect implementation feasibility and support.
  • Interaction with existing authorities (e.g., Department of Transportation/PHMSA regulation of pipelines) is not detailed; overlaps or disputes over jurisdiction could generate opposition or require additional legislative clarification.
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Scope and scale of federal authority: liberal and centrists view accept expanded federal leadership; conservative view sees mission creep a…

On content alone, this is a focused, technical security bill that codifies and clarifies federal responsibility and contains oversight and…

Unlocked analysis

Relative to its intended legislative type, this bill clearly assigns and codifies administrative responsibilities to TSA for pipeline physical and cybersecurity, provides multiple operational mechanisms and near-term de…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis