Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20040103325 A1
Publication typeApplication
Application numberUS 10/305,179
Publication dateMay 27, 2004
Filing dateNov 27, 2002
Priority dateNov 27, 2002
Also published asEP1429229A1, US8495381, US20080028229
Publication number10305179, 305179, US 2004/0103325 A1, US 2004/103325 A1, US 20040103325 A1, US 20040103325A1, US 2004103325 A1, US 2004103325A1, US-A1-20040103325, US-A1-2004103325, US2004/0103325A1, US2004/103325A1, US20040103325 A1, US20040103325A1, US2004103325 A1, US2004103325A1
InventorsMark Priebatsch
Original AssigneePriebatsch Mark Herbert
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Authenticated remote PIN unblock
US 20040103325 A1
Abstract
This invention provides a simple and secure PIN unblock mechanism for use with a security token. A set of one or more passphrases ire stored on a remote sever during personalization. Likewise, the answers to the passphrases are hashed and stored inside the security token for fixture comparison. A local client program provides the user input and display dialogs and ensures a secure communications channel is provided before passphrases are retrieved from the remote server. Retrieval of passphrases and an administrative unblock secret from the remote server are accomplished using a unique identifier associated with the security token, typically the token's serial number. A PIN unblock applet provides the administrative mechanisms to unblock the security token upon receipt of an administrative unblock shared secret. The remote server releases the administrative unblock shared secret only after a non-forgeable confirmatory message is received from the security token that the user has been properly authenticated. The administrative unblock shared secret is encrypted with the token's public key during transport to maximize security.
Images(15)
Previous page
Next page
Claims(24)
What is claimed:
1. A system which facilitates an authenticated user to unblock a temporarily blocked security token comprising:
a security executive associated with said token,
an unblock applet associated with said security executive,
a first secret associated with at least one unblock inquiry, and
a first shared secret associated with said unblock applet;
a client functionally connected to said security token including;
at least one client application for initiating an unblock procedure with said security token and a remote server,
said remote server in processing communications with said client including;
said at least one unblock inquiry,
at least one unblock service application, responsive to said at least one client application, and
a second shared secret,
wherein said at least one unblock inquiry and said second shared secret are progressively sent to said unlock applet for unblocking said security token.
2. The system according to claim 1 wherein said first secret is a one way hash of an answer to said at least one unblock inquiry.
3. The system according to claim 2 wherein said security token further includes a private asymmetric key.
4. The system according to claim 3 wherein said server further includes a public asymmetric key counterpart to said private asymmetric key.
5. The system according to claim 4 wherein said at least one unblock inquiry is encrypted with said public asymmetric key.
6. The system according to claim 1 wherein said first shared secret is equal to said second shared secret.
7. The system according to claim 5 wherein said second shared secret is encrypted with said public asymmetric key.
8. The system according to claim 7 wherein said second shared secret is an administrative PIN.
9. The system according to claim 8 wherein said second shared secret is a synthetic key.
10. The system according to claim 7 wherein said second shared secret is decrypted with said private asymmetric key.
11. The remote server according to claim 1 further including means for providing an audit trail of said unblock procedure.
12. The system according to claim 1 wherein said second shared secret is sent to said security token upon receipt of a properly encoded message by said at least one unblock service application.
13. The system according to claim 1 wherein said at least one unblock inquiry includes a passphrase.
14. The system according to claim 1 wherein said processing communications includes a secure communications protocol.
15. A method for generating and storing at least one passphrase and answers associated with said at least one passphrase, facilitating an authenticated user to unblock a temporarily blocked security token comprising:
generating said at least one passphrase,
associating said at least one passphrase with a unique identifier,
storing said at least one passphrase on a server in a manner retrievable using said unique identifier,
generating said answers associated with said at least one passphrase,
performing a message digest function on said answers associated with said at least one passphrase,
storing a result of said message digest function in a security token associated with said authenticated user, and
wherein said unique identifier is associated with said security token.
16. The method according to claim 15 further including the step of encrypting said at least one passphrase with a public asymmetric key associated with said security token.
17. A method which facilitates an authenticated user to unblock a temporarily blocked security token composing:
a. executing a PIN unblock application on a local client in which said security token operatively is connected,
b. passing a set of parameters from said security token via said PIN unblock application to a remote PIN unblock service,
c. using at least one of said set of parameters for retrieving and locally displaying at least one passphrase from said PIN unblock service,
d. entering an appropriate response to said at least one passphrase,
e. performing a mathematical function on said appropriate response,
f. comparing said result of said mathematical function to an existing reference,
g. sending a confirmatory message to said remote PIN unblock service if said result of said mathematical function matches said existing reference or ending processing if no match is found,
h. retrieving an unblocking secret using said at least one of said set of parameters upon receipt of said confirmatory message,
i. sending said unblocking secret to said security token,
j. unblocking said security token using said unblocking secret.
18. The method according to claim 17 further including the step of using said at least one of said set of parameters to establish a secure communications channel between said remote PIN unblock service and said PIN unblock application
19. The method according to claim 18 further including the step of entering a replacement PIN when prompted by said PIN unlock application.
20. The method according to claim 17 wherein said at least one of said set of parameters includes an authentication challenge, a unique identifier and a digital certificate.
21. A computer program product embodied in a tangible form which provides computer executable instructions to perform the steps of:
a. generating user display and input dialogs,
b. passing a set of parameters from said security token via said PIN unblock application to a remote PIN unblock service,
c. using at least one of said set of parameters for retrieving and locally displaying at least one passphrase from said PIN unblock service,
d. prompting for entry of an appropriate response to said at least one passphrase,
e. performing a mathematical function on said appropriate response,
f. comparing said result of said mathematical function to an existing reference,
g. sending a confirmatory message to said remote PIN unblock service if said result of said mathematical function matches said existing reference or ending processing if no match is found,
h. retrieving an unblocking secret using said at least one of said set of parameters upon receipt of said confirmatory message,
i. sending said unblocking secret to said security token,
j. unblocking said security token using said unblocking secret.
22. The computer program product according to claim 21 further including the step of using said at least one of said set of parameters to establish a secure communications channel between said remote PIN unblock service and said PIN unblock application.
23. The computer program product according to claim 22 further including the step of prompting for the entry of a replacement PIN.
24. The computer program product according to claim 21 wherein said at least one of said set of parameters includes an authentication challenge, a unique identifier and a digital certificate.
Description
FIELD OF INVENTION

[0001] The present invention relates generally to a data processing system and method and more specifically to a data processing system and method for unblocking a security token by an authenticated user.

BACKGROUND

[0002] A security token is used to store an entity, for example a user's digital identity. The digital identity has many uses, such as building access, signing of emails, access to computer systems and obtaining monetary trust. The inherent security mechanism that protects a user's digital identity from being used fraudulently is a combination of security token characteristics and a Personal Identification Number (PIN) known only to the user. The PIN is usually a four digit number which is used to authenticate the user to the security token. Successful authentication of the user to the security token allows the user access to the resources and data contained in or available using the security token.

[0003] The use of a four digit number has an inherent weakness in today's E-commerce environment. A four digit number has only ten thousand possible combinations. As such, access to a lost or stolen security token could easily be accomplished by entry of random PIN combinations until the correct PIN is determined. To address this inherent weakness, a security mechanism is generally incorporated into the security token which counts the number of sequential incorrect PIN entries and blocks the security token from further access after a predetermined number of sequential incorrect PIN entries has occurred. This is the situation in which the security mechanism is designed to protect against.

[0004] The security mechanism, while simple to implement and reasonably effective may inadvertently block out an authorized user due to common keyboarding problems such as a stuck key, incorrectly replaced key cover or difficulty in determining when a keyboard entry has occurred. Another increasingly common problem, a user will have memorized several PINs for various service providers which lends itself to entry of incorrect PINs. Once blocked, the only way that a user can revive access to his or her security token is to have the security mechanism reset by an appropriate support organization.

[0005] This becomes problematic in large organizations as the time and effort to reset the security mechanism usually involves physical presentation of the security token by the user to the support organization. The physical presentation requirement allows the support organization to visually identify the authorized user and maintains close control over post issuance security token management. As is apparent, this process negatively impacts the productivity of both the user and the support organization and increases overall administrative costs to the organization.

[0006] Alternatives to physical presentation of the security token include the use of a telephone support call center. An example of which is disclosed in U.S. Pat. No. 6,360,092 to Carrarra. The '092 patent requires a user to telephone a maintenance center to telemetrically reset the security mechanisms in the token. This method alleviates the physical presentation requirement but does not significantly reduce the productivity loss to the user and the support organization

[0007] Thus, it would be highly advantageous to provide a mechanism which allows an authenticated user to unblock their own security token, while ensuring that the user initiated unblocking procedure is securely performed to prevent fraudulent unblocking or otherwise compromising the resources or data contained in or available using the security token.

SUMMARY

[0008] This invention addresses the limitations described above and provides a secure mechanism to allow an authenticated user to securely unblock his or her security token. This invention provides the advantages Of utilizing normally existing cryptographic and administrative mechanisms to unblock a security token without having to physically identify the end user or require the assistance of a third party and end-to-end security is maintained throughout the PIN reset process using the existing cryptographic and administrative mechanisms.

[0009] The PIN unblock mechanism utilizes responses to one or more passphrases which must be correctly answered before an administrator level PIN reset mechanism is performed. The initial answers to the passphrases are entered during the security token's personalization stage, hashed using a one-way message digest function and stored inside the security token in a maimer not directly accessible via external processes.

[0010] To practice this invention, a token PIN unblock applet is installed in the security token and associated with the token's security executive. The token PIN unblock applet is the only token based applet that a user can successfully initiate after the security token has been locked due to sequential incorrect PIN entries.

[0011] The unblock applet includes the ability to compare the hashed passphrases results to the existing hashed passphrases answers, securely signal the remote server that the passphrases have been correctly answered, securely access cryptographic functions, receive and utilize administrator PIN unblock secrets and perform replacement of the locked user PIN with a new and unblocked user PIN after the security token is unblocked by the remote server. The token PIN unblock applet is written in such a way that it will never return either a cryptographic key or any decrypted data.

[0012] A client PIN unblock application is installed in the user's desktop computer system, preferably as a downloadable browser application, which allows the user to initiate the PIN unblock applet installed in the security token. If the desktop computer system lacks the required client PIN unblock application, the user will need to download the application from a secure website. The client PIN unblock application provides the user interface dialogs, securely stores user inputs, causes a secure communications session to be generated between the desktop computer system, requests retrieval of the set of passphrases from a remote server mid securely passes the hashed results to the passphrases and the administrator PIN unblock secrets to the token unblock applet.

[0013] The remote server housing the passphrases includes a server PIN unblock service which retrieves the proper passphrases associated with the security token, provides the unblocking secret to the token PIN unblock applet following receipt of the signal from the token that the passphrases have been correctly answered and generates an audit trail of the PIN unblock transactions. The stored passphrases and unblock secrets are retrieved from the remote server using a unique identifier associated with the security token.

[0014] All communications between the client and the server are performed using a secure messaging protocol preferably IPsec, Mutual authentication is preferred and utilizes PKI credentials provided by a digital certificate contained in the security token and a separate digital certificated received from the server. The use of mutual authentication provides the additional advantage of preventing denial of service attacks (DoS.)

[0015] All unblock secrets sent from the server PIN unblock service are encrypted with the token's public key obtained from the digital certificate received during mutual authentication.

[0016] The term “security token” as defined herein refers to hardware based security devices such as smart cards, integrated circuit cards, subscriber identification modules (SIM), wireless identification modules (WIM), identification tokens, secure application modules (SAM), hardware security modules (HSM), secure multi-media card (SMMC) and like devices.

BRIEF DESCRIPTION OF DRAWINGS

[0017] The features and advantages of the invention will become apparent from the following detailed description when considered in conjunction with the accompanying drawings. Where possible, the same reference numerals and characters are used to denote like features, elements, components or portions of the invention. It is intended that changes and mollifications can be made to the described embodiment without departing from the true scope and spirit of the subject invention as defined in the claims.

[0018]FIG. 1 is a general block diagram illustrating the major components and general arrangement of the invention.

[0019]FIG. 1A is a detailed block diagram illustrating the arrangement of the PIN unblock applet included in a security token.

[0020]FIG. 1B is a detailed block diagram illustrating the arrangement of the client unblock application included in the local client and its interrelationship with the remote unblocked service included in the remote server.

[0021]FIG. 2 is a detailed block diagram illustrating the initiation of a security token PIN unblock process at the local client where an initial set of parameters is passed from the local client to the remote server.

[0022]FIG. 3 is a detailed block diagram illustrating the initiation of a security token PIN unblock process inside the security token where the initial set of parameters is generated by the security token and passed to the client unblock application.

[0023]FIG. 4 is a detailed block diagram illustrating the continuation of the PIN unblock process between the remote server and the local client where a passphrases is retrieved by the remote server using one of the parameters passed by the client unblock application.

[0024]FIG. 5 is a detailed block diagram illustrating the continuation of the PIN unblock process between the local client and the security token where a hash of answers is received from the client unblock application.

[0025]FIG. 6 is a detailed block diagram illustrating the continuation of the PIN unblock process where an initial challenge is padded, encrypted using a private key forming a cryptogram and passed to the client unblock application.

[0026]FIG. 7 is a detailed block diagram illustrating the continuation of the PIN unblock process between the local client and the remote server where the cryptogram containing a padded challenge is returned to the remote server and verified.

[0027]FIG. 8 is a detailed block diagram illustrating the continuation of the PIN unblock process between the remote server and the local client where a cryptogram containing a PIN unblock secret is returned to the local client and passed to the security token.

[0028]FIG. 9 is a detailed block diagram illustrating the continuation of the PIN unblock process between the security token and the local client where the cryptogram containing the PIN unblock secret is decrypted and used to unblock the security token. An affirmative response is passed from the security token to the local client for routing to the remote server.

[0029]FIG. 10 is a detailed block diagram illustrating the continuation of the PIN unblock process between the local client and the remote server where the affirmative response is sent to the remote server signaling successful completion of the PIN unblock process.

[0030]FIG. 11 is a detailed flow chart illustrating the major steps used in the invention to record and store a set of passphrases.

[0031]FIG. 12 is a detailed flow chart illustrating the major steps used in the invention to unblock a user s security token.

DETAILED DESCRIPTION

[0032] This invention provides a simple and secure PIN unblock mechanism for use with a security token. A set of one or more passphrases which must be answered correctly before an administrative PIN unblock secret is passed to the security token. The initial answers to the passphrases are entered during the security token's personalization stage, hashed using a one-way message digest function and stored inside the security token in a manner not directly accessible via external processes.

[0033] Referring to FIG. 1, a security token 5 is shown functionally connected to a local client 10. The security token includes an a token PIN unblock applet 25 which performs the actual PIN unblock functions based on parameters passed form client PIN unblock application 30 operatively installed in the local client,

[0034] The local client 10 operatively connected 50A to a telecommunications network 20 using a secure messaging protocol In the preferred embodiment of the invention, IPsec is employed. Other secure messaging protocols such as secure socket layer (SSL) encryption, secure shell encryption (SSH) or transport layer security (TLS) may be implemented as well. The client PIN unblock application 30 provides user interface dialogs and passes messages between the token PIN unblock applet 25 and a server PIN unblock service installed on a remote server 15.

[0035] The client PIN unblock application 30 is preferably a downloadable browser application or applet, which allows the user to initiate the PIN unblock applet 25 installed in the security token 5. If the client 10 lacks the required client PIN unblock application 30, the user may download the application form a secure website. The universal resource locator (URL) is usually printed on the back of the security token 5 or is otherwise known to the end user.

[0036] The remote server 15 is shown operatively connected 50B to the network 20 and in processing communications with the local client 10 using the secure messaging protocol. The remote server 15 includes the server PIN unblock service 35. The server PIN unblock service 35 retrieves the applicable passphrases and an administrative unblock secret using parameters supplied or generated by the token PIN unblock applet 25.

[0037] In FIG. 1A the token PIN unblock applet 25 is shown associated with the token's security executive 75. The security executive 75 provides symmetric and asymmetric cryptographic services, random number generation, authentication challenge generation and comparator functions when requested by the PIN unblock applet 25.

[0038] The security executive 75 includes the ability to pass 150 a unique identifier ID 105 to external resources. The unique identifier 105 may be art internally masked token serial number or another obfuscated identifier unique to the security token.

[0039] The token PIN unblock applet 25 communicates 155 with the client unblock application 30 and is the only token based applet that a user can successfully initiate after the security token has been blocked due to sequential incorrect PIN entries. A one-way message digest Hasho 110 of the original answers to the set of passphrases is stored inside the security token and associated with the PIN unblock applet 25. The PIN unblock applet 25 includes the ability to compare the reference one-way message digest Hasho 110 passphrases against a later hashed passphrase result passed to the applet by the client unblock application 30. The one-way message digest preferably uses SHA-1, however, other common message digest functions such as MD-5 may be used as well so long as consistency is maintained between the digest function used to create the reference hash and the subsequent response hash.

[0040] An administrative shared secret Secrett 115 is used to unblock an existing PIN block applet 120. The counterpart shared secret is securely stored on the remote sever and is only passed to the PIN unblock applet 25 after a user has correctly entered the proper passphrases and the resulting hash verified against the reference hash Hasho 110. The token PIN unblock applet 25 provides an encrypted message which is passed to the remote PIN unblock service which signaling successful user authentication. The successful verification of the encrypted message by the remote PIN unblock service causes the administrative counterpart shared secret to be securely sent to the PIN unblock applet 25. This mechanism is discussed in more detail in the discussion that follows herein.

[0041] The administrative shared secret may be a symmetric cryptographic key or an administrative PIN. The PIN block applet 120 monitors the number of sequential incorrect PIN entries and prevents access to end user applets 130 and cryptographic keys 145 when the user's PIN PINb 125 has become been blocked. The token PIN unblock applet 25 includes the functionality to replace 160 the blocked PIN PINb 125 following successful unblocking of the PIN block applet 120. A security mechanism is incorporated into the token PIN unblock applet 25, which after a predefined number of sequential and unsuccessful attempts to unblock the user's PIN results, in the security token becoming unrecoverable by the end user.

[0042] The token PIN unblock applet 25 may access 165 the user's public and private cryptographic keys Kpri 135, Kpub 140 and with the exception of the user's digital certificate certt 142 containing the user's public key Kpub 140, is prohibited by the security executive 75 from exporting any cryptographic keys or PIN data. Operations involving the token's private key Kpri 135 PIN are tightly controlled to limit its use to only those operations necessary to support the token PIN unblock applet 25. The public key infrastructure (PKI) keys in the preferred embodiment of the invention are intended to utilize 1,024 bit RSA keys but may include pretty good privacy (PGP), Diffie-Helman (DIA) or elliptical curve cryptography (ECC).

[0043] Referring to FIG. 1B, the client PIN unblock application 30 is installed in the user's desktop and provides the user display and input dialogs for entry of a replacement PIN PINn 179 and displays the set of passphrases 195 retrieved from the remote server by the remote unblock service 35. If the client 10 lacks the required client PIN unblock application 30, a copy CUA (Common User Access) downloadlable 176 may retrieved from the remote server as previously described.

[0044] Referring to FIG. 2, once the client unblock application 30 is initiated, the user is prompted to enter a replacement PIN PINn 179 which is securely passed 155 to the token unblock applet 25. Concurrently, an authentication challenge Challenget 182 is generated by the token's security executive 75 and passed 150 along with the token's unique identifier 198 and digital certificate cert.t 210 via the client unblock application 30 to 20 the remote unblock service 35. The remote unblock service temporarily stores the initial challenge Challenget 182 and the token's digital certificate certt 210 for future use. In alternate embodiment of the invention, mutual authentications are performed between the client unblock application 30 and the remote unblock service 35 by sending 200 a server based challenge Challenges 215 and digital certificate Cert.s 220 to the client unblock application 30. Both digital certificates certificate cert.t 210 and Cert.s 220 conform to X.509 standards.

[0045] Referring to FIG. 3, the incoming 155 replacement PIN PINn 179 passed by the client unblock application 30 is shown being temporarily stored by the token unblock applet 25. The challenge Challenget 182 is generated by the security executive 75 and passed along with the user's digital certificate certt 142 and unique identifier 105 to the client unblock applet 30 as described above.

[0046] In FIG. 4, a secure communications session is established 50A, 50B between the client unblock application 30 and the remote unblock service 35 based on the latter authentication. The remote unblock service 35 retrieves the stored set of passphrases 195 using the token's unique identifier id 198 as a lookup reference. The passphrases 195 and counterpart administrative secret Secrets 185 were originally stored in a record 188 associated with the token's unique identifier id 198 at the time the security token was personalized.

[0047] In an alternative embodiment of the invention, the contents of the record 188 is separately encrypted with the user's public key. The remote unblock service generates an audit trail 192 of the PIN unblock transactions. The retrieved passphrases 195 are securely passed 20 to the client unblock application 173 where the user is prompted to enter responses 400 to the passphrases 195. The user responses 400 are then hashed Hashn 173 by the client unblock application 30 and securely passed 155 to the token unblock applet 25

[0048] Referring to FIG. 5, the incoming hashed user responses Hashn 173 passed 155 from the client unblock application 30 are received by the token unblock applet 25 and compared to the reference hash Hasho 110. If the incoming hash Hashn 173 does not match the reference hash Hasho 110, the user is alerted that the PIN unblock process has failed by the client unblock application 30 (not shown.) The aforementioned security mechanism incorporated into the token PIN unblock applet 25 prevents excessive multiple attempts at unblocking the security token. No other messages are provided which prevents a sophisticated hacker from attempting to determine where in the process the failure has occurred.

[0049] In FIG. 6, a successful match between the user response Hashn 173 and the reference hash Hasho 110 results in a cryptogram 605 to be generated. The cryptogram is comprised of the original challenge Challenget 182 and padding 600 which is encrypted by the token PIN unblock applet 25 using the private key Kpti 135. The cryptogram is then passed 155 to the client unblock application 30. The random padding 600 is generated by the security executive 75 preferably in accordance with public key cryptographic system (PKCS) #1 specifications. Padding is employed in the preferred embodiment of the invention to prevent surreptitious capture after receipt fly the client, which is particularly advantageous when using an uncontrolled client. The cryptogram will be used by the remote PIN unblock service as a signal that the user has been successfully authenticated.

[0050] In FIG. 7, the cryptogram 605 is received 155 by the client unblock application and passed 20 using the secure messaging protocol 50A, 50B to the remote unblock service 35. The remote unblock service 35 decrypts the cryptogram using the public key Kpub 140 counterpart contained in the previously received digital certificate certt 210.

[0051] The remote unblock service 35 then compares the decrypted result to the original challenge Challenget 182 while ignoring the extraneous padding. If the decrypted challenge does not match the original challenge Challenget 182, the unblock process ends. As before, no other messages are provided. As before, the relate unblock service generates an audit trail 192 of the PIN unblock transactions.

[0052] In FIG. 8, if the decrypted challenge does match the original challenge Challenget 182, the remote unblock service 35 retrieves the counterpart administrative secret Secrets 185 using the token's unique identifier as a lookup reference. The retrieved administrative secret Secrets 185 is then encrypted using the public key Kpub 140. The resulting cryptogram 805 is then passed 20 using the secure messaging protocol 50A, 50B to the client unblock application 30. The client unblock application 30 securely and transparently passes 155 the cryptogram 805 to the token unblock applet 25.

[0053] Referring to FIG. 9, cryptogram 805 is received 155 by the token unblock applet 25 and decrypted using the private key Kpri 135. The resulting administrative secret Secrets 185 is used in combination with the token shared secret Secrett 115 to unblock the PIN block applet 120. The replacement PIN n 179A is then operatively installed as the active user PIN n 179B. After the unblocking process has successfully completed, a completion message 905 is generated by the token unblock applet 25 which is passed 155 to the client unblock application 30.

[0054]FIG. 10, the completion message 905 is then passed 20 using the secure messaging protocol 50A, 50B to the remote unblock service 35 where the audit trail 192 of the PIN unblock transactions is recorded.

[0055] In FIG. 11, the initial process for generating and storing the passphrases is shown. The process is initiated 1100 by the user being prompted for a PIN 1105. The user is then prompted for entry of one or more passphrases 1110. The passphrases are then stored on a server 1145 indexed by a unique identifier associated with the security token. In an alternative embodiment of the invention, the initial passphrases are encrypted 1120 with the user's public key 1115 then stored and indexed as before 1145. The user is then prompted to enter the answers to the passphrase 1125. The answers are hashed 1135 using a one-way hash 1130 and stored inside the user's security token 1140. The process ends 1150 after storage of the hashed passphrase answers.

[0056] Lastly, referring to FIG. 12, the authenticated PIN unblock process is shown. The process is initiated 1200 by requesting the PIN unlock service on a appropriately equipped local client 1205. The local client performs an authentication and establishes a secure path between the local client and a remote server 1215 and transfers necessary parameters to retrieve the stored passphrases 1220. The user is then prompted to enter a new PIN 1230 while the remote server retrieves and passes the user's passphrase to the local client 1240. The passphrases are displayed and the user prompted to enter the appropriate answers 1255. In an alternate embodiment of the invention, the passphrases are decrypted 1250 using the user's private key 1235.

[0057] The user's answers are then hashed 1260 using a one-way hash algorithm 1245 and compared with the stored hashed answered 1265. If the hashed user answers match the stored hashed answers 1270, a confirmatory message is securely sent to the server 1275. The server retrieves and passes an encrypted unblock secret to the security token 1280. The encrypted unblock secret is decrypted 1285 using the private key 1235 and used to unblock the security token 1290 and the new PIN activated 1210.

[0058] Another confirmatory message is securely sent to the server 1295 for audit trail purposes and the process ends 1310. If the hashed user answers do not match the stored hashed answers 1270 and less than n attempts have occurred 1300, the user is prompted to again enter the proper passphrase as before and the process repeated. If greater than n ties has occurred, the token is disabled 1305 and processing ends 1310.

[0059] The foregoing described embodiments of the invention are provided is illustrations and descriptions. They are not intended to limit the invention to precise form described. In particular, it is contemplated that functional implementation of the invention described herein may be implemented equivalently in hardware, software, firmware, and/or other available functional components or building blocks. No specific limitation is intended to a particular security token operating environment. Other variations and embodiments are possible in light of above teachings, and it is not intended that this Detailed Description limit the scope of invention, but rather by the Claims following herein.

Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7222365 *Feb 25, 2005May 22, 2007Metavante CorporationNon-algorithmic vectored steganography
US7536722 *Mar 25, 2005May 19, 2009Sun Microsystems, Inc.Authentication system for two-factor authentication in enrollment and pin unblock
US7617390 *Jun 25, 2004Nov 10, 2009Sun Microsystems, Inc.Server authentication in non-secure channel card pin reset methods and computer implemented processes
US7822209Jun 6, 2006Oct 26, 2010Red Hat, Inc.Methods and systems for key recovery for a token
US8041037 *Oct 4, 2005Oct 18, 2011Massachusetts Institute Of TechnologyCryptographic system and methods using a one way multidimensional function
US8042163 *May 20, 2004Oct 18, 2011Symatec Operating CorporationSecure storage access using third party capability tokens
US8099765 *Jun 7, 2006Jan 17, 2012Red Hat, Inc.Methods and systems for remote password reset using an authentication credential managed by a third party
US8266378Dec 21, 2006Sep 11, 2012Imation Corp.Storage device with accessible partitions
US8321953 *Jul 14, 2006Nov 27, 2012Imation Corp.Secure storage device with offline code entry
US8335920Jun 19, 2007Dec 18, 2012Imation Corp.Recovery of data access for a locked secure storage device
US8341713 *Nov 28, 2006Dec 25, 2012K.K. Athena Smartcard SolutionsDevice, system and method of performing an administrative operation on a security token
US8381294Aug 17, 2011Feb 19, 2013Imation Corp.Storage device with website trust indication
US8387125 *Nov 28, 2006Feb 26, 2013K.K. Athena Smartcard SolutionsDevice, system and method of performing an administrative operation on a security token
US8423783 *May 19, 2010Apr 16, 2013International Business Machines CorporationSecure PIN management of a user trusted device
US8438647Sep 19, 2006May 7, 2013Imation Corp.Recovery of encrypted data from a secure storage device
US8505075May 2, 2009Aug 6, 2013Marble Security, Inc.Enterprise device recovery
US8522326 *Sep 24, 2008Aug 27, 2013Motorola Mobility LlcSystem and method for authenticating a smart card using an authentication token transmitted to a smart card reader
US8543764Sep 10, 2012Sep 24, 2013Imation Corp.Storage device with accessible partitions
US8584222 *Sep 28, 2011Nov 12, 2013Hid Global GmbhSecure pin reset process
US8639873Dec 21, 2006Jan 28, 2014Imation Corp.Detachable storage device with RAM cache
US8639940 *Feb 28, 2007Jan 28, 2014Red Hat, Inc.Methods and systems for assigning roles on a token
US8683088Aug 6, 2009Mar 25, 2014Imation Corp.Peripheral device data integrity
US8745365Aug 6, 2009Jun 3, 2014Imation Corp.Method and system for secure booting a computer by booting a first operating system from a secure peripheral device and launching a second operating system stored a secure area in the secure peripheral device on the first operating system
US8813243 *Feb 2, 2007Aug 19, 2014Red Hat, Inc.Reducing a size of a security-related data object stored on a token
US8832453 *Feb 28, 2007Sep 9, 2014Red Hat, Inc.Token recycling
US20080189543 *Feb 2, 2007Aug 7, 2008Steven William ParkinsonMethod and system for reducing a size of a security-related data object stored on a token
US20090119215 *Nov 7, 2007May 7, 2009Microsoft CorporationSecure e-payments
US20090300756 *Sep 24, 2008Dec 3, 2009Kashyap MerchantSystem and Method for Authentication
US20110131639 *May 19, 2010Jun 2, 2011International Business Machines CorporationSecure PIN Management of a User Trusted Device
US20110270762 *Dec 29, 2010Nov 3, 2011Gsimedia CorporationSecure Data Transfer From a Vending Device to Portable Data Storage Devices
US20110271119 *Apr 30, 2010Nov 3, 2011Gsimedia CorporationSecure Data Storage and Transfer for Portable Data Storage Devices
US20120084855 *Sep 28, 2011Apr 5, 2012Omnikey GmbhSecure pin reset process
US20130097427 *Oct 12, 2011Apr 18, 2013Goldkey Security CorporationSoft-Token Authentication System
WO2005082104A2 *Feb 28, 2005Sep 9, 2005Metavante CorpNon-algorithmic vectored steganography
Classifications
U.S. Classification726/6, 713/185, 726/9
International ClassificationG06F21/00
Cooperative ClassificationG06F21/31, G06F2221/2131
European ClassificationG06F21/31
Legal Events
DateCodeEventDescription
Jan 17, 2003ASAssignment
Owner name: ACTIVCARD, FRANCE
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PRIEBATSCH, MARK;REEL/FRAME:013675/0272
Effective date: 20020111