PIA - Executive Scheduling System (ESS)
DEPARTMENT OF TRANSPORTATION
Office of the Secretary of Transportation (OST)
PRIVACY IMPACT ASSESSMENT
Executive Scheduling System (ESS2)
November 10, 2008
TABLE OF CONTENTS
Overview of Privacy Management Process
Personally Identifiable Information (PII) & ESS
Why ESS Collects Information
How ESS uses information
How ESS Shares Information
How ESS Provides Notice and Consent
How ESS Ensures Data Accuracy
How ESS Provides Redress
How ESS Secures Information
How Long ESS Retains Information
System of Records
The Office of the Secretary (OST) oversees the formulation of national transportation policy and promotes intermodal transportation. Other responsibilities range from negotiation and implementation of international transportation agreements, assuring the fitness of US airlines, enforcing airline consumer protection regulations, issuance of regulations to prevent alcohol and illegal drug misuse in transportation systems and preparing transportation legislation.
Privacy management is an integral part of the Department of Transportation (DOT) Executive Scheduling System (ESS). The Office of the Secretary (OST) has retained the services of privacy experts to help assess its privacy management program, utilizing proven technology, sound policies and procedures, and established methodologies.
The privacy management process is built upon a methodology that has been developed and implemented in leading companies around the country and globally. The methodology is designed to help ensure that DOT and OST will have the information, tools and technology necessary to manage privacy effectively and employ the highest level of fair information practices while allowing OST to achieve its mission of protecting and enhancing the U.S. transportation system. The methodology is based upon the following steps:
- Establish priority, authority, and responsibility. Appointing a cross-functional privacy management team to ensure input from systems architecture, technology, security, legal, and other disciplines necessary to ensure that an effective privacy management program is developed.
- Assess the current privacy environment. This involves interviews with key individuals involved in the ESS system to ensure that privacy risks are identified, addressed and documented.
- Organize the resources necessary for the project's goals. Internal OST resources, along with outside experts, are involved in reviewing the technology, data uses, and associated risks. They are also involved in developing the necessary redress systems and training programs.
- Develop the policies, practices, and procedures. The resources identified in the paragraph above work to develop effective policies, practices, and procedures to ensure that fair information practices are complied with. The policies are designed to protect privacy effectively while allowing OST to achieve its mission.
- Implement the policies, practices, and procedures. Once the policies, practices, and procedures are developed, they must be implemented. This involves training all individuals who will have access to and/or process personally identifiable information (PII). It also entails working with vendors to ensure that they maintain the highest standard for privacy while providing services to the OST project.
- Maintain policies, practices, and procedures. Due to changes in technology, personnel and other aspects of any program, effective privacy management requires that technology and information be available to the privacy management team to ensure that privacy policies, practices, and procedures continue to reflect actual practices. Regular monitoring of compliance is required.
- Manage exceptions and/or problems with the policies, practices, and procedures. This step involves the development and implementation of an effective redress and audit system to ensure that any complaints are effectively addressed and corrections made, if necessary.
ESS is used to control and manage official invitations to the Secretary. As such, it contains information on individuals that includes names, position, phone numbers and duty titles.
The ESS modules will contain and publicly post the following information: ESS does not publicly post any PII information.
ESS collects the PII in order to effectively manage schedules and subsequent changes.
OST personnel enter schedule information and then manage alterations and subsequent contacts with scheduled personnel.
In accordance with Section 1.9 of the ESS System Security Plan, ESS is located on DOT's Intranet. The system is not available on the Internet; however, access is possible through a VPN connection. The system does not share data with other systems.
ESS displays the DOT approved system warning banner to alert users of notice and consent to monitoring prior to login.
ESS employs the data accuracy checks inherit in Oracle database software to ensure data validity and accuracy. The system has been reviewed to ensure, to the greatest extent possible, it is accurate, relevant, timely and complete via security testing and evaluation.
Validation checks are built into the application software that both prompt the user that an incorrect entry has been entered and must be corrected, and that a user has successfully input data.
ESS takes appropriate security measures to safeguard PII and other sensitive data. ESS applies DOT security standards, including but not limited to routine scans and monitoring, back-up activities, and background security checks of OST employees and contractors.
ESS retains PII information for a minimum of one year.
ESS contains information that is part of existing System of Records subject to the Privacy Act, because it is searched by an individual's name, position and phone number. In most instances, DOT/ALL 9 applies and the Department of Transportation controls the data and maintains System of Records responsibilities.
OST has certified and accredited the security of ESS in accordance with DOT information technology security standard requirements.