# US 2013/0159704 A1 · System and method of enforcing a computer policy

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

- Number: US 2013/0159704 A1
- Document ID: US20130159704A1
- Status: Published application
- Kind: A1
- Application number: 13/521,674
- Filed: 2011-01-11
- Published: 2013-06-20
- Earliest claimed: 2010-01-11
- Assignees: Scentrics Information Security Technologies Ltd.
- Inventors: Guruparan Chandrasekaran
- Web page: https://patentgrep.com/patent/US20130159704A1

## CPC

- H04L 9/08: Key distribution {or management, e.g. generation, sharing or updating, of cryptographic keys or passwords (network architectures or network communication protocols for supporting key management in a packet data network H04L63/06)}
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/0844: {with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0897: {involving additional devices, e.g. trusted platform module [TPM], smartcard or USB}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/102: {Entity profiles}
- H04L 2209/127: Trusted platform modules [TPM]
- H04L 2209/80: Wireless
- 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

A method and system of enforcing a computer policy uses a central server to manage user profiles, policies and encryption keys. The server securely supplies the keys to client devices only after checking that the policy has been complied with. The checks include both the identity of the user and the machine identity of the client device. The keys are held in a secure environment of the client device, for example in a Trusted Platform Module (TPM), and remain inaccessible at all times to the end user. Theft or loss of a portable client device does not result in any encrypted data being compromised since the keys needed to decrypt that data are not extractable from the secure environment.

## Claims

### Claim 1

A method of accessing a cryptographic key stored on a remote server in order to perform a cryptographic operation, comprising:
determining the identity of a user;
cryptographically validating the identity of the client device;
determining whether the identity of the user and the identity of the client device satisfy an access condition which is stored on the remote server;
securely transmitting the cryptographic key from the remote server to the client device when the access condition is satisfied; and
using the cryptographic key to perform a cryptographic operation without disclosing the cryptographic key to the user.

### Claim at position 2

2-40. (canceled)

### Claim 41 (depends on 1)

The method of claim 1, wherein the cryptographic operation comprises signing data.

### Claim 42 (depends on 1)

The method of claim 1, comprising using a secure cryptoprocessor to allow the client device's identity to be cryptographically validated or to perform the cryptographic operation.

### Claim 43 (depends on 1)

The method of claim 1, further comprising the client device holding the cryptographic key in volatile memory and clearing the cryptographic key from the memory after performing the cryptographic operation.

### Claim 44 (depends on 1)

The method of claim 1, further comprising the server validating the identity of the client device.

### Claim 45 (depends on 1)

The method of claim 1, further comprising the server verifying the identity of the user.

### Claim 46 (depends on 1)

The method of claim 1, further comprising the client device validating the identity of the server.

### Claim 47 (depends on 1)

The method of claim 1, wherein the cryptographic key is specific to the user.

### Claim 48 (depends on 1)

The method of claim 1, further comprising the remote server transmitting one or more certificates along with the cryptographic key.

### Claim 49

A client device configured to:
allow the device's identity to be cryptographically validated;
receive a securely-transmitted cryptographic key from a remote server; and
use the cryptographic key to perform a cryptographic operation without disclosing the cryptographic key to a user

### Claim 50 (depends on 49)

The client device of claim 49, wherein the cryptographic operation comprises signing data.

### Claim 51 (depends on 49)

The client device of claim 49, comprising a secure cryptoprocessor.

### Claim 52 (depends on 51)

The client device of claim 51, wherein the secure cryptoprocessor comprises a Trusted Platform Module.

### Claim 53 (depends on 51)

The client device of claim 51, configured to use the secure cryptoprocessor to allow the client device's identity to be cryptographically validated or to perform the cryptographic operation.

### Claim 54 (depends on 49)

The client device of claim 49, further configured to hold the cryptographic key in volatile memory and to clear the cryptographic key from the memory after performing the cryptographic operation.

### Claim 55 (depends on 49)

The client device of claim 49, further configured to validate the identity of the server.

### Claim 56

A server on which a cryptographic key and an access condition are stored, wherein the server is configured to:
determine whether the identity of a user and the identity of a client device satisfy the access condition; and
transmit the cryptographic key securely to the client device when the access condition is satisfied.

### Claim 57 (depends on 56)

The server of claim 56, further configured to validate the identity of the client device.

### Claim 58 (depends on 56)

The server of claim 56, further configured to verify the identity of the user.

### Claim 59 (depends on 56)

The server of claim 56, further configured to transmit one or more certificates along with the cryptographic key.
