Strengthening Surface Transportation Security

Defense & Security Economy & Labor Federal Workforce

In simple terms

This executive order designates the Secretary of Homeland Security as the lead federal official for surface transportation security, mandating development of a comprehensive sector-specific security plan, mode-specific annexes, risk assessments, and technology coordination to protect mass transit, rail, commercial vehicles, pipelines, and related infrastructure from terrorist attacks.

Federal Register Open PDF 71 FR 71033

Record & deadlines

Dec 5, 2006Signed
Signed by the President
Dec 7, 2006FR published
Published in the Federal Register · 71 FR 71033
Federal Register PDF
Jun 3, 2007
Identify high-risk modes and draft security guidelines/requirements
Jun 3, 2007
Establish and make available lists of available protective technologies
Mar 5, 2007
Mode-specific annexes due (90 days after sector plan completion)
Dec 31, 2006
Comprehensive transportation systems sector specific plan due

Key directives

Assess security of each surface transportation mode and evaluate current federal initiatives
Develop comprehensive transportation systems sector specific plan by December 31, 2006
Develop mode-specific annexes within 90 days of sector plan completion
Identify high-risk modes and draft security guidelines/requirements within 180 days of order date
Establish and publish lists of available protective technologies within 180 days of order date
Coordinate RDT&E for surface transportation security technologies
Use security grants to assist implementation

Who is ordered

Related orders

What to expect

Immediate

Secretary designated principal federal official for surface transportation security

Near term (90d)

Comprehensive transportation systems sector specific plan due by December 31, 2006
High-risk mode identification and draft security guidelines/requirements due within 180 days
Technology lists due within 180 days

Long term

Mode-specific annexes due 90 days after sector plan completion
Annual review protocols for information sharing mechanisms
Ongoing research and technology coordination

Risks & tensions

Extremely tight deadline for sector plan (26 days after signing) suggests possible reliance on pre-existing draft work
Voluntary vs. mandatory security measures tension: 'guidelines' are voluntary while 'requirements' are regulatory—unclear balance in final implementation
Coordination burden across federal, state, local, tribal, and private sector actors may create implementation friction
Subject to appropriations availability may limit grant-based implementation
Annex deadline depends on prior completion date of sector plan, creating cascading schedule uncertainty