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. The link for this article located at InfoWorld is no longer available. . The Department of Homeland Security encounters a notable three-year delay in launching a smart card ID system for federal employees due to poor management and tech issues. DHS Smart Card, Federal ID Program, Smart Card Challenges. . Anthony Pell
Mandating an XML messaging format, the integration allowed for the transfer of remote program and financial information from one database to another, where batch information is verified and balanced, said Negron. Even though these two divisions had already been sharing information . . . . Mandating an XML messaging format, the integration allowed for the transfer of remote program and financial information from one database to another, where batch information is verified and balanced, said Negron. Even though these two divisions had already been sharing information manually, Negron found the electronic integration more difficult than he expected. "We learned that something that people might consider simple, like security and encryption, took some work to get that working right," said Negron. "Some people would question if it is possible [to interface] effectively, with a minimum impact on the legacy system. ... We did very minor [code rewriting]." Homeland Security's Cooper said he expects similar balking. "Let's get real. It's cultural, political, organizational; this is where turf comes into play," said Cooper. "We're human beings; we do quirky stuff. Not because anyone is doing the wrong thing, but people have succeeded and been rewarded for certain behaviors. And, guess what, someone just moved everyone's cheese. We have to change, and that's not easy." The link for this article located at eWeek is no longer available. . Implementing a standardized JSON communication format enhanced the efficiency of sharing offsite software and monetary information.. XML Messaging, Data Integration, System Security, Program Management. . Anthony Pell
Get the latest Linux and open source security news straight to your inbox.