DHS To Automate Terror Watchlist
Watchlist Service will replace the current manual process for sending information from the Terrorist Screening Database to the DHS
August 23, 2010
![](https://eu-images.contentstack.com/v3/assets/blt6d90778a997de1cd/bltc94608acf452fd67/655cf371ab171e040a838b2a/329050_DR23_Graphics_Website_V5_Default_Image_v1.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
The Department of Homeland Security plans to automate the process for how it receives data from the Terrorist Screening Database (TSD).
Working together with the FBI Terrorist Screening Center, the agency is developing a Watchlist Service to replace multiple, manual data feeds from the TSD to various components within the DHS.
The service will help the agency “move away from a manual and cumbersome process of data transmission and management to an automated and centralized process,” according to a DHS document outlining the Watchlist Service.
A presidential directive issued in September 2003 established a consolidated watchlist to help government enforcement officials identify, screen and track terrorist suspects or those believed to have the potential to engage in terrorist activities.
The system was criticized when airport screeners failed to identify a man who attempted to blow up a U.S. flight from Amsterdam to Detroit on Christmas day, 2009, even though he was on the watchlist. A failed car bomb in New York earlier this year also called into question the usefulness of the system.
The Watchlist Service will be implemented in several phases, according to the DHS. In the initial phase, those building the system will install a data broker to manage the transfer of data and ensure that DHS entities receiving data will receive only formatted records that are authorized for use.
In the second implementation phase, the service will be fitted with another data broker to manage encounter information regarding people on the watchlist.
Currently, when there is an encounter with a potential match on the watchlist, a report of that is sent to the TSD via a system-generated message or manually, by secure phone or fax. The DHS Watchlist Service Encounters Data Broker will allow all of these transmissions to be sent in a standardized way, as well as securely recorded for future use, according to the DHS.
A later implementation phase will add a persistent data store of the TSD within a DHS server so people can perform queries on the information. A combination of off-the-shelf products and custom components will be used to build the Watchlist Service, according to the DHS.
The DHS Screening Coordination Office will oversee the business end of creating the system, while the DHS Transportation Security Agency and Customs and Border Protection will handle the technical side. The DHS Office of the CIO also will aid with initial requirements and project management.
Read more about:
2010About the Author
You May Also Like
State of AI in Cybersecurity: Beyond the Hype
October 30, 2024[Virtual Event] The Essential Guide to Cloud Management
October 17, 2024Black Hat Europe - December 9-12 - Learn More
December 10, 2024SecTor - Canada's IT Security Conference Oct 22-24 - Learn More
October 22, 2024