Security and the National ITS Architecture

1. Architecture Development Team Security and the National ITS Architecture ITS America 2003 Session 19: The State of the Practice: ITS and Homeland Security May 19, 2003 Minneapolis, MN

2. Security Update • Enhance Coverage of Security in the National ITS Architecture • Nine areas of functionality identified and presented to US DOT • Cut across multiple user service areas • Better reflect the opportunities for security applications in planning ITS • Regional and Project Architecture development • Standards development

3. ITS Security Areas • Using ITS to Enhance Surface Transportation Security • Transit Security • Rail Security • Freight and Commercial Vehicle Security • HAZMAT Security • Disaster Response and Evacuation • Wide Area Alert • Critical Infrastructure Security • Includes functions for Traveler Security • Securing ITS

4. Transit Security • Use ITS to help secure passengers, facilities, and assets of • Bus transit systems • Rail transit systems • Many aspects of transit security already exist in Version 4.0 • Video surveillance at stops/ stations • Response to emergencies • On board transit vehicle • At transit stop/ station • Transit traveler information

5. Transit Security • Added Security functionality • Surveillance and Sensor Monitoring • On-Board Transit Vehicles • Stations • Facilities (e.g. yards, shops) • Infrastructure (Rail Track, Tunnel, Bridge, Guideway, etc.) • Remote Vehicle Disable • Vehicle Operator Authentication • Use of Transit to Support Disaster Response and Evacuation

6. Rail Security • Full scope of Rail Security includes using ITS to address Freight Rail Security for • Trains • Rail Car • Fixed Assets (e.g. track, wayside equipment, highway/rail crossings) • Personnel • However, Version 5 architecture will add only • Rail Interface for Emergency Services • Update Incident Management User Service Requirements

7. Freight & CommercialVehicle Security • Use ITS to enhance security of Freight and Commercial Vehicle shipments • Tracking Commercial Vehicles and Freight shipments • Monitoring Freight Integrity • Monitoring Commercial Vehicle Integrity • Monitoring Assignment Integrity • CV Driver/Commercial Vehicle/Freight Equipment

8. HAZMAT Security • Use ITS to Secure Commercial Vehicles carrying HAZMAT • Detect Diversions and Geofence Violations • Safely Disable Vehicle / Public Safety Traffic Stop • Roadside Remote Sensing of HAZMAT Cargo • Correlate with permitted activity • Pull-In/Public Safety Traffic Stop • Authenticate Drivers • Safely Disable Vehicle / Public Safety Traffic Stop

9. HAZMAT Security • Institutional Elements • Deployments will likely limit service to Security Sensitive HAZMAT (e.g. gasoline, not nail polish) • CV Tracking and Driver Authentication • Monitored by CV Dispatch function • Private Fleet and Freight Management, NOT a Government Agency • Police (Emergency Management) notified when FMS detects/validates significant route deviation, geofence boundary violation, or apparent hijacking • Remote disabling of vehicle by Fleet and Freight Management

10. Disaster Responseand Evacuation • Use ITS to Enhance Response to All Disasters, Natural and Man-Made • Work Within Existing Emergency Response Framework • Existing Institutional Relationships, Roles, and Responsibilities • Define Scope to Focus on Transportation and Interface to Emergency Management/Public Safety • Existing Incident Management User Service/Architecture Support Provide Starting Point

11. Coordinate Response Plans Monitor Alert Levels Detect and Verify Emergency Assess Infrastructure Status Manage Area Transportation Critical Service Restoration Coordinate Response Disaster Traveler Information Evacuation Planning Support Evacuation Traveler Information Evacuation Traffic Management Evacuation Resource Sharing Disaster Responseand Evacuation

12. ITS Wide-AreaAlert • Use ITS to Notify Public in Emergency Situations • Inspired by Recent Use of ITS For “AMBER Alerts” • Significant institutional issues will remain • Public Safety and Emergency Management Agencies Control • Architecture Defines Potential ITS Interfaces • Plans, Policies, and Procedures for Use Established by Local Jurisdictions • Modify Existing “Emergency Notification and Personal Security” User Service

13. Critical InfrastructureSecurity • Use ITS to secure critical transportation infrastructure • Bridges • Tunnels • Interchanges • TMCs / Offices • Maintenance Facilities • Critical infrastructure will be locally determined • Modify existing “Emergency Notification and Personal Security” user service

14. Securing ITS • Define Security Services necessary for securing ITS itself • Information Security • Operational Security • Personnel Security • Security Management • No change to the Architecture Functional Definition (i.e., no new or modified Flows or Subsystems)

15. Securing ITS • Map Securing ITS Services to Physical Architecture • Information Security => Architecture Flows • Operational/Personnel Security => Subsystems • No User Service or User Service Requirement Changes • “Considerations” not “Requirements” • Securing ITS Services are Not Mandatory • Provide resource to deployers of ITS to understand need for providing security for their ITS

16. Security Summary • Physical Architecture high-level changes • New Subsystem • Security Monitoring • New Terminators • Alerting and Advisory Systems • Freight Container-Trailer • Shelter Providers • Telecommunications System for Traveler Information

17. Other Changes for Version 5.0 • 511 • Add new “Telecommunications System for Traveler Information” terminator to interface with the ISP • Hyperlinked Architecture • Theory of Operations and Market Package documents text, tables, and diagrams • Standards Mapping Updates • Stakeholder feedback changes

18. Version 5.0 Subsystem Diagram Travelers Centers Maintenance and Construction Management Traffic Management Emergency Management Toll Administration Commercial Vehicle Administration Remote Traveler Support Information Service Provider Emissions Management Transit Management Fleet and Freight Management Archived Data Management Personal Information Access Wide Area Wireless (Mobile) Communications Fixed-Point to Fixed-Point Communications Vehicle Roadway Security Monitoring Emergency Vehicle Toll Collection Commercial Vehicle Vehicle to Vehicle Communications Dedicated Short Range Communications Transit Vehicle Parking Management Maintenance and Construction Vehicle Commercial Vehicle Check Vehicles Field

19. Turbo Architecture Update • Turbo Architecture • New version will be released for use with Version 5.0 • Enables regional & project architectures to incorporate new security, 511, and other features

20. National ITS Architecture Version 5.0 • Schedule • Web site ready for feedback Sep 2003 • Look for Federal Register Notice • Launch Version 5.0 Website Oct 2003 • CDs available Nov 2003