Operating a secure storage device with a non-volatile memory
US-2019228163-A1 · Jul 25, 2019 · US
US10691356B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10691356-B2 |
| Application number | US-201816199402-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 26, 2018 |
| Priority date | Nov 26, 2018 |
| Publication date | Jun 23, 2020 |
| Grant date | Jun 23, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A secure storage device is connected to a computer system. The secure storage device has a memory including a domain and a subdomain storing first and second data, respectively. The computer system includes a first level hypervisor managing a first level virtual machine, which supports a first operating system, and a second level hypervisor. The second level hypervisor manages a second level virtual machine, which supports a second level operating system. A first authentication process for the first level operating system uses first profile data sent by the computer system and a portion of the first data. A second authentication process for the second level operating system uses second profile data sent by the computer system and a portion of the second data. The first data is not accessible by the second level operating system. The second data is not accessible by the first level operating system.
Opening claim text (preview).
What is claimed is: 1. A method for operating a secure storage device, comprising: configuring a computer system with at least one first level hypervisor managing at least one first level virtual machine (VM), the first level VM supporting a first level operating system (OS); configuring the first level virtual machine (VM) of the computer system with at least one second level hypervisor, the second level hypervisor managing at least one second level VM, the second level VM supporting a second level OS; storing first data indicative of the first level OS in a domain of the secure storage device, wherein the first data is not accessible by the second level OS; storing second data indicative of the second level OS in a subdomain of the domain of the secure storage device, wherein the second data is not accessible by the first level OS; storing in the computer system first profile data indicative of the first level OS and the domain of the secure storage device; storing in the computer system second profile data indicative of the second level OS and the subdomain of the secure storage device; sending the first profile data from the computer system to the secure storage device and performing, by the secure storage device, a first authentication process to authenticate the first level OS using the first profile data and a portion of the first data; sending the second profile data from the computer system to the secure storage device and performing, by the secure storage device, a second authentication process to authenticate the second level OS using the second profile data and a portion of the second data; in response to receiving a request from a trusted key entry system by the first level OS to manage the second data, forwarding the received request to the secure storage device by the first level OS, thereby causing the secure storage device to process the request; and in response to receiving by the first or second OS a request to manage the other portion of the first or second data respectively from a trusted key entry system, forwarding by the first OS or the second OS the received request to the secure storage device thereby causing the secure storage device to process the request. 2. The method of claim 1 , further comprising: associating the portion of the first data with a first flag; associating the portion of the second data with a second flag; setting the first flag and second flag for enabling a change of the portions of the first and second data respectively. 3. The method of claim 2 , wherein setting the first or second flag comprises: receiving a request from the trusted key entry system for setting the first or second flag respectively; and forwarding the request to the secure storage device, thereby causing the secure storage device to set the first or second flag. 4. The method of claim 2 , wherein the first and second flags are a same flag. 5. The method of claim 1 , wherein: the portion of the first data includes a first hash, the portion of the second data includes a second hash, the first profile data includes a hash that is generated from a unique identification of the first OS and a configuration data indicative of the domain, and the second profile data includes a hash that is generated from a unique identification of the second OS and a configuration data indicative of the subdomain; and wherein the first authentication process further comprises comparing the hash included in the first profile data with the first hash, and the second authentication process further comprises comparing the hash included in the second profile data with the second hash. 6. The method of claim 1 , wherein the second OS is configured to receive requests from the trusted key entry system via the first OS and to communicate with the secure storage device via the first OS. 7. The method of claim 1 , further comprising: creating a partition in the computer system, the partition including a secure firmware appliance, wherein the performing a second authentication process to authenticate the second level OS includes connecting the trusted key entry system to the partition, connecting the second level OS to the partition, and configuring the second level OS to receive data from the trusted key entry system via the partition and to send data to the secure storage device via the partition. 8. The method of claim 7 wherein the second profile data are sent via the firmware appliance. 9. The method of claim 7 , further comprising: transmitting a first set of keys from the TKE system to the second level OS, transmitting a second set of keys from the TKE system to the secure storage device, and establishing a secure channel between the second level OS and the secure storage device by exchanging the first and second set of keys. 10. The method of claim 9 , the first set of keys include a private key of a first pair of keys and a public key of a second pair of keys, and the second set of keys include a public key of the first pair of keys and a private key of the second pair of keys. 11. The method of claim 1 , wherein the sending of the second profile data is performed in response to a successful authentication of the first level OS. 12. A computer program product comprising a non-transitory computer-readable storage medium having computer-readable program instructions stored thereon, the instructions being for a hardware processor to perform a process for operating a secure storage device, comprising: instructions for configuring a computer system with at least one first level hypervisor managing at least one first level virtual machine (VM), the first level VM supporting a first level operating system (OS); instructions for configuring the first level virtual machine (VM) of the computer system with at least one second level hypervisor, the second level hypervisor managing at least one second level VM, the second level VM supporting a second level OS; instructions for storing first data indicative of the first level OS in a domain of the secure storage device, wherein the first data is not accessible by the second level OS; instructions for storing second data indicative of the second level OS in a subdomain of the domain of the secure storage device, wherein the second data is not accessible by the first level OS; instructions for storing in the computer system first profile data indicative of the first level OS and the domain of the secure storage device; instructions for storing in the computer system second profile data indicative of the second level OS and the subdomain of the secure storage device; instructions for sending the first profile data from the computer system to the secure storage device and performing, by the secure storage device, a first authentication process to authenticate the first level OS using the first profile data and a portion of the first data; instructions for sending the second profile data from the computer system to the secure storage device and performing, by the secure storage device, a second authentication process to authenticate the second level OS using the second profile data and a portion of the second data; instructions for, responsive to receiving a request from a trusted key entry system by the first level OS to manage the second data, forwarding the received request to the secure storage device by the first level OS, thereby causing the secure storage device to process the request; and instructions for, responsive to receiving by the first or second OS a request to manage the other portion of the first or second data respectively from a trusted key entry system, forwarding by the first OS or the sec
by allocating resources to storage systems · CPC title
in relation to access · CPC title
Hypervisor-specific management and integration aspects · CPC title
Isolation or security of virtual machine instances · CPC title
Single storage device · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.