NIST special publication expands government authentication options

"Changes made to the document reflect changes in the state of the art," explains NIST computer security expert Tim Polk, Cryptographic Technology Group manager at NIST. "There are new techniques and tools available to government agencies, and this provides them more flexibility in choosing the best authentication methods for their individual needs, without sacrificing security."

When SP 800-63 was first released, its authors assumed that most agencies would handle the business of figuring out if users were who they claimed to be in-house. But since that time, an industry has grown around providing authentication services, and it is often in the best interest of agencies to take advantage of commercial systems or those of other government entities. And while passwords are still the leading mechanism for authenticating user identity, a growing number of systems rely on cryptographic keys or physical tokens.

The revision broadens the discussion of technologies available to agencies and gives a more detailed discussion of these technologies. The guideline applies whether agencies choose to handle authentication directly or leverage services provided by other parties, including commercial companies.

Government agencies have the option of using the services of companies that have had their authentication systems certified through the Federal Chief Information Officer Council's Trust Framework Provider Adoption Process (TFPAP). This program assesses credentialing processes against federal requirements, including those established in 800-63. To ensure consistency and avoid redundant analysis, NIST strongly encourages agencies to leverage the TFPAP process.

SP 800-63-1 is the official implementation guidance for the Office of Management and Budget (OMB) Memorandum 04-04, "E-Authentication Guidance for Federal Agencies.*" Polk stresses that the revised NIST guideline may inform but is not intended to restrict or constrain the development or use of standards for implementation of the National Strategy for Trusted Identities in Cyberspace (NSTIC). NIST SP 800-63-1 is specifically designated as a guideline for use by federal agencies for electronic authentication. NSTIC, in contrast, has a broader charge: the creation of an Identity Ecosystem, "an online environment where individuals and organizations will be able to trust each other because they follow agreed upon standards to obtain and authenticate their digital identities."

More information: NIST SP 800-63-1, Electronic Authentication Guideline, is available at http://www.nist.go … ub_id=910006 . For more NIST computer security publications, see http://csrc.nist.gov/publications/PubsSPs.html

* The Office of Management and Budget's guidance, "E-Authentication Guidance for Federal Agencies" [OMB 04-04] can be found at http://www.whiteho … 4/m04-04.pdf

Provided by National Institute of Standards and Technology (NIST)