HB5062, the Pipeline Security Act, would amend the Implementing Recommendations of the 9/11 Commission Act of 2007 to formally place responsibility for pipeline transportation and pipeline facility security with the Transportation Security Administration (TSA). The bill directs TSA, in consultation with the Cybersecurity and Infrastructure Security Agency as appropriate, to secure pipelines against cybersecurity threats, terrorism, and other security threats. It also requires TSA to develop and update security guidelines aligned with the NIST Cybersecurity Framework, issue additional directives or regulations as needed, share threat information with government and industry stakeholders, assess and inspect compliance, rank security risks, and inspect critical pipeline assets.
The bill further requires TSA to hold at least one industry day within a year to engage pipeline stakeholders, report to relevant House and Senate committees at least every two years on its pipeline security activities, and develop a personnel strategy within 180 days to ensure it has the cybersecurity expertise and resources needed to carry out these responsibilities. A Government Accountability Office review would be required two years after enactment. The bill also makes a clerical amendment to the 9/11 Act’s table of contents to add a new section on pipeline security.
If enacted, the bill would codify and expand TSA’s statutory role in pipeline security within federal homeland security law, specifically by adding a new section to the 9/11 Commission Act. It would create ongoing federal obligations for guidance, inspections, information sharing, risk ranking, workforce planning, congressional reporting, and GAO oversight, while affecting pipeline owners and operators that would be subject to TSA guidelines, directives, inspections, and potential regulatory requirements. The bill would also reinforce coordination with CISA and reference the NIST cybersecurity framework as a benchmark for pipeline security practices.
Based on the bill text and available context, the measure appears to have a generally supportive and bipartisan framing, with introduction by members from both parties and no recorded committee opposition or votes in the provided materials. The bill is presented as a homeland security and critical infrastructure protection measure, suggesting a consensus-oriented approach focused on strengthening pipeline cybersecurity and physical security. No committee transcript is available, so there is no recorded debate to indicate broader controversy in the provided record.
The main policy issue embedded in the bill is the scope of TSA’s authority over pipeline security and how much regulatory and inspection responsibility should be centralized at TSA versus coordinated with CISA and other stakeholders. Pipeline owners and operators may be concerned about new directives, inspections, reporting expectations, and compliance costs, while security advocates are likely to favor clearer federal authority and stronger oversight. Because no committee discussion or votes are provided, there is no documented opposition in the record, but the likely points of contention would center on federal oversight, industry burden, and the balance between cybersecurity standards and operational flexibility.