# US 2012/0084562 A1 · Methods and systems for updating a secure boot device using cryptographically secured communications across unsecured networks

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

- Number: US 2012/0084562 A1
- Document ID: US20120084562A1
- Status: Published application
- Kind: A1
- Application number: 13/105,164
- Filed: 2011-05-11
- Published: 2012-04-05
- Earliest claimed: 2010-10-04
- Inventors: Ralph Rabert Farina; Steven Lee Rajcan; Jim R. Trocki; Mark Valleyand
- Web page: https://patentgrep.com/patent/US20120084562A1

## CPC

- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- G06F 21/575: {Secure boot}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- 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

Methods and systems for updating a virtual terminal associated with a secure network are disclosed. One method includes validating at a service enclave an identity of a user of a virtual terminal. The service enclave includes an authorization server, and the virtual terminal is generated from a trusted set of processing modules executing from a secure boot device at a client computing device. The method further includes authorizing the user of the virtual terminal to access a customer enclave and an update enclave based on security credentials received from the virtual terminal. The method also includes, while the user of the virtual terminal establishes a secure connection between the client computing device and the customer enclave, transmitting updates from the update enclave to the client computing device, thereby updating the trusted set of processing modules.

## Claims

### Claim 1

A method of updating a virtual terminal associated with a secure network, the method comprising:
validating at a service enclave an identity of a user of a virtual terminal, the service enclave including an authorization server, and the virtual terminal generated from a trusted set of processing modules executing from a secure boot device at a client computing device;
authorizing the user of the virtual terminal to access a customer enclave and an update enclave based on security credentials received from the virtual terminal; and
while the user of the virtual terminal establishes a secure connection between the client computing device and the customer enclave, transmitting updates from the update enclave to the client computing device, thereby updating the trusted set of processing modules.

### Claim 2 (depends on 1)

The method of claim 1, wherein the customer enclave and the update enclave have separately established secure connections to the client computing device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the customer enclave is located at a customer site, and the update enclave is located at a managed service provider.

### Claim 4 (depends on 3)

The method of claim 3, wherein the service enclave is located at the managed service provider.

### Claim 5 (depends on 1)

The method of claim 1, wherein the service enclave provides authentication and authorization of the client computing device for connection to both the customer enclave and the update enclave.

### Claim 6 (depends on 1)

The method of claim 1, wherein the security credentials received from the virtual terminal includes a security identifier associated with a secure boot device directly communicatively connected to a computing system hosting the virtual terminal.

### Claim 7 (depends on 1)

The method of claim 1, wherein the secure connection transmits split and encrypted data packets between the client computing device and the customer enclave representing transactions sent from the virtual terminal to the customer enclave.

### Claim 8 (depends on 1)

The method of claim 1, wherein validating at a service enclave an identity of a user of a virtual terminal comprises receiving from the service enclave a location of the customer enclave, a location of the update enclave, and a plurality of keys used to establish secure connections to the customer enclave and the update enclave.

### Claim 9 (depends on 8)

The method of claim 8, wherein validating at the service enclave an identity of a user of a virtual terminal further includes receiving an update script

### Claim 10 (depends on 1)

The method of claim 1, wherein transmitting updates from the update enclave to the client computing device comprises transmitting updates to an ephemeral port assigned at the client computing device.

### Claim 11 (depends on 1)

The method of claim 1, further comprising validating at the service enclave an integrity status of a trusted set of software modules installed on the secure boot device.

### Claim 12 (depends on 1)

The method of claim 1, further comprising, prior to validating at the service enclave an identity of a user of the virtual terminal, establishing a secure connection between the virtual terminal on the client computing device and the service enclave based at least in part on the trusted set of processing modules executing from the secure boot device.

### Claim 13 (depends on 1)

The method of claim 1, further comprising, upon termination of the secure connection between the virtual terminal on the client computing device and the service enclave while updates are transmitted from the update enclave, terminating transmission of updates from the update enclave.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
resuming a secure connection between the virtual terminal on the client computer and the service enclave; and
upon resuming the secure connection, resuming transmission of updates from the update enclave to the client computing device.

### Claim 15

A system for updating one or more trusted software modules in a secure boot device directly connected to a client computing system, the system comprising:
a service enclave configured to receive and respond to authentication and authorization requests from a client computing system, and to define one or more communities of interest associated with a secure boot device;
a customer enclave configured to, upon authorization of the secure boot device at the service enclave, establish a secure connection to the client computing system and receive transaction information from the client computing system; and
an update enclave configured to, while the secure connection is established between the customer enclave and the client computing device, establish a second secure connection between the update enclave and the client computing device and update one or more of the trusted software modules.

### Claim 16 (depends on 15)

The system of claim 15, wherein the customer enclave is at a separate location from the update enclave.

### Claim 17 (depends on 15)

The system of claim 15, wherein the service enclave includes an authorization server configured to receive and respond to authorization requests from the client computing device.

### Claim 18 (depends on 15)

The system of claim 15, wherein the service enclave includes an administrative server configured to manage communities of interest, each community of interest defining one or more users and one or more resources the one or more users are authorized to access.

### Claim 19 (depends on 15)

The system of claim 15, wherein the update enclave is collocated with the service enclave.

### Claim 20 (depends on 15)

The system of claim 15, wherein the secure boot device includes a read-only memory portion and a read-write memory portion, the read-only memory portion including a boot module.

### Claim 21 (depends on 15)

The system of claim 15, wherein the update enclave is configured to update one or more trusted software modules stored in the read-write memory portion of the secure boot device.

### Claim 22

A computer-storage medium storing computing instructions which, when executed, implement a computerized method of updating a virtual terminal associated with a secure network, the method comprising:
validating at a service enclave an identity of a user of a virtual terminal, the service enclave including an authorization server, and the virtual terminal generated from a trusted set of processing modules executing from a secure boot device at a client computing device;
authorizing the user of the virtual terminal to access a customer enclave based on security credentials received from the virtual terminal; and
while the user of the virtual terminal establishes a secure connection between the client computing device and the customer enclave, transmitting updates from an update enclave to the client computing device, thereby updating the trusted set of processing modules.
