Milestones on the Way to a Standardized Federal ID Card
Milestones on the Way to a Standardized Federal ID Card
By CSO Contributor
August 01, 2006 — CSO —
Aug. 27, 2004 President Bush signs Homeland Security Presidential Directive 12 (HSPD 12), mandating a secure, common identification method for federal employees and contractors.
Feb. 25, 2005 The Secretary of Commerce approves Federal Information Processing Standard 201 (FIPS 201), which lays out the technical aspects of how HSPD 12 will be implemented.
June 2005 Agencies must submit implementation plans to the Office of Management and Budget.
August 2005 OMB releases guidance on implementing FIPS 201, with deadlines for all federal agencies and departments.
Oct. 27, 2005 Deadline for agencies to comply with part one of FIPS 201, which involves making sure their processes to issue ID cards meet certain standards.
February 2006 The Government Accountability Office reports that there are still no products available that have been approved as FIPS 201compliant, and warns that true interoperability may not be achieved.
June 30, 2006 OMB announces that the first nine products, from five vendors, have been approved as FIPS 201 compliant.
Oct. 27, 2006 Agencies must begin complying with part two of FIPS 201, which means actually issuing interoperable smart cards.
Oct. 27, 2007 Agencies must verify or complete background investigations for all current employees and contractors. (Background checks of workers with more than 15 years' tenure may be delayed.)
Oct. 27, 2008 Agencies must complete background investigations for all employees with more than 15 years tenure.
Read more about data protection in CSOonline's Data Protection section.
The challenge of true data protection spans databases, internal and external networks, physical and offsite storage, business partners and more. These resources offer expert perspective from the basics through specific key elements of data protection strategies.
Network security basics
Protection, detection, and reaction—those are the three underlying principles your security program must embody
Computer incident detection, response, forensics
Richard Bejtlich shows how to measure and improve the maturity of your incident response
A few good IT security metrics
Stop counting blocked malware attachments and measure things that can contribute to meaningful change
5 key cloud security trends
Cloud security is evolving rapidly—stay on top of it
IT risk assessment frameworks
How to do end-to-end encryption
How to compare and use enterprise antivirus
Also find sample data protection policies in CSO's tools, templates and policies library
- Introduction to VMware vCenter Site Recovery Manager 5
- Introduction to Virtualization
- Preventing Unplanned Downtime with Server Virtualization
- Secure Cloud Infrastructure and Next-Generation Data Centers - An Interactive Panel for Decision Makers
- Gartner Next Generation Network IPS Webcast
- Understand Your Data: The Future of Backup and Archiving
- Overcome Top 7 Admin Challenges of Active Directory
- Insiders Can Ruin Your Company. Take Action.
- Top Solutions and Tools to Prevent Devastating Malware
- X-Ray of the PCI Process-4 Proactive Steps
- Streamline Compliance and Increase ROI
- Beyond SFTP: Five Ways Secure Managed File Transfer Can Improve Your Business
CSO Corporate Partners
- Patch Tuesday preview, February 2012
Microsoft published its Patch Tuesday Preview for February of 2012 a few minutes ago. IT admins can expect nine bulletins to address 21 security vulnerabilities.
It looks like four bulletins will be rated critical while the rest are designated as important.
Affected Microsoft products are:
- M86 report proves water is wet
- Actor, banker, soldier, spy: Suits and Spooks Anti-Conference aims to redefine security
More Salted Hash with Bill Brenner
