Risk
2/4/2011
03:33 PM
50%
50%

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
Comments
Oldest First  |  Newest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: just wondering...Thanx
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
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.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.