A security token (or sometimes a hardware token, authentication token, USB token, cryptographic token, software token, virtual token, or key fob) may be a physical device that an authorized user of computer services is given to ease authentication. The term may also refer to software tokens. Security tokens are used to prove ones identity electronically (as in the case of a customer trying to access their bank account). The token is used in addition to or in place of a password to prove that the customer is who they claim to be. The token acts like an electronic key to access something. Some may store cryptographic keys, such as a digital signature, or biometric data, such as fingerprint minutiae. Some designs feature tamper resistant packaging, while others may include small keypads to allow entry of a PIN or a simple button to start a generating routine with some display capability to show a generated key number. Special designs include a USB connector, RFID functions or Bluetooth wireless interface to enable transfer of a generated key number sequence to a client system. Contents [hide] 1 Password types 1.1 Time-synchronized one-time passwords 1.2 Mathematical-algorithm-based one-time passwords 2 Physical types 2.1 Disconnected tokens 2.2 Connected tokens 2.2.1 Smart cards 2.3 Contactless tokens 2.3.1 Bluetooth tokens 2.4 Single sign-on software tokens 2.5 Mobile device tokens 3 Vulnerabilities 4 Digital signature 5 Notable vendors and models 6 See also 7 References 8 External links Password types[edit] All tokens contain some secret information that are used to prove identity. There are four different ways in which this information can be used: Asynchronous password token for online banking. Static password token. The device contains a password which is physically hidden (not visible to the possessor), but which is transmitted for each authentication. This type is vulnerable to replay attacks. Synchronous dynamic password token. A timer is used to rotate through various combinations produced by a cryptographic algorithm. The token and the authentication server must have synchronized clocks. Asynchronous password token. A one-time password is generated without the use of a clock, either from a one-time pad or cryptographic algorithm. Challenge response token. Using public key cryptography, it is possible to prove possession of a private key without revealing that key. The authentication server encrypts a challenge (typically a random number, or at least data with some random parts) with a public key; the device proves it possesses a copy of the matching private key by providing the decrypted challenge. Time-synchronized one-time passwords[edit] Time-synchronized one-time passwords change constantly at a set time interval, e.g. once per minute. To do this some sort of synchronization must exist between the clients token and the authentication server. For disconnected tokens this time-synchronization is done before the token is distributed to the client. Other token types do the synchronization when the token is inserted into an input device. The main problem with time-synchronized tokens is that they can, over time, become unsynchronized.[citation needed] However, some such systems, such as RSAs SecurID, allow the user to resynchronize the server with the token, sometimes by entering several consecutive passcodes. Most also cannot have replaceable batteries and only last up to 5 years before having to be replaced - so there is additional cost. Mathematical-algorithm-based one-time passwords[edit] Another type of one-time password uses a complex mathematical algorithm, such as a hash chain, to generate a series of one-time passwords from a secret shared key. Each password is unguessable, even when previous passwords are known. The open source OATH algorithm is standardized; other algorithms are covered by U.S. patents. Each new password is unique, so an unauthorized user would be unable to guess what the new password may be, based on previously used passwords. Physical types[edit] Tokens can contain chips with functions varying from very simple to very complex, including multiple authentication methods. The simplest security tokens do not need any connection to a computer. The tokens have a physical display; the authenticating user simply enters the displayed number to log in. Other tokens connect to the computer using wireless techniques, such as Bluetooth. These tokens transfer a key sequence to the local client or to a nearby access point. Alternatively, another form of token that has been widely available for many years is a mobile device which communicates using an out-of-band channel (like voice, SMS, or USSD). Still other tokens plug into the computer, and may require a PIN. Depending on the type of the token, the computer OS will then either read the key from token and perform cryptographic operation on it, or ask the tokens firmware to perform this operation A related application is the hardware dongle required by some computer programs to prove ownership of the software. The dongle is placed in an input device and the software accesses the I/O device in question to authorize the use of the software in question. Commercial solutions are provided by a variety of vendors, each with their own proprietary (and often patented) implementation of variously used security features. Token designs meeting certain security standards are certified in the United States as compliant with FIPS 140, a federal security standard. Tokens without any kind of certification are sometimes viewed as suspect, as they often do not meet accepted government or industry security standards, have not been put through rigorous testing, and likely cannot provide the same level of cryptographic security as token solutions which have had their designs independently audited by third-party agencies.[citation needed] Disconnected tokens[edit] A disconnected token. The number must be copied into the PASSCODE field by hand. Disconnected tokens have neither a physical nor logical connection to the client computer. They typically do not require a special input device, and instead use a built-in screen to display the generated authentication data, which the user enters manually themselves via a keyboard or keypad. Disconnected tokens are the most common type of security token used (usually in combination with a password) in two-factor authentication for online identification.[1] Connected tokens[edit] Historically, the term connected token referred to tokens that must be physically connected to the computer with which the user is authenticating. Tokens in this category automatically transmit the authentication information to the client computer once a physical connection is made, eliminating the need for the user to manually enter the authentication information. However, in order to use a connected token, the appropriate input device must be installed. The most common types of physical tokens are smart cards and USB tokens, which require a smart card reader and a USB port respectively. Older PC card tokens are made to work primarily with laptops. Type II PC Cards are preferred as a token as they are half as thick as Type III. Tokens with Audio Jack Port The audio jack port is a relatively practical method to establish connection between mobile devices, such as iPhone, iPad and Android, and other accessories. The most well known device is called Square, a credit card reader for iPhone and Android. Some use a special purpose interface (e.g. the crypto ignition key deployed by the United States National Security Agency). Tokens can also be used as a photo ID card. Cell phones and PDAs can also serve as security tokens with proper programming. Contemporary use of the term Connected Token within online applications refers to tokens that do not require a connection to the users computer as the conduit to the (generally) centralised or cloud based authentication service, but instead maintain their own connection to this service for the interchange of authentication requests and responses. The advantages of this approach over prior generation connected tokens and disconnected tokens is that there is a decoupling of the authentication mechanism from the online service channel such that the authentication mechanism becomes channel independent. For example a contemporary connected token could be used by a banking customer to authenticate transactions entered via the Internet, at point of sale, at an ATM or via an operated assisted channel, all with a common authentication use case prevailing. Examples of contemporary Connected Tokens include Salt Groups mSign product. USB Tokens Smart cards[edit] Main article: Smart card Many connected tokens use smart card technology. Smart cards can be very cheap (around ten cents[citation needed]) and contain proven security mechanisms (as used by financial institutions, like cash cards). However, computational performance of smart cards is often rather limited because of extreme low power consumption and ultra thin form-factor requirements. Smart-card-based USB tokens which contain a smart card chip inside provide the functionality of both USB tokens and smart cards. They enable a broad range of security solutions and provide the abilities and security of a traditional smart card without requiring a unique input device. From the computer operating systems point of view such a token is a USB-connected smart card reader with one non-removable smart card present.[2] Contactless tokens[edit] Unlike connected tokens, contactless tokens form a logical connection to the client computer but do not require a physical connection. The absence of the need for physical contact makes them more convenient than both connected and disconnected tokens. As a result contactless tokens are a popular choice for keyless entry systems and electronic payment solutions such as Mobil Speedpass, which uses RFID to transmit authentication info from a keychain token. However, there have been various security concerns raised about RFID tokens after researchers at Johns Hopkins University and RSA Laboratories discovered that RFID tags could be easily cracked and cloned.[3] Another downside is that contactless tokens have relatively short battery lives; usually only 5–6 years, which is low compared to USB tokens which may last more than 10 years.[citation needed] Though some tokens do allow the batteries to be changed, thus reducing costs. Bluetooth tokens[edit] Bluetooth tokens are often combined with a USB token, thus working in both a connected and a disconnected state. Bluetooth authentication works when closer than 32 feet (10 meters). If the Bluetooth is not available, the token must be inserted into a USB input device to function. In the USB mode of operation sign off required care for the token while mechanically coupled to the USB plug. The advantage with the Bluetooth mode of operation is the option of combining sign-off with a distance metrics. Respective products are in preparation, following the concepts of electronic leash. Single sign-on software tokens[edit] Some types of Single sign-on (SSO) solutions, like enterprise single sign-on, use the token to store software that allows for seamless authentication and password filling. As the passwords are stored on the token, users need not remember their passwords and therefore can select more secure passwords, or have more secure passwords assigned. Mobile device tokens[edit] A mobile computing device such as a smartphone or tablet computer can also be used as the authentication device. This provides secure two-factor authentication that does not require the user to carry around an additional physical device. Some vendors offer a mobile device authentication solution that uses a cryptographic key for user authentication. This provides a high level of security protection including protection from a Man-in-the-middle attack, which can occur from a rogue Hotspot (Wi-Fi). Vulnerabilities[edit] The simplest vulnerability with any password container is theft or loss of the device. The chances of this happening, or happening unawares, can be reduced with physical security measures such as locks, electronic leash, or body sensor and alarm. Stolen tokens can be made useless by using two factor authentication. Commonly, in order to authenticate, a personal identification number (PIN) must be entered along with the information provided by the token the same time as the output of the token. Any system which allows users to authenticate via an untrusted network (such as the Internet) is vulnerable to man-in-the-middle attacks. In this type of attack, a fraudster acts as the go-between the user and the legitimate system, soliciting the token output from the legitimate user and then supplying it to the authentication system themselves. Since the token value is mathematically correct, the authentication succeeds and the fraudster is granted access. Citibank made headline news in 2006 when its hardware-token-equipped business users became the victims of a large Ukrainian-based man-in-the-middle phishing attack.[citation needed] In 2012, the Prosecco research team at INRIA Paris-Rocquencourt developed an efficient method of extracting the secret key from several PKCS #11 cryptographic devices, including the SecurID 800. [4] [5] These findings were documented in INRIA Technical Report RR-7944, ID hal-00691958, [6] and published at CRYPTO 2012. [7] Digital signature[edit] Trusted as a regular hand-written signature, the digital signature must be made with a private key known only to the person authorized to make the signature. Tokens that allow secure on-board generation and storage of private keys enable secure digital signatures, and can also be used for user authentication, as the private key also serves as a proof for the user’s identity. For tokens to identify the user, all tokens must have some kind of number that is unique. Not all approaches fully qualify as digital signatures according to some national laws.[citation needed] Tokens with no on-board keyboard or another user interface cannot be used in some signing scenarios, such as confirming a bank transaction based on the bank account number that the funds are to be transferred to. Notable vendors and models[edit] Aladdin Knowledge Systems - eToken, some branded for Verisign BCODE Entrust - IdentityGuard Mini Token Mykotronx - Fortezza RSA - SecurID Secure Computing - Safeword Verisign Gemalto AVTOR - Official site of company author.kiev.ua/ See also[edit] Authentication Hardware Security Module Identity management Initiative For Open Authentication Mobile signature Multi-factor authentication Mutual authentication One-time pad Single sign-on Software token References[edit] Jump up ^ de Borde, Duncan (2007-06-28). Two-factor authentication. Siemens Insight Consulting. Retrieved 2009-01-14. Jump up ^ Specification for Integrated Circuit(s) Cards Interface Devices, usb.org Jump up ^ Biba, Erin (2005-02-14). Does Your Car Key Pose a Security Risk?. PC World. Retrieved 2009-01-14. Jump up ^ Somini Sengupta (2012-
Posted on: Wed, 10 Dec 2014 11:02:50 +0000