The bill requires the Secretary of Homeland Security to establish, within one year of enactment, a pilot program (lasting no more than one year) to reduce and mitigate terrorist uses of motor vehicles. The pilot directs DHS—working with the automotive sales and rental sectors—to develop a uniform standard for what rental and dealer firms collect and how they submit suspicious activity reports (SARs), to deliver a terrorism threat assessment focused on large vehicles, and to provide guidance, training, and technical assistance to operators.
The statute also authorizes the Secretary to set up a procedure to check information against a non‑classified, designated watch list and to require dealers and rental companies to notify the FBI of a sale or rental if the Secretary deems that necessary. It requires periodic reporting to Congress (every 120 days during the pilot) including a privacy and civil liberties assessment, directs an 18‑month study on working with rental and ride‑share companies, and shields dealers and rental companies from liability for actions taken under the pilot.
For compliance officers and security planners, the bill signals possible new operational standards and information‑sharing obligations for the rental sector, while raising practical and privacy tradeoffs that DHS would have to manage during implementation.
At a Glance
What It Does
Mandates a DHS pilot—set up within one year and limited to one year—that creates a uniform information‑collection standard for dealers and rental companies, issues a vehicle‑focused terrorism threat assessment, and supplies SAR guidance, training, and technical assistance. The Secretary may also deploy a non‑classified watch list check and require FBI notice of certain sales or rentals if needed.
Who It Affects
Primarily rental companies and vehicle dealers (as defined in 49 U.S.C. 30102) that handle large vehicles—defined in the bill as trucks, buses, trailers, semitrailers, tractors and vans capable of carrying more than 15 passengers—plus DHS components (Undersecretary for Intelligence and Analysis, TSA) and law enforcement partners who would receive notices or access to SARs.
Why It Matters
This creates a formal, DHS‑led operational engagement with the rental/dealer sector that could standardize suspicious‑activity reporting and create new notification flows to the FBI. The pilot’s liability shield, prescribed reporting cadence to Congress, and the optional watchlist check make it a testing ground for broader policy changes affecting industry practices, privacy safeguards, and interagency intelligence handling.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill directs the Secretary of Homeland Security to stand up a time‑limited pilot aimed at preventing terrorism carried out with motor vehicles. DHS must do this within one year of the law taking effect and may run the pilot for up to a year.
The pilot’s core deliverables are practical: work with automotive sellers and renters to agree on what data those businesses should collect, standardize the kinds of information that feed into suspicious activity reports, and provide training and technical help so designated employees can identify and report concerns consistently.
Operationally, the statute assigns the Undersecretary for Intelligence and Analysis to prepare a specific threat assessment about large vehicles and requires DHS and TSA to jointly report to Congress every 120 days about how the pilot is working. Those recurring reports must include a privacy and civil liberties assessment and an analysis of what permanent implementation would mean for U.S. counter‑terrorism efforts.
Separately, DHS must deliver a study within 18 months on how to collaborate with rental and ride‑share providers (including peer‑to‑peer platforms) to detect risks and threats.Two implementation levers in the bill are discretionary: the Secretary may establish a procedure to check submitted information against a designated watch list that excludes classified entries, and may require dealers and rental companies to notify the FBI of a sale or rental when the Secretary determines it is necessary. The statute also provides a statutory liability exemption for dealers and rental companies for actions taken in accordance with the pilot, and it defines the vehicles in scope—commercial‑type vehicles or vans and buses capable of carrying more than 15 passengers—using standard statutory definitions for dealer and rental company.Taken together, the bill converts a policy concern—vehicle‑as‑weapon attacks—into a manageable test of standardized data collection, reporting pathways, training, and limited screening.
It places DHS at the center of designing operational rules in close consultation with industry while requiring Congress to receive frequent updates on privacy impacts and the practical effect of making any of these measures permanent.
The Five Things You Need to Know
DHS must establish the pilot within one year of enactment and may run it for no longer than one year.
The pilot requires DHS to develop, in consultation with automotive sales and rental representatives, a uniform standard for what rental/dealer firms collect and how suspicious activity reports are formatted.
The Secretary may set up a procedure to check information against a designated, non‑classified watch list and to require dealers or rental companies to notify the FBI of a sale or rental if DHS deems it necessary.
DHS and TSA must jointly report to Congress every 120 days during the pilot, and those reports must include a privacy and civil liberties assessment and an assessment of what permanent implementation would mean.
Dealers and rental companies are statutorily shielded from liability for any action taken in accordance with the pilot, and the bill specifically scopes covered rental vehicles to those capable of transporting more than 15 passengers.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Create a uniform data standard with industry
This subsection requires DHS to consult automotive sale and rental industry representatives to design a uniform standard for the type of information rental agencies collect and the information used in suspicious activity reporting. Practically, that means DHS would lead inter‑industry negotiations over the fields, formats, and retention practices for rental/dealer records and SAR inputs—material decisions that will affect back‑end IT, training, and recordkeeping burdens for firms.
Threat assessment, SAR guidance, training and technical assistance
DHS must provide an intelligence product from the Undersecretary for Intelligence and Analysis focused on large‑vehicle threats, and distribute operational guidance to improve SAR submission and train designated employees. The agency must also give technical assistance so operators can access and use SARs. These clauses impose no statutory penalties but create expectations for DHS to produce usable analytical and implementation resources for private operators.
Optional watch list checks and FBI notice authority
If the Secretary decides it is necessary, she may create a process to compare information against a designated watch list that explicitly excludes classified entries, and may require dealers and rental companies to provide notice of a sale or rental to the FBI. The provision vests significant discretion in DHS about whether to deploy these screening and notification tools, making the pilot’s operational footprint dependent on agency judgment rather than automatic statutory triggers.
Reporting cadence and the scope of required reports
DHS and TSA must jointly submit reports to Congress every 120 days after the pilot is established and until it concludes. Each report must assess privacy and civil liberties impacts and describe the implications of making the pilot permanent. Separately, DHS must complete an 18‑month study on collaboration models with rental car and ride‑share companies, including peer‑to‑peer platforms; that study should surface legal, technical, and business barriers to broader implementation.
Liability shield and definitions
The bill bars civil liability for dealers and rental companies for actions taken in accordance with the pilot and defines ‘covered rental vehicle’ to include trucks, trailers, buses, semitrailers, tractors and vans capable of transporting more than 15 passengers. By pairing a liability exemption with narrow vehicle scope, the bill reduces legal risk for participating firms while concentrating the pilot on larger commercial vehicles.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Large rental companies and commercial vehicle dealers — receive DHS threat products, training and technical assistance, plus a liability shield for actions taken under the pilot, reducing legal exposure for compliance efforts.
- Federal law enforcement and intelligence components (FBI, DHS components, TSA) — gain standardized reporting formats, possible notification streams, and a focused pilot to test intelligence‑to‑operator workflows for vehicle‑based threats.
- Event and venue security planners and public transit agencies — stand to benefit indirectly if the pilot improves early detection of risks tied to large vehicles used near mass gatherings or transit hubs.
Who Bears the Cost
- Small and medium rental companies and independent dealers — will likely face the largest operational and compliance costs to change data collection, staff training, and IT systems to meet any new uniform standard.
- DHS and TSA — must allocate personnel and analytic resources to produce the threat assessment, manage industry consultations, provide technical assistance, and deliver recurrent congressional reports and the 18‑month study.
- Riders, renters and the public — face potential increased screening, data collection and information sharing with federal agencies, with attendant privacy and false‑positive risks; communities may also see disproportionate impacts if guidance is unevenly applied.
Key Issues
The Core Tension
The central dilemma is whether expanding standardized data collection, screening and notification in the name of preventing vehicle‑based attacks will materially reduce risk without creating excessive surveillance, discrimination, and operational burdens—especially given that the bill vests substantial discretion in DHS and shields participating firms from liability, potentially trading accountability for faster deployment.
The bill centralizes much of the pilot’s design in DHS’s discretion—whether to implement watch list checks, what the uniform data standard looks like, and when FBI notification is necessary. That discretion allows flexibility but means the pilot’s scope and civil‑liberties footprint will depend heavily on non‑statutory choices: what data fields are included, how long records are retained, who within firms can access SAR systems, and how false positives are handled.
The liability exemption reduces litigation risk for industry but also reduces external pressure on DHS to calibrate safeguards; absent robust oversight, firms could act on poor guidance with limited recourse for harmed individuals.
Operational questions remain unresolved by the text. The bill requires an 18‑month study on ride‑share collaboration, but it does not set funding, interoperability standards, or timelines for implementing any recommendations.
The pilot’s one‑year limit may be too short to evaluate long‑tail privacy harms, measure false‑positive rates, or assess whether watch list checks materially reduce risk. Finally, the bill does not specify mechanisms to prevent profiling or discrimination stemming from broadened SAR collection—an implementation gap that will determine whether the pilot improves security without imposing unfair burdens on particular communities.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.