Risk

2/18/2010
03:19 PM
50%
50%

DHS Misses Target For Smart Card ID System

Poor management, insufficient funding, and deficient IT systems are blamed for a three-year delay by the Department of Homeland Security in issuing smart cards to 250,000 employees and contractors.

The Department of Homeland Security is three years behind schedule on a project to develop a standard smart-card identification method for federal employees and contractors, according to a DHS report.

The project -- officially called Homeland Security Presidential Directive 12 (HSPD-12): Policy for a Common Identification Standard for Federal Employees and Contractors -- requires that DHS develop a government-wide way to identify employees by issuing smart cards. The cards contain information about which IT applications and networks and facilities each employee is permitted access to.

The original completion for the issuance and use of identity cards was Oct. 27, 2008, according to the report, issued by inspector general Richard L. Skinner. However, as of Sept. 22, 2009, only 15,567 of the approximately 250,000 department employees and contractors have been issued identity credentials.

The program's target date for completion has now been pushed to Sept. 30, 2011, the end of the 2011 fiscal year.

Specifically, DHS plans to issue smart cards to 135,000 federal employees and contractors by the end of fiscal year 2010, and to the remaining 105,000 employees and contractors by the end of fiscal year 2011.

The report blames poor program management, including insufficient funding and resources, as well as a change in implementation strategy for issuing cards in June 2009, for falling behind schedule.

There are significant IT problems hindering completion of the directive, too, according to the report.

One of its biggest challenges is allowing what the report calls "logical access" to IT systems. The government does not have proper system security and account management controls in place to protect people's personal identity information from unauthorized access, it concluded.

In particular, DHS has been slow to implement government-wide identity-management and smart-card identification systems to handle the project. Coordinating efforts between various departments and their respective IT systems has been a significant challenge, according to the report.

The report offers a set of recommendations to get the program back on track so it can meet its new target completion date.

One basic recommendation is to make sure the project management office that is overseeing the project has the staffing and funding necessary to do its job properly.

Coming up with a reasonable estimate for how much completing the project will cost is also on the list. Problems with planning for the cost of the project within the federal budget have been one of the reasons the project has been insufficiently funded, according to the report.

On the IT side, DHS also appears to have a lot of work to do to implement the system in time.

The agency still needs to develop formal procedures for defining employee, or user, accounts and roles, as well as defining the privileges associated with those user accounts and roles.

It also must reconcile data and collaboration between a series of user configuration, card management, and account management systems, as well find and correct any inconsistencies between an identity-management system and government physical-access control systems.

Further, there are still no policies in place for how to control employee access in cases in which cards must be revoked, suspended, or destroyed, nor are there procedures for evaluating the physical security of enrollment centers where government employees are issued their cards, according to the report.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
3 Ways to Retain Security Operations Staff
Oliver Rochford, Vice President of Security Evangelism at DFLabs,  11/20/2017
A Call for Greater Regulation of Digital Currencies
Kelly Sheridan, Associate Editor, Dark Reading,  11/21/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Managing Cyber-Risk
An online breach could have a huge impact on your organization. Here are some strategies for measuring and managing that risk.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.