Session 19 Security and Architecture - v5

Slide 1

Security and the National ITS Architecture

Logo: Architecture Development Team

ITS America 2003

Session 19: The State of the Practice: ITS and Homeland Security

May 19, 2003

Minneapolis, MN

Slide 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

Slide 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

Graphic: Securing ITS encompasses Transit Security, Rail Security, Freight and Commercial Vehicle Security, HAZMAT Security, Critical Infrastructure Security, Traveler Security, Disaster Response and Evacuation and ITS Wide Area Alert

Slide 4

Transit Security

Photo: A bus sitting at a bus stop

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

Slide 5

Transit Security

Photo: A bus sitting at a bus stop

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

Slide 6

Rail Security

Photo: A train passing over a bridge in an arid area

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

Slide 7

Freight & Commercial Vehicle Security

Photo: A truck and its payload pass a factory

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

Slide 8

HAZMAT Security

Photo: A rear view of a liquid-carrying cargo canister on a truck

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

Slide 9

HAZMAT Security

Photo: A rear view of a liquid-carrying cargo canister on a truck

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

Slide 10

Disaster Response and Evacuation

Photo: A room full of emergency personnel working at desks

Photo: A firefighter spraying flames with water from atop a firetruck

Photo: Four lanes of cars in traffic during an 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

Slide 11

Disaster Response and Evacuation

Photo: A room full of emergency personnel working at desks

Photo: A firefighter spraying flames with water from atop a firetruck

Photo: Four lanes of cars in traffic during an evacuation

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

Slide 12

ITS Wide-Area Alert

Photo: An overhead electronic roadsign displaying details of an "Amber Alert" while traffic moves below

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

Slide 13

Critical Infrastructure Security

Photo: A view from underneath of a suspension bridge

Photo: A view from within a road tunnel

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

Slide 14

Securing ITS

Photo: Picture of a key

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)

Slide 15

Securing ITS

Photo: Picture of a key

Map Securing ITS Services to Physical Architecture
- Information Security to Architecture Flows
- Operational/Personnel Security to 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

Slide 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

Slide 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

Logo: Logo reads "511" surrounded by a stylized telephone and cord

Slide 18

Version 5.0 Subsystem Diagram

Diagram: The diagram illustrates the Version 5.0 Subsystem. There are four forms of communication being illustrated, Wide Area Wireless (Mobile), Fixed-Point to Fixed-Point, Vehicle to Vehicle and Dedicated Short Range. The diagram shows the relationships between these four forms of communication and Travelers, Centers, Vehicles and the Field.

Slide 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

Logo: The Turbo Architecture logo that reads "Turbo Architecture"

Slide 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

Search Operations: Home About Operations Office Directory Program Areas Regulation/Policy Publications Speeches Press Room Links Subject Index Feedback	Session 19 Security and Architecture - v5 ETO Home > Response Slide 1 Security and the National ITS Architecture Logo: Architecture Development Team ITS America 2003 Session 19: The State of the Practice: ITS and Homeland Security May 19, 2003 Minneapolis, MN Slide 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 Slide 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 Graphic: Securing ITS encompasses Transit Security, Rail Security, Freight and Commercial Vehicle Security, HAZMAT Security, Critical Infrastructure Security, Traveler Security, Disaster Response and Evacuation and ITS Wide Area Alert Slide 4 Transit Security Photo: A bus sitting at a bus stop 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 Slide 5 Transit Security Photo: A bus sitting at a bus stop 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 Slide 6 Rail Security Photo: A train passing over a bridge in an arid area 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 Slide 7 Freight & Commercial Vehicle Security Photo: A truck and its payload pass a factory 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 Slide 8 HAZMAT Security Photo: A rear view of a liquid-carrying cargo canister on a truck 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 Slide 9 HAZMAT Security Photo: A rear view of a liquid-carrying cargo canister on a truck 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 Slide 10 Disaster Response and Evacuation Photo: A room full of emergency personnel working at desks Photo: A firefighter spraying flames with water from atop a firetruck Photo: Four lanes of cars in traffic during an 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 Slide 11 Disaster Response and Evacuation Photo: A room full of emergency personnel working at desks Photo: A firefighter spraying flames with water from atop a firetruck Photo: Four lanes of cars in traffic during an evacuation 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 Slide 12 ITS Wide-Area Alert Photo: An overhead electronic roadsign displaying details of an "Amber Alert" while traffic moves below 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 Slide 13 Critical Infrastructure Security Photo: A view from underneath of a suspension bridge Photo: A view from within a road tunnel 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 Slide 14 Securing ITS Photo: Picture of a key 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) Slide 15 Securing ITS Photo: Picture of a key Map Securing ITS Services to Physical Architecture Information Security to Architecture Flows Operational/Personnel Security to 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 Slide 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 Slide 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 Logo: Logo reads "511" surrounded by a stylized telephone and cord Slide 18 Version 5.0 Subsystem Diagram Diagram: The diagram illustrates the Version 5.0 Subsystem. There are four forms of communication being illustrated, Wide Area Wireless (Mobile), Fixed-Point to Fixed-Point, Vehicle to Vehicle and Dedicated Short Range. The diagram shows the relationships between these four forms of communication and Travelers, Centers, Vehicles and the Field. Slide 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 Logo: The Turbo Architecture logo that reads "Turbo Architecture" Slide 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
	US DOT Home \| FHWA Home \| Operations Home \| Privacy Policy