Risk
8/23/2010
12:34 PM
50%
50%

DHS To Automate Terror Watchlist

Watchlist Service will replace the current manual process for sending information from the Terrorist Screening Database to the DHS

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.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

CVE-2014-6132
Published: 2014-12-24
Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

CVE-2014-6153
Published: 2014-12-24
The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.