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
Comments
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12697
PUBLISHED: 2018-06-23
A NULL pointer dereference (aka SEGV on unknown address 0x000000000000) was discovered in work_stuff_copy_to_from in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. This can occur during execution of objdump.
CVE-2018-12698
PUBLISHED: 2018-06-23
demangle_template in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30, allows attackers to trigger excessive memory consumption (aka OOM) during the "Create an array for saving the template argument values" XNEWVEC call. This can occur during execution of objdump.
CVE-2018-12699
PUBLISHED: 2018-06-23
finish_stab in stabs.c in GNU Binutils 2.30 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write of 8 bytes. This can occur during execution of objdump.
CVE-2018-12700
PUBLISHED: 2018-06-23
A Stack Exhaustion issue was discovered in debug_write_type in debug.c in GNU Binutils 2.30 because of DEBUG_KIND_INDIRECT infinite recursion.
CVE-2018-11560
PUBLISHED: 2018-06-23
The webService binary on Insteon HD IP Camera White 2864-222 devices has a stack-based Buffer Overflow leading to Control-Flow Hijacking via a crafted usr key, as demonstrated by a long remoteIp parameter to cgi-bin/CGIProxy.fcgi on port 34100.