Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

5/2/2006
08:15 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Deadline Could Spur Smart Cards

HSPD-12 requires unified government credentials - deployments serve as a proving ground

U.S. federal agencies are gearing up to deploy new, standards-based smart card technology that could soon be an attractive option for large enterprises as well.

Agencies are making changes in their building security systems today in an effort to meet the October compliance deadline for Homeland Security Presidential Directive/HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors. HSPD-12 requires that all government agencies adopt strict policies to identify and credential employees and contractors, and to issue a secure electronic credential, which will take the form of a smart card that shares a common format across all agencies.

The National Institute of Standards and Technology, working with the U.S. Department of Commerce, developed the guidelines for the smart card technology under its NIST Personal Identification Validation Program (NPIVP) program. Compliance with the processes and technical requirements, which are defined in FIPS-201-1, Personal Identity Verification (PIV) of Federal Employees and Contractors, is required by October.

Smart cards, experts say, have a number of advantages over other types of security credentials. They can carry multiple identities and other data in a portable form factor, and they can be used for both physical and electronic access. But the technology is not simple or cheap to deploy, so agencies are "trying to work through a viable, cost effective rollout," says David Troy, practice leader for identity management at Electronic Data Systems (EDS).

While the agencies are taking some arrows during their HSPD-12 projects, their large-scale deployments of the technology should help the private sector, Troy said. "HSPD-12 is accelerating convergence within the security industry itself. Functionally and organizationally, the security industry landscape is changing rapidly to meet this new market. Secondly, because so many federal government employees and contractors will be using this new standard, the private sector will most likely adopt it, or a form of it, as well."

Enterprises will also benefit from the lessons learned by the agencies as they deploy the HSPD-12 technology, Troy observed.

Capital costs for the technology probably won't drop, however. Randy Vanderhoof, Executive Director of the Smart Card Alliance, doesn't expect the prices of smart card and support systems to fall as a result of HSPD-12: "The supporting systems will be more feature-rich at the same price points," he says, "and systems that don't support smart cards today will evolve into ones that do."

— Mike Fratto, Editor at Large, Dark Reading

Organizations mentioned in this article:

  • Electronic Data Systems Corp. (EDS) (NYSE: EDS)
  • National Institute of Standards and Technology (NIST)
  • Smart Card Alliance

    Mike Fratto is a principal analyst at Current Analysis, covering the Enterprise Networking and Data Center Technology markets. Prior to that, Mike was with UBM Tech for 15 years, and served as editor of Network Computing. He was also lead analyst for InformationWeek Analytics ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    News
    Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
    Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
    Edge-DRsplash-10-edge-articles
    Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
    Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
    News
    Cybercrime Groups More Prolific, Focus on Healthcare in 2020
    Robert Lemos, Contributing Writer,  2/22/2021
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Write a Caption, Win an Amazon Gift Card! Click Here
    Latest Comment: This comment is waiting for review by our moderators.
    Current Issue
    2021 Top Enterprise IT Trends
    We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
    Flash Poll
    Building the SOC of the Future
    Building the SOC of the Future
    Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2021-25284
    PUBLISHED: 2021-02-27
    An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
    CVE-2021-3144
    PUBLISHED: 2021-02-27
    In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
    CVE-2021-3148
    PUBLISHED: 2021-02-27
    An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
    CVE-2021-3151
    PUBLISHED: 2021-02-27
    i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...
    CVE-2021-3197
    PUBLISHED: 2021-02-27
    An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.