Pipeline Security Act
Summary
What This Bill Does
This bill assigns the Transportation Security Administration continuing responsibility for securing pipeline transportation and pipeline facilities against cybersecurity threats, terrorism, and other security threats. TSA must consult with the Cybersecurity and Infrastructure Security Agency when appropriate and carry out guideline, directive, regulatory, and information-sharing work for pipeline security.
TSA must develop and update pipeline security guidelines in consultation with relevant federal, state, local, Tribal, and territorial entities plus public and private stakeholders. Those guidelines must be consistent with the NIST Cybersecurity Framework. TSA may promulgate additional security directives or regulations when needed, and it must share guidelines, directives, regulations, and threat information with relevant government and private-sector actors as appropriate. The bill turns pipeline security responsibilities into explicit statutory duties rather than leaving them mainly to administrative practice.
Who Benefits and How
TSA pipeline security staff benefit from clear statutory ownership of pipeline transportation and facility security. CISA pipeline cybersecurity staff benefit from an express consultation role. Pipeline operators benefit from clearer federal responsibility and NIST-aligned guidance, even though they may face more directives. State pipeline security officials and Tribal emergency-management offices benefit from information sharing and consultation. Pipeline cybersecurity vendors benefit if operators need help meeting updated guidelines, directives, or regulations. Energy consumers benefit indirectly if better pipeline security reduces cyber, terrorism, or physical disruption risk.
Who Bears the Burden and How
Pipeline operators must monitor TSA guidelines, security directives, regulations, and information-sharing requests. TSA rulemaking and inspection staff must develop guidelines, update them, consult with other agencies, issue directives where needed, and share threat information. CISA coordination staff must support consultation on cybersecurity threats. State, local, Tribal, and territorial officials must participate in consultation or information-sharing channels. Smaller pipeline operators may face compliance costs if TSA issues additional security directives or regulations.
Key Provisions
- Establishes TSA responsibility for securing pipeline transportation and pipeline facilities against cybersecurity, terrorism, and other security threats.
- Requires TSA consultation with CISA when appropriate.
- Requires development and updating of NIST Cybersecurity Framework-consistent pipeline security guidelines.
- Authorizes TSA to promulgate additional pipeline security directives or regulations.
- Directs TSA to share guidelines, directives, regulations, and threat information with relevant government and private-sector stakeholders.
Evidence Chain:
This summary is generated from the full bill text using AI analysis. Expand "Detailed Analysis" below for identified beneficiaries/burden bearers with clause-level evidence links.
At a Glance
What This Bill Does
Codifies TSA responsibility for securing pipeline transportation and pipeline facilities against cybersecurity, terrorism, and other security threats, while requiring consultation with CISA and sharing of NIST-aligned guidelines, directives, regulations, and intelligence with government and private-sector stakeholders.
Key Policy Areas
Pipeline Security, Cybersecurity, Transportation, Homeland Security, Critical Infrastructure
Primary Purpose
Codifies TSA responsibility for securing pipeline transportation and pipeline facilities against cybersecurity, terrorism, and other security threats, while requiring consultation with CISA and sharing of NIST-aligned guidelines, directives, regulations, and intelligence with government and private-sector stakeholders.
Policy Domains
House resolution provisions
Identified Gains
- TSA pipeline security staff
- CISA pipeline cybersecurity staff
- Pipeline operators
- State pipeline security officials
- Tribal emergency-management offices
- Pipeline cybersecurity vendors
- Energy consumers
Identified Costs
- Pipeline operators
- TSA rulemaking staff
- TSA inspection staff
- CISA coordination staff
- State officials receiving pipeline security information
- Local officials receiving pipeline security information
- Tribal officials receiving pipeline security information
- Smaller pipeline operators
Sponsors
Legislative Progress
ReportedCommitted to the Committee of the Whole House on the …
Placed on the Union Calendar, Calendar No. 327.
Reported by the Committee on Homeland Security. H. Rept. 119-376.
Subcommittee on Transportation and Maritime Security Discharged
Ordered to be Reported by the Yeas and Nays: 22 …
Committee Consideration and Mark-up Session Held
Introduced in House
Referred to the Subcommittee on Transportation and Maritime Security.
Referred to the House Committee on Homeland Security.
Ms. Johnson of Texas (for herself, Mr. Gimenez, and Mr. …
Stakeholder Effects
cui bono?How this legislation distributes effects. Mention counts reflect frequency, not effect magnitude.
CISA pipeline cybersecurity staff, State pipeline security officials, TSA pipeline security staff
Bill Structure & Actor Mappings
Who is "The Secretary" in each section?
- "tsa"
- → Transportation Security Administration
- "cisa"
- → Cybersecurity and Infrastructure Security Agency
- "nist"
- → National Institute of Standards and Technology
We use a combination of our own taxonomy and classification in addition to large language models to assess meaning and potential beneficiaries. High confidence means strong textual evidence. Always verify with the original bill text.
Learn more about our methodology