# US 2012/0084545 A1 · Methods and systems for implementing a secure boot device using cryptographically secure 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/0084545 A1 - Document ID: US20120084545A1 - Status: Published application - Kind: A1 - Application number: 13/105,173 - Filed: 2011-05-11 - Published: 2012-04-05 - Earliest claimed: 2010-10-04 - Inventors: Ralph Rabat Farina; Thomas Nieters; Steven Rajcan; Jim Trocki; Mark Vallevand - Web page: https://patentgrep.com/patent/US20120084545A1 ## 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 A secure boot device, method, and system for securely connecting a client computer having a secure boot device to a remote server over a communications network are disclosed. The secure boot device includes a housing having an integrated communication interface, a controller located within the housing and operatively connected to the communication interface, and a memory communicatively connected to the programmable circuit and the communication interface. The memory securely stores program instructions including a boot module, a client terminal process module, an operating system module, and a secure communications interface module. The secure communications interface module includes program instructions for communicating split and encrypted data communicated between a computing system to which the communication interface is connected and a remote computing system. ## Claims ### Claim 1 A secure boot device comprising: a housing having an integrated communication interface; a controller located within the housing and operatively connected to the communication interface; a memory communicatively connected to the programmable circuit and the communication interface, the memory securely storing program instructions comprising: a boot module; a client terminal process module; an operating system module; and a secure communications interface module, the secure communications interface module including program instructions for communicating split and encrypted data communicated between a computing system to which the communication interface is connected and a remote computing system. ### Claim 2 (depends on 1) The secure boot device of claim 1, wherein the housing is sized to fit in a hand of a user. ### Claim 3 (depends on 1) The secure boot device of claim 1, wherein the communication interface comprises a USB interface. ### Claim 4 (depends on 1) The secure boot device of claim 1, wherein the boot module enables a computing system to which the secure boot device is connected to boot from the secure boot device into the operating system module. ### Claim 5 (depends on 4) The secure boot device of claim 4, wherein the client terminal process module is configured to, when executed, authenticate a user at an authorization server remote from the computing system when booting from the secure boot device. ### Claim 6 (depends on 4) The secure boot device of claim 4, wherein the client terminal process module is configured to, when executed, provide a client terminal at the computing system for communication with the remote computing system, the client terminal configured to generate a user interface useable in connection with the secure communication interface module to communicate with the remote computing system. ### Claim 7 (depends on 4) The secure boot device of claim 4, wherein the operating system module is configured to deactivate one or more hardware devices of the computing system when the computing system is booted from the boot module. ### Claim 8 (depends on 4) The secure boot device of claim 4, wherein the boot module, client terminal process module, operating system module, and secure communications interface module are stored in a secured area of the memory, the secured area of the memory configured to be written to only by authorized computing systems remote from the computing system. ### Claim 9 (depends on 8) The secure boot device of claim 8, wherein the authorized computing systems include the remote computing system and an authorization server remote from the computing system and the remote computing system. ### Claim 10 (depends on 1) The secure boot device of claim 1, wherein the secure communications interface module includes one or more encryption keys configured for use to encrypt and split data transmitted to the remote computing system. ### Claim 11 (depends on 1) The secure boot device of claim 1, wherein the secure communications interface module is configured to generate a security code useable to authenticate the secure boot device at an authentication server or a remote computing system. ### Claim 12 A method of establishing a secure connection between a local computing system and a remote computing system, the method comprising: booting a local computing system from a boot module of a secure boot device, the secure boot device including a memory storing the boot module, a client terminal process module, an operating system module, and a secure communications interface module; authenticating the secure boot device; upon authenticating the user, establishing a secure connection between the local computing system and the remote computing system, the secure connection configured for communication of cryptographically split data. ### Claim 13 (depends on 12) The method of claim 12, wherein authenticating the secure boot device includes: receiving user credentials from a user at the local computing system; transmitting user credentials from the local computing system to an authentication system; selecting one or more encryption keys for use by the local computing system, each of the one or more encryption keys associated with a community of interest that includes the user. ### Claim 14 (depends on 12) The method of claim 12, wherein selecting one or more encryption keys for use by the local computing system includes receiving the one or more encryption keys from the authentication system. ### Claim 15 (depends on 12) The method of claim 12, wherein selecting one or more encryption keys for use by the local computing system include selecting keys from among a set of keys stored in the memory of the secure boot device. ### Claim 16 (depends on 12) The method of claim 12, further comprising, prior to booting the local computing system, configuring the local computing system based on data stored on the secure boot device. ### Claim 17 (depends on 16) The method of claim 16, wherein configuring the local computing system comprises: collecting data for USB configuration; and modifying a BIOS configuration setting of the local computing system to allow the local computing system to boot from the secure boot device. ### Claim 18 (depends on 12) The method of claim 12, wherein the remote computing system comprises a financial institution. ### Claim 19 (depends on 12) The method of claim 12, further comprising, upon booting a local computing system from a boot module of a secure boot device, disabling one or more hardware devices of the local computing system, thereby preventing modification of the operating system module. ### Claim 20 A system for securely connecting a client computer having a secure boot device to a remote server over a communications network, the system comprising: a general purpose computing device having a peripheral interface and a network interface connected to a communications network; a secure boot device connected to the general purpose computing device via the peripheral interface; and a set of processing modules loaded onto the general purpose computing device from the secure boot device that, when executed, provide a secure communications connection over the communications network to a remote server; wherein the set of processing modules comprise: a boot module; a client terminal process module; a small operating system shell; and a secure communications interface module. ### Claim 21 (depends on 20) The secure communication system of claim 20, further comprising an authorization system configured to authorize communication between the general purpose computing device and the remote server based on credentials received from the client terminal process module. ### Claim 22 (depends on 21) The secure communication system of claim 21, wherein the authorization system is located within a service enclave at a managed service provider. ### Claim 23 (depends on 22) The secure communication system of claim 22, wherein the remote server is located within a customer enclave at a managed service provider. ### Claim 24 (depends on 23) The secure communication system of claim 23, wherein the remote server is associated with a financial institution. ### Claim 25 (depends on 20) The secure communication system of claim 20, wherein the remote server is a web services server.