03:33 PM

Feds Set Deadline For Identity Smart Card Program

Agencies have until March 31 to come up with an implementation plan for a government-wide biometric-based credential system for employees and contractors.

Inside DHS' Classified Cyber-Coordination Headquarters
(click image for larger view)
Slideshow: Inside DHS' Classified Cyber-Coordination Headquarters

Federal agencies have until March 31 to come up with an implementation plan for a new government-wide identification system that leverages biometric technology and smart cards.

The federal government has stepped up plans to use the Federal Personal Identity Verification (PIV) system to verify employee and contractor credentials to access federal facilities and IT networks and systems, according to a memo from the Department of Homeland Security (DHS) issued Thursday.

The move to the system is mandated by Homeland Security Presidential Directive 12 (HSPD 12), a federal cybersecurity initiative the government said is aimed at increasing security and efficiency, reducing identity fraud, cutting costs and protecting personal privacy. Cybersecurity is a chief concern of the federal government, and the system is one of many it's taking to provide more security both internally and externally.

To qualify for PIV credentials, federal employees must have their fingerprints scanned and undergo background checks. Their personal identifying information is contained in cards that are scanned on card readers before entering federal facilities or logging on to federal IT networks. As of December 2010, 4.5 million federal employees had achieved PIV credentials, and 5 million of 5.7 million federal employees and contractors have completed background investigations, according to the memo.

In addition to outlining a time frame, the memo also lays out requirements for how agencies must ensure their facilities and IT systems are ready to accept the PIV cards.

Accessing systems at Marine Camp Lejeune

The DHS mandates that all new systems under development must support PIV credentials according to guidelines from the National Institute of Technology (NIST) before they can be deployed.

Further, effective in October at the beginning of the government's 2012 fiscal year, agencies must upgrade all existing "physical and logical" access control systems to support the PIV system before they can use any technology refresh funds for other projects.

The DHS also is requiring that any procurements involving facility or IT system access meet HSPD-12 policy. PIV credentials and acceptance of the credentials also must be interoperable, according to the memo.

The memo directs each agency to pick a lead official to oversee their implementation plan.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-02
Buffer overflow in Canary Labs Trend Web Server before 9.5.2 allows remote attackers to execute arbitrary code via a crafted TCP packet.

Published: 2015-10-02
Cisco NX-OS 6.0(2)U6(0.46) on N3K devices allows remote authenticated users to cause a denial of service (temporary SNMP outage) via an SNMP request for an OID that does not exist, aka Bug ID CSCuw36684.

Published: 2015-10-02
Cisco Email Security Appliance (ESA) 8.5.6-106 and 9.6.0-042 allows remote authenticated users to cause a denial of service (file-descriptor consumption and device reload) via crafted HTTP requests, aka Bug ID CSCuw32211.

Published: 2015-10-01
lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink attack on a (1) mount target or (2) bind mount source.

Published: 2015-10-01
kernel_crashdump in Apport before 2.19 allows local users to cause a denial of service (disk consumption) or possibly gain privileges via a (1) symlink or (2) hard link attack on /var/crash/vmcore.log.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.