# US 2013/0212385 A1 · Utilization of a protected module to prevent offline dictionary attacks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0212385 A1
- Document ID: US20130212385A1
- Status: Published application
- Kind: A1
- Application number: 13/370,331
- Filed: 2012-02-10
- Published: 2013-08-15
- Earliest claimed: 2012-02-10
- Assignees: Microsoft Corporation
- Inventors: Stuart Edward Schechter; David Alexander Molnar; Jacob Rubin Lorch; Barry Clayton Bond; Bryan Jeffrey Parno
- Web page: https://patentgrep.com/patent/US20130212385A1

## CPC

- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- G06F 21/31: User authentication
- H04L 9/0877: {using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- G06F 2221/2115: Third party
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Various technologies pertaining to authenticating a password in a manner that prevents offline dictionary attacks are described. A protected module, which can be a hardware security module, a trusted platform module, or the like, is in communication with an authentication server. The protected module comprises a key that is restricted to the protected module. The key is employed in connection with authenticating the password on the protected module.

## Claims

### Claim 1

A method executed by a computer processor in a protected module, the method comprising:
receiving from an authentication server a purported password that corresponds to a username;
receiving from the authentication server a first hash value, the first hash value being previously generated through execution of a hash function over a string that comprises a concatenation of a proper password for the username, and a key, the key restricted such that it cannot be released outside the protected module;
generating a second string that comprises a concatenation of the purported password and the key;
executing the hash function over the second string to generate a second hash value; and
transmitting a signal that indicates whether or not the first hash value is equivalent to the second hash value to the authentication server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the string further comprises a salt that is concatenated with the proper password and the key, and wherein the second string comprises a concatenation of the purported password, the salt, and the key.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
responsive to receiving the purported password, reviewing historical password authorization requests corresponding to the username; and
determining whether or not to authenticate the password based at least in part upon the historical password authorization requests corresponding to the username.

### Claim 4 (depends on 1)

The method of claim 1, the protected module being a hardware security module.

### Claim 5 (depends on 1)

The method of claim 1, the protected module being a Trusted Platform Module.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
updating an audit log responsive to receiving the purported password, wherein updating the audit log comprises:
indicating in the audit log that the purported password has been submitted for the username; and
indicating in the audit log either that the purported password matches the proper password or that the purported password is different from the proper password.

### Claim 7 (depends on 6)

The method of claim 6, further comprising at least one of encrypting at least a portion of the data in the audit log with the key of the protected module or signing at least a portion of the audit log using the key.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
prior to receiving the purported password from the authentication server, receiving an indication from the authentication server that a client computing device has initiated a communication session with the authentication server;
responsive to receiving the indication, generating a nonce; and
transmitting the nonce to the authentication server for transmittal to the client computing device.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
subsequent to transmitting the nonce to the authentication server, receiving ciphertext from the authentication server, the ciphertext being the nonce and the purported password encrypted through utilization of a public key;
decrypting the ciphertext through utilization of a secret key to obtain the nonce, the secret key being restricted to the protected module; and
authenticating the purported password only if the nonce is valid.

### Claim 10

A protected module comprising:
a processor; and
a memory that is operably coupled to the processor, the memory comprising a key that is restricted to the protected module, the memory further comprising a plurality of components that are executed by the processor, the components comprising:
an encrypter component that generates first ciphertext via encrypting first data that is indicative of a proper password for a specified username through utilization of the key, the first ciphertext transmitted to an authentication server for retention in a password database;
a receiver component that, subsequent to the encrypter component transmitting the first ciphertext to the authentication server, receives from the authentication server:
a purported password for the specified username; and
the first ciphertext,
a decrypter component that decrypts the first ciphertext utilizing the key to generate the first data;
a hash component that computes a hash of a data packet that comprises the purported password received from the authentication server to generate second data; and
a comparer component that compares the first data with the second data and transmits a signal to the authentication server that is indicative of whether or not there is a difference between the first data and the second data.

### Claim 11 (depends on 10)

The protected module of claim 10 being a hardware security module.

### Claim 12 (depends on 10)

The protected module of claim 10 being a Trusted Platform Module.

### Claim 13 (depends on 10)

The protected module of claim 10, the first data being the proper password and the second data being the purported password.

### Claim 14 (depends on 10)

The protected module of claim 10, wherein the receiver component receives a salt corresponding to the username from the authentication server, wherein the first data is a hash of a concatenation of the proper password and the salt, wherein the data packet additionally comprises the salt, and wherein the second data is a hash of a concatenation of the purported password and the salt.

### Claim 15 (depends on 10)

The protected module of claim 10, further comprising a logger component that maintains an audit log that indicates which usernames have submitted passwords to the authentication system, at least a portion of the audit log being at least one of encrypted through utilization of the key or signed through utilization of the key.

### Claim 16 (depends on 10)

The protected module of claim 10, the memory further comprising a public key that is shared with other computing devices and a secret key that is restricted to the protected module, the protected module further comprising:
a nonce generator component that generates a nonce responsive to receiving an indication from the authentication server that a client computing device has requested a session with the authentication server, wherein the protected module transmits the nonce to the authentication server to facilitate establishing a secure connection between the protected module and the client computing device.

### Claim 17 (depends on 16)

The trusted protected module of claim 16, wherein the receiver component receives an encrypted data packet generated from the client computing device that includes the nonce, and wherein the decrypter component decrypts the data packet through utilization of the secret key to obtain the nonce, and wherein the purported password is authenticated only if the nonce obtained through decrypting the data packet is valid.

### Claim 18

The protected module of 17, wherein the encrypted data packet further comprises the password.

### Claim 19 (depends on 10)

The protected module of claim 10 being one of a plurality of protected modules that are in communication with the authentication server.

### Claim 20

A computer-readable medium in a protected module comprising instructions that, when executed by a processor in the protected module, cause the processor to perform acts comprising:
responsive to receiving an indication that a client computing device has initiated a session with an authentication server, generating a nonce;
transmitting the nonce to the authentication server while retaining a copy of the nonce in the computer-readable medium, the authentication server configured to authenticate a purported password that corresponds to a particular username;
receiving from the authentication server:
ciphertext, the ciphertext being an encryption of a concatenation of the purported password and the nonce, the concatenation of the purported password and the nonce encrypted through utilization of a public key; and
a first hash value, the first hash value being a hash of a first string that comprises a concatenation of a proper password for the username and a key, the key restricted to the trusted protected module;
utilizing a secret key, decrypting the ciphertext to obtain the purported password and the nonce, wherein the secret key is restricted to the protected module, and wherein the secret key corresponds to the public key;
comparing the nonce with the copy of the nonce retained in the computer-readable medium to determine equivalence therebetween;
subsequent to comparing the nonce with the copy of the nonce, generating a second hash value, the second hash value being a hash of a second string that comprises a concatenation of the purported password and the key;
comparing the first hash value with the second hash value; and
transmitting a signal to the authentication server that is indicative of a difference between the first hash value and the second hash value.
