# US 2020/0403803 A1 · Auditably proving a usage history of an asset

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

- Number: US 2020/0403803 A1
- Document ID: US20200403803A1
- Status: Published application
- Kind: A1
- Application number: 16/450,127
- Filed: 2019-06-24
- Published: 2020-12-24
- Earliest claimed: 2019-06-24
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Klaus Werner; Jakob C. Lang; Joerg Schmidbauer; Angel Nunez Mencias
- Web page: https://patentgrep.com/patent/US20200403803A1

## CPC

- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/3247: {involving digital signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Auditably proving a usage history of an asset, in which the asset includes a hardware security module with at least a public key and a private key. A client application logs hash values of a pair of request data and response data. Usage history of the asset is proved. The proving includes verifying, using the public key, a signature of other hash values of the pair of request data and response data. The other hash values are signed with the private key. The proving further includes comparing the hash values logged by the client application with the other hash values.

## Claims

### Claim 1

A computer-implemented method of auditably proving a usage history of an asset, the computer-implemented method comprising:
logging hash values of a pair of request data and response data; and
proving the usage history of the asset, the asset comprising a hardware security module having at least a public key and a private key, the proving comprising:
verifying a signature of other hash values of the pair of request data and response data, the other hash values signed with the private key and stored in a secure database, the verifying comprising verifying the signature of the other hash values with the public key; and
comparing the hash values that are logged with the other hash values stored in the secure database.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising:
generating the response data, by a hardware security module, based on receiving the request data from a server application;
generating, by the hardware security module, the other hash values of the request data and the response data;
sending, by the hardware security module, the response data to the server application; and
signing, by the hardware security module, the other hash values with the private key and sending the signed other hash values to the secure database.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, further comprising:
logging, by the client application, the hash values of the request data and the response data received by the server application;
retrieving the signed other hash values from the secure database;
validating, by the client application, the signature of the other hash values using the public key; and
comparing, by the client application, the hash values logged by the client application with the other hash values stored in the secure database.

### Claim 4 (depends on 2)

The computer-implemented method of claim 2, wherein the server application is controlled by a client.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the hardware security module comprises a counter, and wherein the computer-implemented method further comprises:
incrementing a value of the counter with each new request data;
combining the incremented value of the counter and the signature with the other hash values; and
verifying gapless request processing of the hardware security module by checking a sequence of the counter values.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the secure database is implemented on a server, the server being a blockchain server comprising a blockchain ledger.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the secure database is implemented in the blockchain ledger, and the other hash values that are signed are stored in the blockchain ledger.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the public key is published during an initial setup.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein the logging is performed by a client application.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, wherein the client application comprises a local log file, the local log file storing the hash values received from a server application.

### Claim 11 (depends on 9)

The computer-implemented method of claim 9, further comprising:
using, by the client application, an application programming interface on a server coupled to the client application to retrieve the other hash values from the secure database, the secure database stored on the server.

### Claim 12 (depends on 1)

The computer-implemented method of claim 1, further comprising adding, by the hardware security module, an execution control to the other hash values of the request data and the response data.

### Claim 13

A computer system for auditably proving a usage history of an asset, the computer system comprising:
a memory; and
a processor in communication with the memory, wherein the computer system is configured to perform a method, said method comprising:
logging hash values of a pair of request data and response data; and
proving the usage history of the asset, the asset comprising a hardware security module having at least a public key and a private key, the proving comprising:
verifying a signature of other hash values of the pair of request data and response data, the other hash values signed with the private key and stored in a secure database, the verifying comprising verifying the signature of the other hash values with the public key; and
comparing the hash values that are logged with the other hash values stored in the secure database.

### Claim 14 (depends on 13)

The computer system of claim 13, wherein the method further comprises:
generating the response data, by a hardware security module, based on receiving the request data from a server application;
generating, by the hardware security module, the other hash values of the request data and the response data;
sending, by the hardware security module, the response data to the server application; and
signing, by the hardware security module, the other hash values with the private key and sending the signed other hash values to the secure database.

### Claim 15 (depends on 14)

The computer system of claim 14, wherein the method further comprises:
logging, by the client application, the hash values of the request data and the response data received by the server application;
retrieving the signed other hash values from the secure database;
validating, by the client application, the signature of the other hash values using the public key; and
comparing, by the client application, the hash values logged by the client application with the other hash values stored in the secure database.

### Claim 16 (depends on 13)

The computer system of claim 13, wherein the hardware security module comprises a counter, and wherein the method further comprises:
incrementing a value of the counter with each new request data;
combining the incremented value of the counter and the signature with the other hash values; and
verifying gapless request processing of the hardware security module by checking a sequence of the counter values.

### Claim 17

A computer program product for auditably proving a usage history of an asset, the computer program product comprising:
a computer readable storage medium readable by a processing circuit and storing instructions for performing a method comprising:
logging hash values of a pair of request data and response data; and
proving the usage history of the asset, the asset comprising a hardware security module having at least a public key and a private key, the proving comprising:
verifying a signature of other hash values of the pair of request data and response data, the other hash values signed with the private key and stored in a secure database, the verifying comprising verifying the signature of the other hash values with the public key; and
comparing the hash values that are logged with the other hash values stored in the secure database.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein the method further comprises:
generating the response data, by a hardware security module, based on receiving the request data from a server application;
generating, by the hardware security module, the other hash values of the request data and the response data;
sending, by the hardware security module, the response data to the server application; and
signing, by the hardware security module, the other hash values with the private key and sending the signed other hash values to the secure database.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the method further comprises:
logging, by the client application, the hash values of the request data and the response data received by the server application;
retrieving the signed other hash values from the secure database;
validating, by the client application, the signature of the other hash values using the public key; and
comparing, by the client application, the hash values logged by the client application with the other hash values stored in the secure database.

### Claim 20 (depends on 17)

The computer program product of claim 17, wherein the hardware security module comprises a counter, and wherein the method further comprises:
incrementing a value of the counter with each new request data;
combining the incremented value of the counter and the signature with the other hash values; and
verifying gapless request processing of the hardware security module by checking
