119-HR-7272 Journalist Public Summary

Headline Summary

A bipartisan proposal would task the Department of Energy with coordinating pipeline and LNG facility cybersecurity and physical security—developing voluntary tools, running pilot projects, and helping lead incident response; it was introduced on January 27, 2026 and referred to the House Energy & Commerce Committee. (congress.gov)

What It Does

In plain terms, the bill tells DOE to help keep oil and gas pipelines and LNG facilities safer from hacks and physical attacks. It would set up a program to improve government–industry coordination, build optional cybersecurity tools and technologies, run demonstration projects, develop training, and support joint response and recovery when incidents occur. It does not change other agencies’ legal powers (like TSA’s or PHMSA’s); DOE’s role would be to coordinate and assist as the Energy Sector’s risk‑management lead. (energy.gov)

Why it matters: Cyber incidents like the 2021 Colonial Pipeline attack showed how a single breach can disrupt fuel supplies and daily life. The bill aims to reduce that risk by tightening coordination and giving operators more voluntary tools to harden their systems. (energy.gov)

Who’s For It

• Sponsors: Rep. Randy Weber (R‑TX) introduced the bill with Rep. Debbie Dingell (D‑MI) as the listed cosponsor—an early bipartisan signal. (congress.gov)
• Committee interest: House Energy & Commerce leaders scheduled and held a January 13, 2026 hearing on a package that included this measure, indicating majority attention to moving it. (energycommerce.house.gov)
• Industry precedent: Pipeline trade groups (AGA, INGAA) backed substantially similar “Pipeline and LNG Facility Cybersecurity Preparedness Act” language in a prior Congress, praising DOE coordination and the bill’s non‑regulatory, voluntary approach; while not a formal endorsement of today’s bill, it signals likely themes of support. (ingaa.org)

Who’s Against It

• No organized opposition is publicly documented yet. However, critics of similar efforts often worry about duplicating or blurring existing authorities—since TSA already issues pipeline cyber requirements and CISA runs a pipeline cybersecurity initiative. (tsa.gov)
• Oversight concerns: GAO has repeatedly urged clearer roles and up‑to‑date plans for pipeline security, highlighting the risk of fragmented responsibilities—an argument some may cite against layering on new programs without strict guardrails. (gao.gov)

What’s Next

Status: Introduced on January 27, 2026 and referred to the House Energy & Commerce Committee. The subcommittee has already held a related hearing; next steps would typically be a subcommittee markup, full committee vote, and then possible House floor consideration. (congress.gov)