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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

CVE-2015-0113
Published: 2015-04-27
The Jazz help system in IBM Rational Collaborative Lifecycle Management 4.0 through 5.0.2, Rational Quality Manager 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Team Concert 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Requirements Composer 4.0 through 4.0.7, Rational DOORS Next Generation...

CVE-2015-0174
Published: 2015-04-27
The SNMP implementation in IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.5 does not properly handle configuration data, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

CVE-2015-0175
Published: 2015-04-27
IBM WebSphere Application Server (WAS) 8.5 Liberty Profile before 8.5.5.5 does not properly implement authData elements, which allows remote authenticated users to gain privileges via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.