Abstract:
A portable mass storage device for use in two factor authentication systems and methods. A secure portable mass storage device protects content from being freely copied with security mechanisms and firmware. The security functionality also protects confidential user credentials and passwords, as well as algorithms and seeds needed for two factor authentication or asymmetric authentication methods. A client application residing in the mass storage device acts as both a password manager and an authentication manager that seamlessly performs the authentication procedures in the background while signing a user into various institutions of his choosing. A very high level of security is integrated into a mass storage device the user has for purposes other than two factor authentication, and the convenience of highly secure password management also comes in a convenient pocket sized package easy for the user to transport. This facilitates the acceptance of two factor authentication, and increases security for a wide variety of online transactions.

Description:
PRIORITY CLAIM 
       [0001]    This application is a continuation of U.S. patent application Ser. No. 11/319,259, filed Dec. 27, 2005; and U.S. patent application Ser. No. 11/319,835, filed Dec. 27, 2005, both of which claim the priority benefit of U.S. Provisional Patent Application No. 60/697,906, filed on Jul. 8, 2005; the disclosures of which are incorporated herein by reference in their entireties. 
       RELATED APPLICATIONS 
       [0002]    This application is related to: U.S. patent application Ser. No. 11/285,600, filed Nov. 21, 2005; U.S. patent application Ser. No. 11/317,390, filed Dec. 22, 2005; U.S. patent application Ser. No. 11/317,862, filed Dec. 22, 2005; U.S. patent application Ser. No. 11/317,341, filed Dec. 22, 2005; and U.S. patent application Ser. No. 11/317,339, filed Dec. 22, 2005. All of the aforementioned applications and each application referred to in this application are hereby incorporated by this reference in their entireties. 
     
    
     FIELD OF THE INVENTION 
       [0003]    The present invention relates generally to portable mass storage devices such as the memory cards and portable universal serial bus (“USB”) flash memory drives used to store and transfer large files to and from digital devices, and more specifically to security and access control mechanisms implemented within the devices to access the devices and also other institutions. 
       BACKGROUND 
       [0004]    Remembering passwords is a hassle. The computer at the office requires a user name and password. Each email account requires a user name and password, as does each online account. If security were not an issue, a person would likely have only one username and password for all accounts. 
         [0005]    However, security is a serious issue, and therefore password management and access to accounts is also a serious issue. A number of current approaches address this serious issue in an attempt to either make passwords easier to remember or more robust and resistant to being compromised. 
         [0006]    One approach is the one time password (“OTP”). A one time password is, generally speaking, a value that can be used to access a system once before it is changed. In other words, it is regularly updated (at a certain defined frequency) without the user having to change it. This means that the user submits a unique (password) value that is used only once and the system that he wishes to access verifies that the value is what it should be. Typically this is accomplished with a small device or “token” that generates the password for the user based upon a predictable algorithm. The same predictable algorithm is utilized by a validating entity in the system, and when the algorithms are given the same seed value, the system therefore “knows” what the user&#39;s ever changing one time password value should be at any instant (or count). The most common form of the tokens to date requires that the user read the value from a screen and enter it into a computer. Another recently developed form allows the token to transmit the value directly to the computer. Both of these implementations, and the one time password concept generally, provide a high level of security, but require that the user carry around a token for generation of the one time password values. The tokens are a form of two factor authentication, the user&#39;s secret (password or pin) being one factor, and the OTP value and the hardware (token) necessary to produce it being the second factor. 
         [0007]    Another approach utilizes a password management device. Such a device can keep track of a user&#39;s various passwords and account numbers and submit the proper password(s) for each user account. For example, the user may have a master password for accessing the device, and after the device has verified the user&#39;s master password, it can then submit the actual password for a given account when it is connected to a host computer. The user can either enter his various passwords or passwords can be pushed to the password management device. One such device from SafeNet® (formerly thought to be Rainbow Technologies) is known as the iKey™ and is also capable of encryption and the associated key generation. 
         [0008]    Each of these approaches lacks something and has therefore not achieved a high level of acceptance with the general public. OTP tokens are primarily used today for controlling access to corporate networks and have not been widely accepted for use with systems widely available to the general public, e.g. email providers or on-line auctioneers etc. Currently available password management devices lack the level of security of OTP tokens and systems. 
         [0009]    Each of these approaches requires usage of a dedicated device, or alternatively lacks the ability to generate one time passwords for different institutions while keeping the passwords and associated algorithms and seeds secure. For example, many involve a single purpose keychain token or USB device. Carrying such a device everywhere is an inconvenience and limits user acceptance, especially given that the tech savvy user may already be toting around a cell phone, music player, PDA or Blackberry, digital camera, and other assorted electronic gadgets. 
         [0010]    Therefore, there is a need for a convenient multi-purpose device that integrates one time password generation as part of a robust security and password management system. 
       SUMMARY OF THE INVENTION 
       [0011]    The present invention integrates robust security and the convenience of password management into a portable mass storage device. Since a user typically already has a portable mass storage device for use with his digital camera, music player, PDA, or the like, the added security and convenience impose little burden on the user. This facilitates greater penetration of very secure one time password schemes, and results in significantly less risk for sensitive applications such as on-line banking. Because a secure portable mass storage device can store programs and other secure data, OTP generation and password management can be integrated into one convenient platform. 
         [0012]    One of the barriers to adoption of such two-factor authentication systems in the consumer space is the need for a user to carry a token specifically for the purpose of performing the authentication operation. One way to eliminate this burden of having to carry multiple dedicated devices is to integrate such functionality into a device that a person may possess and/or carry with them for other reasons. An example of such a mass storage device is a USB flash storage device or a mass storage flash memory card such as a compact flash “CF” card, SD card, MMC card, XD card, Memory Stick, TransFlash card, or the like, which is commonly used to store data, and more recently to store and carry applications. Such a device, according to the present invention, performs the basic OTP functionality and carries a client application that could be launched from the mass storage device and executed on the host computer. The client application is responsible for interacting with the device to perform the OTP operation, and to get the OTP value from the device. In another embodiment, the client itself performs the OTP functionality and stores and retrieves information such as the count to and from the device as needed. In either case, the information would be stored in a secure manner, and protected appropriately by some means such as encryption. 
         [0013]    In one embodiment, a single mass storage device may be used to authenticate to a number of independent institutions by maintaining a number of independent seed and count pairs on the device, each one to authenticate independently to a given institution. The authentication with multiple institutions may alternately be achieved with a single seed and count by employing a central location of verifying the authentication information. In either case, the seed or seeds may be loaded into the device or to the client securely either during manufacture of the device, or remotely, preferentially through a secure channel. Secure channels are well known in the art and generally involve a communication protocol whereby communication between two entities is encrypted with a key known only to those two entities. Generally the key is a type of session key that is established with a predefined key exchange protocol between the two entities. 
         [0014]    One of the concerns surrounding authentication systems for consumer use is the ease of use and simplicity of the system. Typically, security adds a level of complexity that is a barrier to adoption. One goal in the design of such systems is to achieve a level of simplicity that makes the security aspects of the user interaction almost transparent to the user. To this end, in the present invention, the security is handled in the background as a part of the normal user activities. 
         [0015]    This invention involves the integration of the OTP functionality directly into the user log on operation such that the user preferably has no involvement in performing the OTP authentication after some initial enrollment and/or activation. In particular, in the preferred embodiments, the OTP functionality is integrated into a USB flash storage device or other common removable storage device, and a client application is also stored on the device itself. The client application is launched from the storage device and executes on the host computer. The application may be launched either manually by the user or the system may be set up to automatically launch the application upon insertion of the device into a host computer. Once launched, the client application performs the tasks of obtaining an OTP value from the mass storage device, and providing the user identity, credentials, and OTP value to the server to which the user is authenticating. Ideally, this is performed either automatically if the client application is dedicated to operate with a single institution, or with a one-click operation using a human interface device such as a mouse or a keyboard to select either an institution icon (corporate logo) or name from a list. 
         [0016]    In another embodiment, the client may be active on the host computer and detect when the user accesses a web page within the list of enrolled institutions in order to activate the log on sequence. The Institution list may be displayed on a graphical user interface (“GUI”) as a list, a drop-down list, a group of icons, a group of corporate logos, or other such representations. The user identity and credentials, and the institution Uniform Resource Locator (“URL”) or other form of web address are also ideally already stored on the removable storage authentication mass storage device, and are retrieved for the authentication. If the device supports a number of independent OTP seeds, or even if it supports a number of independent institutions using the same OTP seeds, then the user identity, credentials, and URL are ideally selected from a list stored on the device according to the particular institution to which the person is authenticating. This system combines the functions of a traditional password manager and an OTP authentication system seamlessly, and performs the log on and authentication operation all with a single click of a button. Although performing all these actions with a single click is preferable in some scenarios, multiple clicks or other user input may be utilized and preferable in other scenarios. 
         [0017]    To ensure that no other person can use the device to authenticate in case of loss or theft, the mass storage device of the present invention is such that it will not work without the user inputting some information that uniquely identifies the person, such as a PIN or password, at least once upon launch of the client application. There are a number of other methods of user identification, such as biometrics, answering questions, etc. In one embodiment, the system may be employed to provide user information for more general two-factor authentication and/or password management operations, some of which information may be more sensitive than other information. The system may be designed to segregate such sensitive information and request user verification, additional entry of a PIN/password, or other action to ensure the user is aware of and authorizes such information to be provided by the system. One example of this may be for credit card authorization and payment. 
         [0018]    In one embodiment, the client may provide the user and authentication information to a web server that will upon receiving valid user credentials and authentication information, will automatically fill out the traditional log-in web page entries that are normally used to log on without the two-factor authentication. This embodiment would enable a given institution to maintain a single web log-on page, while adding a separate system component to handle the two factor authentication. In this case, the two-factor authentication may consist of forms of authentication that do not easily lend themselves to form-filling, as OTP does, but instead may be authentication schemes, such as the public key infrastructure (“PKI”), which typically involve challenge-responses operations. 
         [0019]    As an enhancement to the system, the device may contain a list of institutions to which the user may enroll for authentication. This list may be updated remotely, either by user request, or automatically, by means of the client application. The list may be organized in such a way as to provide preferential placement for paying institutions, or placement on the list itself may be reserved for only paying institutions. The system may also fill in the user&#39;s credentials for him when it detects that a particular web page, for which it has stored credentials, has been opened. This can be done with a program or routine that monitors the port used to communicate with the Internet or WWW. The program monitors the browser installed on the host, and configures the browsers to carry out all data communications with the Internet/WWW through a specific port that it monitors. Monitoring would automatically take place any time the host device is utilized, and would maintain a file of all web sites being visited. If a visited web site is one for which the system maintains the users credentials, it will then log the user on. 
         [0020]    One common method of hacking, commonly referred to as ‘phishing’, is one in which a user is tricked into providing confidential information to a web site disguised as a valid web site. There are a number of ways to counter this form of hacking. The list of participating institutions may be used as a means to provide additional information to the system, such as the valid URLs pertaining to a given institution, the form of authentication or specific protocols employed for authentication, and so on. In one embodiment, the URL embedded in the list of participating institutions may be used to limit the URLs to which a user may enroll with the system. In such an implementation, the list would be preferentially downloaded to the device from a remote server via a secure channel to avoid snooping by third parties. In another implementation, the client may request validation of a URL by establishing a link to a remote server and, preferentially through a secure channel, requesting validation of the URL. The remote server may in one embodiment be an authority server or validation entity such as those seen in  FIGS. 1-3 . In yet another embodiment, the validation of the website may be performed by some form of authentication using a common method such as PKI with certificates, etc. In one implementation, security is added to the web server to ensure a valid device is connected prior to initiating the authentication process. In another embodiment, the web page may activate services on the PC, which on a Microsoft Windows OS may be ActiveX technology, to interact with the authentication client to determine the presence to the device. In a preferred solution, all validation happens logically between the remote server and the device itself, with the local client performing only facilitation of communication. 
         [0021]    All of the above systems include a simple mechanism for transferring the authentication rights from one device to another, as well as the user information and credentials from one device to another. The transferal of authentication rights, which may in one embodiment consist of a device ID and seed, and in others a certificate, key, or other form of information, may be performed by adding the information to a list of inactive devices on the server, a removal of said information from the device via a secure protocol, and a re-provisioning via a secure protocol to a new device upon successful identification of the user, and removal from the list of inactive devices. A similar method may be employed in case of loss of the device by the user, which would entail invalidation of the old device ID and seed at the server, and re-provisioning of the same or new device ID and seed to a new device. 
     
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         [0022]      FIG. 1  is a schematic illustration of a first system according to the present invention. 
           [0023]      FIG. 2  is schematic illustration of a second system according to the present invention. 
           [0024]      FIG. 3A  is block diagram of mass storage device  100 . 
           [0025]      FIG. 3B  is an illustration of the memory space of mass storage flash memory  308  of  FIG. 3A . 
           [0026]      FIG. 3C  is diagram of the client and one time password generator of mass storage device  100 . 
           [0027]      FIG. 4  is an illustration of the functionality of mass storage device  100 . 
           [0028]      FIG. 5A  is an illustration of the entities and interactions involved in device slot binding and device slot activation. 
           [0029]      FIG. 5B  is an illustration of the entities and interactions involved in authentication of a device with a bound slot. 
           [0030]      FIG. 5C  is an illustration of the entities and interactions involved in authentication with a public key infrastructure. 
           [0031]      FIG. 6  is a flowchart of a method of use of mass storage device  100  to sign into institutions, according to an embodiment of the present invention. 
           [0032]      FIG. 7  is a flowchart of a method of use of mass storage device  100  to sign into institutions, according to an embodiment of the present invention. 
           [0033]      FIG. 8  is a flowchart of a method of use of mass storage device  100  to sign into institutions, according to an embodiment of the present invention. 
           [0034]      FIG. 9  is a flowchart of a method of use of mass storage device  100  to sign into institutions, according to an embodiment of the present invention. 
           [0035]      FIG. 10A  is a flowchart of device slot binding as seen in step  905  of  FIG. 9 . 
           [0036]      FIG. 10B  is a flowchart of device slot activation as seen in step  910  of  FIG. 9 . 
           [0037]      FIG. 10C  is a flowchart of authentication as seen in step  915  of  FIG. 9 . 
           [0038]      FIGS. 11A-I  are user interface screens of client  320  according to an embodiment of the present invention. 
           [0039]      FIGS. 12A-B  are user interface screens of client  320  according to an embodiment of the present invention. 
       
    
    
     DESCRIPTION 
       [0040]    Portable mass storage devices are widely used to store digital content such as photographs, music, videos, and documents. They are also sufficiently large to store large software applications. Typically, the portable mass storage devices now use flash memory for storage purposes, and have a form factor of a memory card or portable USB drive. These mass storage devices are distinct from other portable devices that are intended to store very little information such as that required for transaction or identification purposes. Mass storage devices are also distinct from other dedicated purpose devices such as key cards and the tokens used for authentication, because while the dedicated devices may have small amounts of memory to store pertinent user identification information, they are not designed to frequently store and transfer what are comparatively massive and often encrypted files in a rapid, reliable, and repeatable manner. 
         [0041]    For example, a memory card, one embodiment of a portable mass storage device, must be capable of rapidly storing pictures on the order of 5-20 megabytes or more. One single picture from a digital camera may require orders of magnitude more storage than is present in a dedicated purpose device such as a smart card, key card, or token. Furthermore, such a dedicated purpose device is generally not capable of quickly reading and writing files, let alone the relatively large files used with cameras and music players etc. Portable mass storage devices have controllers and firmware with routines that are optimized to read and write to the memory banks very quickly. Furthermore, many of the portable mass storage devices have security and encryption routines to thwart unauthorized copying of the frequently updated content. While dedicated tokens may have some form of security (to protect the seed and/or algorithm), the data on the token is generally static and the security is not designed to protect against unauthorized copying of frequently updated user files. The mass storage device of the present invention may also store the seeds and other information needed for validation and authentication in an area of the mass storage memory that is not subject to logical to physical mapping, in order for the information to be more reliably and quickly retrieved. For more information on this, please refer to U.S. patent application Ser. Nos. 11/317,341 and 11/317,339, which are hereby incorporated by this reference in their entireties. The seeds may also be loaded into hidden partitions of the device. Loading of the seeds, wherever they are stored, may also only be possible if the entity wishing to load the seeds has adequate permission and/or credentials to do so. In certain embodiments, this permission is contained in an access control record, which will be discussed later. 
         [0042]    The present invention utilizes a portable mass storage device for security purposes. The device has security features built into the device that i) limit access to information stored on the device, and ii) make the device function as a type of “key” that allows access to other secure systems and data. The present invention also includes a system that uses a portable mass storage device to verify the credentials of a user. Once verified the user will be allowed access to information he would otherwise not be able to access. 
         [0043]    Typically static passwords have been used to verify the credentials of a user. However, a static password is easy to pilfer and affords little protection, especially given the widespread “phishing” for passwords and other personal information today. As discussed previously in the Background, dedicated OTP token systems have also been implemented. These dedicated tokens are a burden to carry, are costly, and have not been widely accepted in the marketplace. These tokens also do not have the mass storage functionality of a memory card or USB drive. 
         [0044]    Today, almost everybody who has a digital camera, video recorder, PDA, portable music player, or personal computer has a memory card or a pocket sized USB drive, sometimes referred to as a “thumb” drive. The present invention removes the barrier to entry of requiring a separate dedicated token (or other dedicated device) for implementing an OTP. If a user need not carry multiple devices, but can instead utilize something he already has, the acceptance and usage of OTP and two factor authentication should grow substantially. This results in better security measures and less risk of fraud in electronic commerce and other areas. 
         [0045]    Embodiments of this invention comprise a portable storage device such as a USB flash storage device with OTP functionality and a client in the device that upon selection by the user will automatically link to the appropriate institution web page, enter user credentials, perform the OTP transaction with the device, and enter the OTP value to the web page, thus seamlessly performing the entire operation with a single user click. 
         [0046]    Increased security measures are of the utmost importance because identify theft and fraud are becoming ever greater threats to the growth of online financial activity. Banks, brokerages, and other financial institutions are seeking solutions that will enable them to drive more activity online, where the costs can be as little as 0.5% per transaction as compared to the same transaction performed in a branch office. Likewise there are other programs that are being developed around online merchant transaction, safe browsing for children, and so on. The fundamental need of each of these is a means to provide stronger authentication of the individual that overcomes the most common forms of identify theft, which are phishing and hacking to obtain user identity and credentials, and physical theft or copying of credit card information. 
         [0047]    One solution to the problem, and one aspect of the present invention is to provide consumers with a means, or system, of performing two-factor authentication in order to log on or perform transactions online. Two-factor authentication, as implied by the name, requires that a person be in possession of two system components, one of which is typically a physical device uniquely identifying the person, and the other is a piece of information (a secret) that is known only to that person and the entity to which the person would like to authenticate. 
         [0048]    The authenticating or validating entity will typically have a database containing the person&#39;s credentials as well as a means of verifying that the person is in possession of both components of the two-factor authentication system. The person is only authenticated if able to prove possession of both components, and so the most common form of fraud, in which a hacker is able to determine the person&#39;s identity and secret, is thwarted, because the hacker, who typically is never physically near the person, will not have possession of the physical component. Likewise, if the person happens to lose the device, or it is stolen, no one can use the physical component to falsely authenticate without knowledge of the secret. 
         [0049]    The present invention includes cryptographic functionality. In a preferred embodiment it includes a hardware-based cryptographic engine, although the cryptographic functionality can alternatively be primarily firmware based. It is advantageous to include some form of cryptography to increase the effort that would be required to hack the system. An advantage of using a hardware based cryptographic engine is that the firmware can be tied to the cryptographic engine in such a way that the firmware won&#39;t be executed unless singed by the hardware. This means that both the authentic firmware and hardware need to be present for the device to work. One or the other cannot be replaced with pieces designed to compromise the security of the device and allow unauthorized copying of the contents. For more information please refer to U.S. patent application Ser. No. 11/285,600, which is hereby incorporated by this reference in its entirety. 
         [0050]    A PC or cell phone has an open architecture which is vulnerable to all forms of hacking. An advantage of the present invention is that by placing the cryptographic capabilities within the mass storage device, a very secure and limited API can be utilized as compared to what would be present on a typical personal computer (“PC”) or electronic device such as a cellular telephone. The secure API of the mass storage device is such that there is no way for hackers to use a normal logical interface to attempt to discern the cryptographic secrets contained within the mass storage device. In essence the mass storage device of the present invention is made to be much more secure than the host to which it is coupled. 
         [0051]    The secure mass storage device works in tandem with a remotely located server or servers, using the host device essentially as a pass-through. Although in certain embodiments the processor of the host device executes a client that is stored on the mass storage device, in the preferred embodiments the cryptographic and OTP operations are contained exclusively in the mass storage device, which can be constructed, both physically and logically, in a much more protected manner. The secure mass storage device works in conjunction with a remotely located secure entity or entities to form a secure system. Connections between the mass storage device and the secure entities are also secure. The remotely located secure entity is or comprises one or more remote servers, which are typically physically protected from access, and have secure countermeasures that limit the types of interactions that can be performed though the external interface. 
         [0052]    Reference will now be made to the figures.  FIG. 1  illustrates a system with which the portable mass storage device (“MSD”) can be used for authentication and password management. MSD  100  is connected to a host computing device  110  via connection  102 . Connection  102  can be any type of direct or wireless connection. Some examples of a wireless connection include: OTA—over the air—which uses standard phone communication link; radio frequencies some of which involved selected ranges and protocols such as wi-fi (802.11x) and Bluetooth; inductive near field communications (“NFC”); and infrared. In the currently preferred embodiments, MSD  100  takes the form of a USB drive or a memory card, and therefore the connection is direct and the MSD will interface with a receptacle  104  of the host device. As will be discussed in greater detail later, MSD  100  has a mass storage memory used to frequently and rapidly store and retrieve large user files. These user files can be any type of file and commonly include digital photos and music, as well as executable software programs. In the case of a wireless connection  102 , receptacle  104  would not be a physical receptacle but would instead be a wireless transceiver. 
         [0053]    Host computing device  110  can be any type of smart electronic device, and will for convenience be simply referred to as the host. Some examples of host  110  would include a personal computer, cellular telephone, or handheld organizer/email device (“PDA”). In fact, the host can be any electronic device that can be used to access a user&#39;s accounts and/or sites of interest. Host  110  is connected to a network that is in turn connected with various institutions  118  and other entities. Only one institution  118  is shown for simplicity. The network may comprise any type of wide area network such as the Internet, and various types of cellular telephone networks. Certain networks may also utilize satellite communications. One type of entity connected to the network is a validating or authenticating entity  124 . Entity  124  comprises one or more servers. In the case where host  110  is a PC, a virtual private network (“VPN”) connection may be established if desired. In addition to network connection  114  that connects the host to the institution  118 , and network connection  116 , that connects the host to the validating entity  124 , there may also exist a separate, non-network connection  122  between institution  118  and validating entity  124 . Certainly institutions  118  can also communicate with entities  124  over the network as well. 
         [0054]    Host  110  and the components that interact with it will now be described with reference to their currently preferred embodiments, but such a description should in no way limit the scope of the invention, which will be defined by the appended claims. In a preferred embodiment, host  110  is a PC and MSD  100  is a USB thumb drive. As mentioned previously, the host computer may also be a handheld computer, commonly referred to as a PDA, or a cellular phone, or digital camera, or a hybrid device having all of these functions, which may accept a removable storage device. In one embodiment, the storage device or subsystem may be embedded in the host computer. When a user wishes to access a particular institution, say his online bank for example, he plugs MSD  100  into a USB port, a client that resides on MSD is launched by the PC, and the client then signs the user into his bank account or accounts. The validating entity  124  works in conjunction with the institution, the client, the PC, and the MSD, to validate/authorize the user and his MSD before the user will be allowed access to the institution and logged on or signed into the institution. Of course, each institution  118  maintains various databases of its users and their account numbers and secrets (e.g. passwords or PIN numbers). Likewise, the validating entities maintain databases needed to validate/authorize the users and their devices. These processes will be discussed in greater detail later. Also, the client application that resides on MSD  100  can be executed by a processor of host  110  or MSD  100 , and this will depend on the level of security required and the configurations of both host  110  and MSD  100 , as well as the connection  102  between them. In the case where host  110  is a PC, at the moment it is currently preferred that the PC execute the client application. 
         [0055]      FIG. 2  is similar to  FIG. 1  but it makes it clear that the validating entity, which comprises one or more servers, can be on the same premises as the institution and its equipment. In addition, it illustrates an authority  126 . The authority is an entity that provides information to MSD  100  that is necessary for validation/authorization and user sign on. Authority  126  will also be referred to as authority server  126 . For example, the authority  126  may provide the seeds necessary for OTP generation within MSD  100 . Authority  126  is shown as connected to the host  110  via the network connection  128 . In such a scenario, the authority can load the seeds into MSD  100  at any time during the usable life of MSD  100 . It could also change and remove the seeds if necessary. In a scenario where the seeds are loaded at the factory, authority  126  could be directly connected to the MSD without having to connect via a network and host device. Authority  126  could be run by any number of companies or other entities. One such entity might be the manufacturer or provider of the device. For instance, if MSD is produced by SanDisk, the assignee of the present invention, the authority may also be SanDisk or its agent. As another example, authority  126  may be a device distributor such an as employer. Also, the institution  118  or validating entity  124  may provide the information necessary for validation/authorization (e.g. OTP seeds), directly in place of or in conjunction with authority  126 . 
         [0056]      FIG. 3A  illustrates some of the physical components of MSD  100 . Interface  304  sends and receives data and commands to and from MSD  100  and communicates the information with controller  306 . As mentioned previously, interface  304  in some embodiments comprises the electrical contacts and/or connector of the mass storage device, while in other embodiments it comprises a wireless transceiver. In certain of the embodiments, power for MSD  100  may also be received via device interface  304 . Controller  306  comprises a microprocessor and it controls all of the data storage operations of MSD  100 . This means that it orchestrates all of the read and write operations to and from the mass storage memory  308 , which is preferably of the flash variety. Although the controller and mass storage memory are illustrated as being connected serially, they are in reality normally connected via a bus. Also on the bus may be various other components including read only memory (“ROM”) and random access memory (“RAM”). MSD  100  is capable of reading and writing encrypted files in mass storage memory  308 , and this is accomplished in the preferred embodiments with an encryption engine within controller  306 . The controller executes firmware in order to run MSD  100 , and this firmware can be located on a dedicated ROM, or alternatively stored in the flash memory  308 . The firmware is preferably stored in mass storage memory  308 , in order to eliminate the cost of a ROM to store the firmware. Storing the firmware that runs the MSD in the flash memory  308 , which lacks the intrinsic protection of a ROM, requires extensive protection mechanisms in MSD  100  that ensure that the copy protection routines in the firmware cannot be tampered with or that the firmware cannot be entirely replaced with malicious/unsecure firmware. 
         [0057]    As seen in  FIG. 3B , flash memory  308  has a secure area  308 A where the firmware and other information essential to the operation of the MSD is located. In some embodiments, the firmware is encrypted and will not be executed unless it is first determined to be authentic. For more information on authentication of firmware please refer to application Ser. No. 11/285,600, incorporated by reference in its entirety. Also, in some embodiments, writing to the secure area  308  can only be performed in certain operating states of the device. Generally speaking, this also serves to protect from tampering or replacement of the firmware, and for more information on operating states of the mass storage device, please see application Ser. No. 11/053,273, incorporated by reference in its entirety. These protections need to be in place because the mass storage device is used for general purpose file storage, and in particular to store copyrighted works that cannot be freely available for copying. For example, music on the MSD must be protected from unauthorized copying (this is not an issue with dedicated tokens that cannot be used to store user files). This is of particular importance when the firmware for controlling the device resides in the same mass storage memory as the user files, rather than on a dedicated storage device such as a ROM, that is intrinsically more difficult to hack. 
         [0058]    Logical slots  310 A,  310 B . . .  310   x . are located in the secure area  308 A. These slots can also be in the file storage area  308 B. A slot is a protected logical memory area that is used to store the information necessary to log a user into an institution. The information is encrypted as one security measure. This can include the user&#39;s identifying information such as his name address account number etc. . . . , the user&#39;s secret such as a password or PIN, and the information necessary to generate OTP values, including the algorithms and seed values for each institution. Each institution will have its own slot. In certain embodiments, each account within an institution may have its own slot. Login and the use of slots will be explained in more detail later. In an embodiment of the invention, the slots of the MSD may be located in a system area of the mass storage memory that is not subject to logical to physical mapping, in order for the information to be more reliably and quickly retrieved. The seeds used for OTP generation may also be stored in an area of memory  308  that is hidden from a computer that has access to the files in file storage area  308 B. This may be done within a hidden partition located anywhere in memory  308 . 
         [0059]    As mentioned previously, seeds can be loaded into MSD  100  at different times. It is important that an entity wishing to load seeds into the card be verified before loading takes place. In one embodiment, this is managed with a secure storage application (“SSA”), which is a security module of the mass storage device. This can interact with the client application  320  or through a management layer within the device. The SSA and other related information is described in U.S. patent application Ser. No. 11/313,536, which is hereby incorporated by this reference in its entirety. The SSA system sits atop the storage system of the MSD and adds a security layer for stored files and other data, including, in one embodiment, the seeds. 
         [0060]    SSA partitions are hidden (from the host operating system or OS and all other entities) partitions that can be accessed only through the SSA. The SSA system will preferably not allow the host device or other entity to access an SSA partition, other than through a session established by logging onto an access control record (“ACR”). Similarly, preferably the SSA will not provide information regarding the existence, size and access permission of an SSA partition, unless this request is coming through an established session by an appropriate authority or entity. 
         [0061]    Access rights to partitions are derived from a list of permissions contained within the ACR. An ACR also may contain the login algorithm, credentials, and authentication method of or to be used with an entity. When a partition is created, the host provides a reference name or ID for the partition. This reference is used in further read and write commands to the partition. Therefore, in such an embodiment, in order for an entity wishing to load a seed in the MSD, it would have to have the proper permission and/or the proper login algorithm, credentials, and authentication method. 
         [0062]      FIG. 3C  illustrates the divided functionality of the preferred embodiments of MSD  100 . In the preferred embodiments, client application  320  performs many functions, but does not perform the OTP generation. In the preferred embodiments, as discussed earlier, the client is executed on the host (although stored on the MSD), whereas the OTP generation is performed on the MSD. OTP generator  330  is better protected within the secure environs of MSD  100 , as compared to the relatively open and potentially insecure environments that may be present in various host devices. Client  320  will request and subsequently fetch the OTP value generated by OTP generator  330 . OTP generator  330  can use multiple different algorithms in order to provide more security and functionality than prior OTP tokens only capable of using a single algorithm seeded at the time of manufacture. For example, OTP generator  330  can use a unique value generating algorithm for each institution. The OTP generator can be implemented in the logic of the controller  306 , in a programmable logic device, or in a separate dedicated circuitry. The dedicated circuitry can be implemented in an ASIC or with board level circuitry components. 
         [0063]    Client  320  also comprises the device interface  320 A, user interface  320 B, authentication manager  320 C, and provisioning manager  320 D. Client  320  seamlessly logs a user onto his chosen institutions based on user interaction with the user interface  320 A. The user interface triggers the device interface, authentication manager, and provisioning manager without the knowledge or intervention of the user. 
         [0064]      FIG. 4  illustrates the multi purpose functionality of device  100 . MSD  100  has mass storage functionality. This is why a user typically has MSD  100 , to store his files in a convenient pocket sized device. Now the present invention adds the convenience of account management and sign on. This involves both password management and authentication management. Authentication management includes verifying that both the user and his device are who they purport to be and are authorized to access secure institutions. Authentication management involves the usage of specific device identifiers and also the one time passwords generated by OTP generator  330 . Adding the security of OTP generation and two factor authentication to a device a user already has should greatly increase the adoption of OTP usage. Adding the convenience of managing the multiple passwords a person typically has should also make such a device much more interesting and valuable to the user. The increased security, functionality, and convenience will result in a higher acceptance level of two factor authentication at secure institutions as well as among users. 
         [0065]    The intricacies of the processes will now be described in detail with regard to  FIGS. 5A-10C . 
         [0066]      FIG. 6C  outlines two principle steps. First, in step  604 , MSD  100  receives one or more OTP seeds while the device is in the field, or in other words after it has been sold and is in the possession of the user. In one embodiment, one seed per institution is received in the card. In other embodiments, one seed is used to generate values for two or more institutions. While various seeds can be pre-loaded in the device before it is sold to the user or an intermediary, it is preferred that the seeds can be loaded on the fly. Later, in step  608  the received seed(s) are used to sign into various institution(s) with the portable mass storage device  100 . Before the seeds are loaded on the fly, the client may in certain embodiments verify that the MSD connected to the host is capable of performing the requisite OTP generation. One way of doing this is with ActiveX. 
         [0067]      FIGS. 5A and 5B  and the flowcharts of  FIGS. 7-10C  should be viewed in tandem.  FIG. 5A  shows the interaction between each of the entities involved in device slot binding and device slot activation: end user  99 , MSD  100 , client  320 , institution  118 , and validating entity  124 . Device slot binding and activation are performed before MSD  100  can be used to access a particular institution.  FIG. 5B  shows the interaction between each of the entities involved in accessing an institution once a slot of MSD  100  is already bound and activated. The entities illustrated in  FIGS. 5A and 5B  are largely the same, but different functionality of the client  320  is utilized and illustrated. For instance, in  FIG. 5B , the authentication manager  320 C and user interface  320 B of client are involved in the processes, whereas the provisioning manager  320 D of client  320  is active during the device slot binding and activation seen in  FIG. 5A . Also, the institution database  120  of institution  118  is illustrated as a separate logical entity, although it is part of the institution  118 . 
         [0068]      FIG. 7  is a flowchart illustrating the main steps of using MSD  100  to access an institution, at a high level. In step  704 , after MSD  100  has been connected to the computer, the client is launched. The client can be launched by the user, or alternatively can be automatically launched when the connection to the computer is sensed. Next, in step  708 , the user selects the institution he wishes to access though the user interface of the client. Some user interface screens can be seen in  FIGS. 11-12 , and will be described later. Generally the selection will be made via human interface devices of the computer each time the client is launched. However, the user can configure MSD  100  to automatically access an institution when the connection is sensed and the client is launched. 
         [0069]    In step  712 , MSD  100  generates an OTP value for each of the selected institutions. Each institution may have a unique seed and algorithm for OTP generation. In step  716 , the client connects to the selected institutions. Once connected, the client then presents the information necessary to log the user into the selected institutions. This information comprises the user&#39;s identifying information such as his name, account number, or user ID, the user&#39;s secret information such as his password or PIN, and the OTP value for the particular institution if the institution is of the type that requires an OTP value for log in. The information can be gathered from a page of the client user interface that the user fills in, or can be gathered by monitoring the actions of a user as he enters his information in the web page of an institution. In one embodiment, the client may provide the user and authentication information to a web server that will upon receiving valid user credentials and authentication information, will automatically fill out the traditional log-in web page entries that are normally used to log on without the two-factor authentication. This embodiment would enable a given institution to maintain a single web log-on page, while adding a separate system component to handle the two factor authentication. In certain embodiments, the device ID of MSD  100  may also be necessary to log in. In step  724 , user  99  and device  100  are authenticated/validated and the user/device are logged into each selected institution. Finally, once the user is logged in, he can access the institution. In the case where the user is accessing a web site of an institution, the institution web pages are presented to the user in step  728 . Of course, institution interfaces are not limited to web pages, and access of other interfaces are within the scope of the present invention. This is especially relevant when host  110  is something other than a PC. 
         [0070]      FIG. 8  is a flowchart similar to  FIG. 7 , but in  FIG. 8  a third party, which is a party other than the institution and the user/device, takes a role in logging the user into an institution. Only steps differing from that in  FIG. 7  will be described. In step  714 , the client connects the user/device/host to a 3 rd  party rather than to an institution as in step  716  of  FIG. 7 . This 3 rd  party maintains databases of users, devices, institutions, and all the information needed to verify the authenticity and validity of a user and his device. This may include verifying OTP values generated by the MSD. In step  717 , the 3 rd  party authenticates/validates the user/device. Once this happens, the 3 rd  party presents the appropriate information needed to log the user into his selected institutions in step  717 . The 3 rd  party may present OTP values generated either at the MSD level or by the 3 rd  party itself. In step  722  the user is then logged into the institution. 
         [0071]    As mentioned previously, before MSD  100  can be used to log a user into his selected sites, slots within the device should be bound and activated. The user and device must also be authenticated before login is completed, as seen in  FIG. 9 . In step  905  a slot  310  of MSD  100  is bound with a server of the validating entity  124 , which can also be referred to as validation server  124 . This step is described in more detail in the flowchart of  FIG. 10  and is also shown in  FIG. 5A . Next, in step  910 , the slot is activated. This process of activation is described in more detail in the flowchart of  FIG. 10B  and is also shown in  FIG. 5A . In step  915 , the user and slot of MSD  100  is authenticated. This authentication or validation process is described in more detail in the flowchart of  FIG. 10C  and can also bee seen in  FIG. 5B . 
         [0072]      FIG. 10A  illustrates the process of binding (step  905  of  FIG. 9 ) in detail. In step  918  the MSD is first connected to host  110 . In step  920 , the client is launched. Next, in step  922  the user selects an institution he wishes to sign into. Again, the user can do this at this time, or the institutions may be pre-selected from previous user session. In step  924 , a slot within MSD  100  is then allocated for the selected institution or account. In step  926  the clients retrieves the device ID from MSD  100 . Then in step  928 , a unique identifier, which is referred to as the token ID is created from the device ID and the slot ID. In step  930 , MSD  100 , in particular the appropriate slot of MSD  100 , is bound to the validation server  128  using the token ID. In step  932 , an OTP seed is received for the selected institution, and it is then assigned to the allocated slot in step  934 . Steps  924 - 934  are repeated for each institution selected in step  922 . 
         [0073]      FIG. 10B  illustrates the process of device slot activation (step  910  of  FIG. 9 ) in detail. A device slot can be activated after it has been bound. In step  940 , the user enters his user name or other user identifying information and his password or other secret. Next, in step  942 , the OTP generator  330  of MSD  100  generates one or more one time password values for the slot being activated. In step  944 , the slot of the MSD is activated with the institution, and in step  946  the institution and/or the client then requests validation of the slot/MSD/user with the validation server  124 . At the same time, the institution  118  and the validation server  124  validate the slot/MSD/user in steps  948  and  950 . Then, optionally in step  952 , the client and user are notified of the successful activation. 
         [0074]      FIG. 10C  illustrates the process of user and device authentication (step  915  of  FIG. 9 ) in more detail. This is also shown in  FIG. 5B . When the device gets activated it is bound and associated to an institution or account. This is done by using the device ID and slot information. The institution then needs to associate the device and its contents to the user name and password so that it can authenticate the user with device presented information plus the user specific information (user identifying information and secret). In step  960 , the MSD is connected to the host if it is not already connected. Next in step  962 , the client is launched if it is not open and running, and in step  964  the user enters in his identifying information (e.g. user name, account number etc.) and his secret (e.g. password or PIN). Next, in step  966  the OTP generator of MSD  100  generates an OTP value for a particular slot. In step  968 , the OTP value, user identifying information and user secret are submitted to the institution. Then, in step  970  the institution validates that the user for access to the institution. This involves steps  970 A and  970 B. In step  970 A the institution validates the user identifying information and secret with the institutions database(s). It also, in step  970 B, validates OTP value and token ID of MSD  100  with validation server  124 . If then user has been successfully validated in step  970  he is then logged into the institution in step  974 . 
         [0075]    As mentioned, in one embodiment, the client may provide the user and authentication information to a web server that will upon receiving valid user credentials and authentication information, will automatically fill out the traditional log-in web page entries that are normally used to log on without the two-factor authentication. This embodiment would enable a given institution to maintain a single web log-on page, while adding a separate system component to handle the two factor authentication. In this case, the two-factor authentication may consist of forms of authentication that do not easily lend themselves to form-filling, as OTP does, but instead may be authentication schemes, such as PKI, which typically involve challenge-responses operations. 
         [0076]      FIG. 5C  shows one possible implementation of the embodiment that utilizes the public key infrastructure for verification/authorization of credentials. Since transactions can be no more secure than the system in which they occur, the most important element becomes establishing a way for correspondents to locate each other and have confidence that the public key they use truly belongs to the person (or machine) with whom/which they wish to communicate. A Public Key Infrastructure is designed to provide this trust. Using a data element called a digital certificate or public key certificate, which binds a public key to identifying information about its owner, the infrastructure is designed to create the binding, and manage it for the benefit of all within the community of use. 
         [0077]    PKI is an authentication technology. Using a combination of secret key and public key cryptography, PKI enables a number of other security services including data confidentiality, data integrity, and key management. The foundation or framework for PKI is defined in the ITU-T X.509 Recommendation [X.509] which is incorporated by this reference it is entirety. 
         [0078]    End Entities are sometimes thought of as end-users. Although this is often the case, the term End Entity is meant to be much more generic. An End Entity can be an end-user, a device such as a router or a server, a process, or anything that can be identified in the subject name of a public key certificate. End Entities can also be thought of as consumers of the PKI-related services. In the present invention, as seen in the embodiment shown in  FIG. 5 , the end entity is the mass storage device  100  or its user. 
         [0079]    Public keys are distributed in the form of public key certificates by CA  550 . A certificate could be required from MSD  100  so that an institution  118  or validating entity would allow a user of MSD  100  to sign on. A certificate from an institution  118  could also be utilized to prove that the institution is authentic before the MSD would sign the user into the institution. Public key certificates are digitally signed by the issuing CA  520  (which effectively binds the subject name to the public key). CAs are also responsible for issuing certificate revocation lists (“CRLs”) unless this has been delegated to a separate CRL Issuer. CAs may also be involved in a number of administrative tasks such as end-user registration, but these are often delegated to a separate registration authority (“RA”) which is optional and not shown in  FIG. 5C . In practice, CA  520  or another CA can also serve as the key backup and recovery facility although this function can also be delegated to a separate component. CAs are often thought of as the “source of trust” in a PKI. Typically, End Entities are configured with one or more “trust anchors” which are then used as the starting point to validate a given certification path. Once trust is established via the PKI interface, login can take place. 
         [0080]      FIGS. 11A-I  and  12 A-B are interface screens of different embodiments of client  320 . These screens serve to illustrate the convenience of the present invention. To a user, the login process becomes very simple, although relatively complex calculations and interactions are taking place “behind the scenes.” For example, the user is unaware that the device is seeded for each institution selected, that the seed is used by a complex algorithm to generate a new (OTP) value for each login that is validated along with the user&#39;s other information automatically. The present invention combines a very high level of security with seamless automation in password management. This can also include a single sign on in certain embodiments, where the user&#39;s master information is automatically correlated with all the individual passwords and usernames for different institutions. There are a number of other methods of user identification that can be used with the present invention, such as biometrics, answering questions, etc. In one embodiment, the system may be employed to provide user information for more general two-factor authentication and/or password management operations, some of which information may be more sensitive than other information. The system may be designed to segregate such sensitive information and request user verification, additional entry of a PIN/password, or other action to ensure the user is aware of and authorizes such information to be provided by the system. One example of this may be for credit card authorization and payment. 
         [0081]      FIG. 11A  shows a welcome screen, and  FIG. 11B  is an interface where the user can fill out his password and user name to access a particular institution. The user can enter a new institution or access an institution that has previously been configured. In this screen the user can enter the device ID of his MSD, although in the preferred embodiments the client will retrieve this information without the user having to enter it. In  FIG. 11C  a user interface informs the user that the system is binding the MSD to his account(s). In this case the selected institution is a financial institution or broker. As seen in  FIG. 11D , the user can access multiple accounts he may have at a particular institution, and can add, edit, and delete accounts. In  FIG. 11E , the user is asked to enter his master password. This is a password that is later correlated by the system with all the user&#39;s other passwords and account info. Once the user has been bound, in one embodiment, he need only enter this master password and in order to access his account the process will begin at  FIG. 11D , rather than  11 A or  11 B. In  FIG. 11F , the user is asked to wait as the system connects to his account. Next, the user is informed that he is securely connected to his account in  FIG. 11G . At this stage, the web page or other interface of the institution will be opened on the host device of the user. When the user is finished accessing his account(s) he can then click the exit button of the user interface screen shown in  FIG. 11H . The user can then connect to additional accounts, as seen in  FIG. 11   i.    
         [0082]      FIGS. 12A-B  depict user interface screens of another embodiment of client  320 . In  FIG. 12A , icons representing a number of different institutions are simultaneously displayed on one user interface screen. The user can add an institution, also referred to as an “account,” and edit or remove an account. The institutions can be manually added by the user, or alternatively the user could select from a list maintained by the MSD. Such a list would be updated remotely to the MSD from a server, either upon request by the user or automatically based on some schedule of update. The list could also be updated based upon based upon any number of events such as upon request for user enrollment. By clicking on buttons within each of the icons, the user can also access or log into the account and close or log off the account. As seen in  FIG. 12B , when the user clicks on a particular account to open it, the client will allow the user to choose between his accounts at the particular institution, which can also be referred to as “sub-accounts.” 
         [0083]    In a preferred embodiment, once all the accounts shown have been configured, the user would only have to enter his master password for the MSD, and could then simply click on the icon corresponding to the institution he wishes to log into. In other embodiments, individual passwords and/or user ID&#39;s would also need to be entered for added security. 
         [0084]    The operations described in detail earlier in the application that facilitate sign on would then take place seamlessly behind the scenes. This would simultaneously make dealing with logon and password management very convenient for the user, while at the same time providing for a very high level of security that would benefit users and institutions alike. All of this convenience and security are incorporated into a device a user most likely already owns. This is possible, because, unlike in dedicated tokens, the client can be added to the mass storage memory of a pocket sized mass storage device. The portable mass storage device has security, both physical and logical, that are more robust than in an open environment such as a PC, and hacking or “phishing” for information is therefore much more difficult. Also, unlike some mass storage devices that may correlate different passwords or other information, the present invention utilizes algorithms and processes that can generate unique password values that are constantly changing yet instantly verifiable. 
         [0085]    While embodiments of the invention have been described, it should be understood that the present invention is not limited to these illustrative embodiments but is defined by the appended claims. For example, MSD  100  may utilize magnetic disk rather than flash type solid state memory for mass storage purposes, and any manner of symmetric or asymmetric authentication can be implemented for authentication purposes to enhance the traditional security of user selected passwords.