- Software token
A software token is a type of
two-factor authentication security device that may be used to authorize the use of computer services. Software tokens are stored on a general-purpose electronic device such as adesktop computer ,laptop , PDA, ormobile phone . This is in contrast tohardware token s, where the credentials are stored on a dedicated hardware device.Software tokens are considered to be weaker than hardware tokens, as they are exposed to threats such as
computer virus es and software attacks. However, the software token does have benefits: there is no physical token to carry, they do not contain batteries that will run out, and they are cheaper than hardware tokens. [SecurityPro News [http://www.securitypronews.com/2004/0121.html Strong Authentication] Retrieved on April 3, 2007]Security architecture
There are two primary architectures for software tokens:
Shared secret andpublic-key cryptography .For a shared secret, an administrator will typically generate a
configuration file for each end-user. The file will contain a username, apersonal identification number , and the secret. This configuration file is given to the user.The shared secret architecture is potentially vulnerable in a number of areas. The configuration file can be compromised if it is stolen and the token is copied. With time-based software tokens, it is possible to borrow an individual's PDA or laptop, set the clock forward, and generate codes that will be valid in the future. Any software token that uses shared secrets and stores the PIN alongside the shared secret in a software client can be stolen and subjected to offline attacks. Shared secret tokens can be difficult to distribute, since each token is essentially a different piece of software. Each user must receive a copy of the secret, which can create time constraints.
Some newer software tokens rely on
public-key cryptography , or asymmetric cryptography. This architecture eliminates many of the traditional weaknesses of software tokens. A PIN can be stored on a remote authentication server instead of with the token client, making a stolen software token no good unless the PIN is known as well. If there are attempts made to guess the PIN, it can be detected and logged on the authentication server, which can disable the token. Using asymmetric cryptography also simplifies implementation, since the token client can generate its own key pair and exchange public keys with the server.References
See also
* Multifactor authentication
*Security token
*eAuthentication External links
* [http://www.vnunet.com/news/1161914 Microsoft to abandon passwords] ,
* [http://it.slashdot.org/article.pl?sid=05/10/19/2340245&tid=172&tid=95 Banks to Use 2-factor Authentication by End of 2006]
Wikimedia Foundation. 2010.
