NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
In today's environment, there is little doubt that companies, organizations, and governments must make significant investments in developing, implementing, and supporting authentication for their digital systems. Perhaps because of this, an organization's IT support center often takes a hard line when it comes to user's authentication. Authentication tools typically take for granted that the user will do whatever it takes to authenticate. No surprise, users don't like being forced into a corner. They are resourceful and very creative in making it more manageable, usually by coming up with ways that circumvent the overall security of a system. Unfortunately, as the number and complexity of authentications for each user become greater, job satisfaction for workers is likely to decrease.