USA Flag

Official website of the Department of Homeland Security

Commercial Airports

Office of Security Policy and Industry Engagement

Overview

com_arpt

Branch Manager: Michael E. Duffy

Mission: To enhance the security of our Nation’s commercial airports by collaborating and partnering with airport industry stakeholders to develop efficient and effective security policies and programs for commercial airports.

Overview: The Office of Security Policy and Industry Engagement Commercial Aviation Airports Branch is responsible for airport security regulations, policies, and programs applicable to approximately 450 U.S. commercial airports. U.S. commercial airports are regulated for the purposes of aviation security under Title 49, Code of Federal Regulations Part 1542 (49 CFR 1542).

Programs and Initiatives

Airport Innovative Security Measures Initiative
The Office of Security Policy and Industry Engagement Commercial Aviation Airports Branch reached out to commercial airport operators for input on TSA’s “Airport Innovative Security Measures Initiative”. Supported by the Homeland Security Studies & Analysis Institute (HSSAI),  the Airports Branch launched this initiative to identify innovative security measures implemented by airport operators that are effectively employed and/or exceed the requirements of 49 CFR 1542. The intent of the project is to: identify innovative security measures in use at commercial airports; enhance TSA's understanding of the various factors airport operators consider when making security resource allocation decisions; and provide airport operators with a reference document of the innovative security measures and a proof-of-concept tool that will assist security resource allocation decisions.

Recommended Security Guidelines for Airport Planning, Design, & Construction
The Office of Security Policy and Industry Engagement Commercial Aviation Airports Branch will facilitate the efforts of the Aviation Security Advisory Committee (ASAC) working group responsible for revising the 2006 edition of “TSA’s Recommended Security Guidelines for Airport Planning, Design & Construction”.

In-Depth Security Review (IDSR) Working Group
The IDSR is a working group comprised of American Association of Airport Executives and Airports Council International – North America members and staff as well as TSA‘s Commercial Airports Office of Chief Counsel and Office of Security Operations. The IDSR working group meets regularly to thoroughly review all active, 49 CFR 1542, airport security directives and security program amendments and consider their inclusion, revision, or deletion within the regulatory framework.

Framework for Airport Biometric Access Systems
The Office of Security Policy and Industry Engagement Commercial Aviation Airports Branch is committed to working with industry partners to better understand commercial airport operator concerns regarding the introduction of biometrics into airports’ identity management and access control systems. In advance of regulatory requirements, TSA continues to promote airport implementation of biometrically enabled interoperability solutions based upon federal standards.

Regulatory Requests from Airport Operators
The Office of Security Policy and Industry Engagement Commercial Aviation Airports Branch is responsible for reviewing and recommending approval or disapproval of requests from airport operators for alternate measures to security directives and re-categorizations based on passenger traffic and security assessments.

Registered Traveler
TSA concluded a two-year Registered Traveler (RT) pilot at 19 airports in July 2008, at which time the program became a market-driven venture offered by the private sector in partnership with airports and airlines. After TSA’s pilot ended in July 2008, all RT service providers were obligated to follow data security standards and continue offering service. However, each service provider’s use of data is regulated under its own privacy policy and its relationship with customers and sponsoring airport or airline. Information submitted to TSA during the RT pilot program will be destroyed in accordance with the record retention period approved by the National Archives and Records Administration (NARA). No customer data was submitted to TSA after July 30, 2008.

Q: Are RT cards accepted as a valid ID at the airport security checkpoint?
A: RT cards are no longer accepted as a primary form of ID at the checkpoint. RT cards that have a visible photograph of the customer and an expiration date may be used as a secondary form of ID at the checkpoint.

Q: What is the status of the RT program now?
A: The program is a market-driven venture offered by the private sector in partnership with airports and airlines.

Q: What will happen to the customer data that CLEAR, FLO Corporation, and Vigilant Solutions collected? Is it secure?
A: Questions regarding data management should be directed to vendors. Each vendor has assured TSA that they are appropriately safeguarding the data. RT service providers were required to use customer data only for the RT program unless customers expressly opted-in for its use elsewhere.

Q: What does this mean for the future of the RT program?
A: TSA concluded its RT pilot in July, 2008. Since that time, is has been a market-driven venture offered by the private sector in partnership with airports and airlines.

Q: What is TSA’s schedule to delete applicants/participants information submitted to the agency during the pilot program?
A: Information submitted to TSA during the RT pilot program (up until July 2008) will be destroyed in accordance with the record retention period approved by NARA as follows:

  • No match- One year after access based on when the security threat assessment becomes inactive (August 1, 2009)
  • Potential match- Seven years after access based on when the security threat assessment becomes inactive
  • Confirmed match- 99 years after the security threat assessment is completed

Back to Top

Contact Us

For general information regarding OSPIE Commercial Aviation Airports Branch, please send inquiries to: TSNMAirports@dhs.gov

Back to Top

Latest revision: 24 December 2012