Patent Grant
9798678
One or more aspects relate, in general, to data processing systems, and in particular, to protecting contents of storage in a computer system from unauthorized access.
In cryptography, a cold boot attack, or to a lesser extent, a platform reset attack is a type of side channel attack in which an attacker with physical access to a computer is able to retrieve valuable data, such as encryption keys, from a running operating system after using a cold reboot to restart the machine. The attack relies on the data remanence property of DRAM (dynamic random access memory) and SRAM (static random access memory) to retrieve memory contents that remain readable in the seconds to minutes after power has been removed.
To execute the attack, a running computer is cold-booted. Cold-booting refers to when power is cycled “off” and then “on” without letting the operating system shut down cleanly, or, if available, pressing the “reset” button. A removable disk with a special boot sector might then be immediately booted (e.g., from a USB (universal serial bus) flash drive), and used to dump the contents of pre-boot memory to a file. Alternatively, the memory modules are removed from the original system and quickly placed in a compatible machine under the attacker's control, which is then booted to access the memory. Further analysis can then be performed against the information that was dumped from memory to find various sensitive data, such as the keys contained in it. Automated tools are now available to perform this task for attacks against some popular encryption systems.
Such an attack is a hardware (insecure memory) and not a software issue. Any sensitive data held in memory is vulnerable to the attack.
Other attacks allow encryption keys to be read from memory. For example, a DMA (direct memory access) attack allows physical memory to be accessed via a 1394 DMA channel.
The ability to execute the cold boot attack successfully varies considerably across different systems, types of memory, memory manufacturers and motherboard properties.
A method is provided for protecting contents of storage in a computer system from unauthorized access. The computer system includes one or more processing units sharing the storage. Each processing unit has at least one processor cache. A hypervisor is executed by the computer system. The method includes, for instance: assigning an area of the storage to a protected section; and one of the processing units generating a random protected section key and distributing the protected section key to the other processing units before starting execution of the hypervisor. Each processing unit respectively encrypts or decrypts, with the protected section key, data transferred between its processor cache and the storage, when data relates to the protected section used by the hypervisor, by encrypting the data on or before leaving the processor cache and decrypting the data on or after receiving in the processor cache. Before executing a virtual machine, the hypervisor generates a random virtual machine key, stores the virtual machine key in the protected section and uses a processor instruction to register the virtual machine key for use by the processing units. Each processing unit respectively encrypts or decrypts, with the corresponding virtual machine key, data transferred between its processor cache and the storage, when data relates to storage areas used by a virtual machine, by encrypting the data on or before leaving the processor cache and decrypting the data on or after receiving in the processor cache.
Thus, data never leaves the secure area of the processing units with its processor caches unencrypted when transferred outside to other caches or to the storage.
Further, a computer program product is provided for protecting contents of storage in a computer system from unauthorized access. The computer system includes one or more processing units sharing the storage. Each processing unit has at least one processor cache, wherein a hypervisor is executed by the computer system. The computer program product includes a computer readable storage medium having program instructions embodied therewith. The program instructions are executable by a computer to cause the computer to perform a method including, for instance: assigning an area of the storage to a protected section; and one of the processing units generating a random protected section key and distributing the protected section key to the other processing units before starting execution of the hypervisor; each processing unit respectively encrypting or decrypting, with the protected section key, data transferred between its processor cache and the storage, when data relates to the protected section used by the hypervisor, by encrypting the data on or before leaving the processor cache and decrypting the data on or after receiving in the processor cache; before executing a virtual machine, the hypervisor generating a random virtual machine key, storing the virtual machine key in the protected section and using a processor instruction to register the virtual machine key for use by the processing units; and each processing unit respectively encrypting or decrypting, with the corresponding virtual machine key, data transferred between its processor cache and the storage, when data relates to storage areas used by a virtual machine, by encrypting the data on or before leaving the processor cache and decrypting the data on or after receiving in the processor cache.
Further, a data processing system for execution of a data processing program is provided, including computer readable program instructions for performing a method described above.
One or more aspects together with the above-mentioned and other objects and advantages may best be understood from the following detailed description of the embodiments, but not restricted to the embodiments, wherein is shown in:
In the drawings, like elements are referred to with equal reference numerals. The drawings are merely schematic representations, not intended to portray specific parameters of aspects of the invention. Moreover, the drawings are intended to depict only typical embodiments of aspects of the invention, and therefore, should not be considered as limiting the scope of aspects of the invention.
One or more of the illustrative embodiments described herein provide a method, system, and computer program product for sharing memory between guests. One or more embodiments are sometimes described herein using particular technologies only as an example for the clarity of the description. One or more embodiments may be used for sharing memory between a first guest and a second guest, the first guest running a first operating system and the second guest running a second operating system, where the two operating systems could be the same one, but could also be different operating systems.
Cold boot attack and system administrator intrusion are threats in the data processing sector. Especially in outsourcing environments the customer has to trust the provider. One or more aspects offer a solution to the cold boot attack and prevention for the memory of multi-tenant ready administrator intrusion.
According to an embodiment of the invention, the memory of a hypervisor and its virtual machines is encrypted in the memory chips so that encryption is transparent to the operating systems and the data never leaves a processing unit unencrypted. One or more aspects use different encryption keys for the hypervisor and its virtual machines so that knowing the data (on the clear and encrypted) of an operating system does not enable decryption of the encrypted data of another operating system, which may be, e.g. a multi-tenant system.
According to one or more aspects of protecting contents of the storage 60 in the computer system 210 from unauthorized access, an area of the storage 60 is assigned to a protected section 62. Then, one of the processing units 20, 22, 24, 26 generates a random protected section key 34, and distributes the protected section key 34 to the other processing units 20, 22, 24, 26 before starting execution of the hypervisor 30. Further, each processing unit 20, 22, 24, 26 respectively encrypts or decrypts, with the protected section key 34, data transferred between its processor cache 40, 42, 44, 46 and the storage 60, when data relates to the protected section 62 used by the hypervisor 30, by encrypting the data on or before leaving the processor cache 40, 42, 44, 46 and decrypting the data on or after receiving in the processor cache 40, 42, 44, 46. Further, before executing a virtual machine 10, 12, 14, 16, the hypervisor 30 generates a random virtual machine key 18, stores the virtual machine key 18 in the protected section 62 and uses a processor instruction to register the virtual machine key 18 for use by the processing units 20, 22, 24, 26. Further, each processing unit 20, 22, 24, 26 respectively encrypts or decrypts, with the corresponding virtual machine key 18, data transferred between its processor cache 40, 42, 44, 46 and the storage 60, when data relates to storage areas 64 used by a virtual machine 10, 12, 14, 16, by encrypting the data on or before leaving the processor cache 40, 42, 44, 46 and decrypting the data on or after receiving in the processor cache 40, 42, 44, 46.
The storage 60 may be a main memory of the computer system 210; it could also be a disk drive or any other storage device.
In the embodiment shown in
Thus, data never leaves the secure area of the processing units 20, 22, 24, 26 with its processor caches 40, 42, 44, 46 unencrypted when transferred outside to other caches 50, 52, 54 or to the storage 60.
A protected section key 34 may be generated and stored in the computer system 210, by starting a boot process on one of the processing units 20, 22, 24, 26 as a master processing unit 28. The protected section key 34 for this master processing unit 28 is then generated using a random key generator 38. The master processing unit 28 distributes the protected section key 34 to all other processing units 20, 22, 24, 26 of the computer system 210. Thus, a processing unit 20, 22, 24, 26 may be booting the hypervisor 30 by accessing the protected section 62 using the protected section key 34.
In one or more aspects, existing operating systems and applications do not need to be modified, because one or more aspects are based on the use of two different kinds of keys. Only hardware, firmware, and, depending on the implementation, the hypervisor of the computer systems are to be adapted. The data from the protected section 62 is encrypted by one single protected section key 34, whereas the data from the virtual machines 10, 12, 14, 16 is encrypted by a virtual machine key 18 which is generated for each virtual machine uniquely. Data from a virtual machine 10 is known only to the virtual machine 10 and not to other virtual machines 12, 14, 16. The data is in clear mode when used in the processing units 20, 22, 24, 26, because these processing units 20, 22, 24, 26 possess the keys 18, 34 from the virtual machines and the hypervisor, respectively, whatever data the processing units 20, 22, 24, 26 are operating on. The data is also in clear mode in the processor caches 40, 42, 44, 46, which may be caches of first and second level. The data in the chip caches 50, 52, which are common for several processing units 20, 22, 24, 26, are encrypted by the virtual machine keys 18 and the protected section key 34, respectively, which is also the case for the shared cache 54. When stored in the storage 60, whether in the memory area 62 of the hypervisor 30 or in the memory area 64 of the virtual machines 10, 12, 14, 16, the data is encrypted with the corresponding protected section key 34 or the virtual machine key 18. The protected section 62 is firmware owned memory. The firmware of the computer system 210 may directly access data of the storage 60, because the firmware can access all the keys 18, 34 in the protected section 62, but no customer and no processing unit 20, 22, 24, 26. Similarly the firmware may also access the processor caches 40, 42, 44, 46. Thus, only the firmware may know that data is encrypted, whereas the operating system 90 does not have any knowledge of the encryption method.
A virtual machine key 18 may be generated and stored in the computer system 210, by generating the virtual machine key 18 using the random key generator 38. The virtual machine key 18 is then stored in a virtual machine key table 80 in the protected section 62.
According to one or more aspects, a virtual machine 10, 12, 14, 16 may be started/dispatched in the computer system 210, by looking up a virtual machine key 18 in the virtual machine key table 80 in the protected section 62 and then loading the virtual machine key 18 into one of the one or more processing units 20, 22, 24, 26.
Data may be stored unencrypted in a processor cache 40, 42, 44, 46. A processing unit 20, 22, 24, 26 may thus access data from the storage 60 or a chip cache 50, 52 or a shared cache 54 by, fetching the data from the storage 60 or the chip cache 50, 52 or the shared cache 54, respectively, decrypting the data using the virtual machine key 18 and storing the data in a core processor cache 40, 42, 44, 46.
A processing unit 20, 22, 24, 26 that is running a virtual machine with a virtual machine key 18 may store data to the storage 60 or a chip cache 50, 52 or a shared cache 54 by fetching the data from core processor cache 40, 42, 44, 46, encrypting the data using the virtual machine key 18 from the storage 60 and writing the encrypted data to the storage 60 or the chip cache 50, 52 or the shared cache 54, respectively.
The hypervisor 30 may encrypt data from a core processor cache 40, 42, 44, 46 and write the encrypted data to a storage 60 and/or a processor cache 40, 42, 44, 46 before dispatching a new virtual machine 10, 12, 14, 16 on the same processing unit 20, 22, 24, 26.
The computer system 210, when executing hypervisor code, may therefore use the protected section key 34 for accessing the protected section 62. The hypervisor 30 may access storage 60 of a virtual machine 10, 12, 14, 16 by using the virtual machine key 18 from the virtual machine key table 80. The virtual machine key 18 may be provided by an address to a virtual machine identifier table 82, when the hypervisor 30 is accessing data from a virtual machine 10, 12, 14, 16. Addresses of the virtual machines 10, 12, 14, 16 in the storage 60 may be configured on a memory segment size basis.
One or more aspects use two types of encryption keys: virtual machine keys (per virtual machine), and a protected section key. In
Thus, there is no need to make virtual machine keys visible or controllable by a customer. The operating system in a virtual machine uses clear data and can encrypt its dumps or IO (input/output) data itself.
When OS/application code is running, the virtual machines may access the storage, e.g. the main memory. If data is in the processor cache of a PU, it is unencrypted and can be directly read. If data is in the chip cache, shared cache, or memory, the corresponding VM key is used for memory access. The corresponding PU fetches encrypted data from the chip cache, shared cache, or memory. Data is decrypted using the VM key, and placed in the processor cache. For stores, when data leaves the processor cache into the chip cache, shared cache, or memory, data is encrypted using a VM key before writing it to the chip cache or shared cache or memory. During the next dispatch of a VM with a different VM ID on the same PU, the hypervisor ensures that processor cache data is encrypted with the previous VM key and written to the chip cache or shared cache or memory, before the new VM key is loaded.
When hypervisor code is executed, the firmware uses the protected section key for fetch and hypervisor data area access. If the hypervisor needs to access the VM's storage, an address to virtual machine identifier table lookup is used to find the right VM key for the memory access in the VM key table. The address to the address to virtual machine identifier table lookup may be configured on a memory segment size basis, e.g. 256 MB or 512 MB.
Accesses from IO to VM memory may also use the VM key.
Thus, data processing is configured in three steps. First, in the activation phase, the virtual machines are activated. A processing unit loads a virtual machine, knowing which virtual machine key is to be used to decrypt the corresponding data. Therefore, the processing unit has only the protected section key and the virtual machine key. In the execution phase, the processing unit decrypts data transferred from the storage or otherwise; if data is to be transferred to the storage, data is encrypted. In the switching phase, if the processing unit is to be dedicated to another virtual machine, first the remaining data from the current virtual machine is encrypted and stored back to the storage and the previous virtual machine key will be deleted, before the new virtual machine may be dispatched. Thus, only one set of virtual machine key and protected section key is present in the processing unit at a time.
Referring now to
In data processing system 210 there is a computer system/server 212, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 212 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 212 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 212 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 218 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include the Industry Standard Architecture (ISA), Micro Channel Architecture (MCA), Enhanced ISA (EISA), Video Electronics Standards Association (VESA), and Peripheral Component Interconnect (PCI).
Computer system/server 212 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 212, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 228 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 230 and/or cache memory 232. Computer system/server 212 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 234 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 218 by one or more data media interfaces. As will be further depicted and described below, memory 228 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 240, having a set (at least one) of program modules 242, may be stored in memory 228 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 242 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 212 may also communicate with one or more external devices 214 such as a keyboard, a pointing device, a display 224, etc.; one or more devices that enable a user to interact with computer system/server 212; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 212 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 222. Still yet, computer system/server 212 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 220. As depicted, network adapter 220 communicates with the other components of computer system/server 212 via bus 218. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 212. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
One or more aspects may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of aspects of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
The descriptions of the various embodiments of aspects of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8010763 | Armstrong et al. | Aug 2011 | B2 |
| 8275996 | Melvin | Sep 2012 | B1 |
| 8516271 | Faraboschi et al. | Aug 2013 | B2 |
| 8627112 | Chaturvedi et al. | Jan 2014 | B2 |
| 8656189 | Orsini et al. | Feb 2014 | B2 |
| 8738932 | Lee | May 2014 | B2 |
| 20030118189 | Ibi | Jun 2003 | A1 |
| 20060294288 | Seth | Dec 2006 | A1 |
| 20110293097 | Maino | Dec 2011 | A1 |
| 20120328105 | Mukkara et al. | Dec 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1612671 | Jan 2009 | EP |
| Entry |
|---|
| Chhabra, Siddhartha et al., “i-NVMM: A Secure Non-Volatile Main Memory System with Incremental Encryption,” Jun. 2011, pp. 177-188. |
| Hong, Mei et al., “Dynamic Encryption Key Design and Management for Memory Data Encryption in Embedded Systems,” Aug. 2013, pp. 70-75. |
| “Cold Boot Attack,” http://en.wikipedia.org/wiki/Cold—boot—attack; (downloaded from internet Mar. 10, 2015), pp. 1-5. |
| Axnix, Christine et al., “Protecting Contents of Storage,” U.S. Appl. No. 14/676,866, filed Apr. 2, 2015, pp. 1-29. |
| List of IBM Patents or Patent Applications Treated as Related, Apr. 2, 2015, pp. 1-2. |
| Axnix, Christine et al., “Protecting Storage From Unauthorized Access,” U.S. Appl. No. 14/941,548, filed Nov. 14, 2015, pp. 1-24. |
| Axnix, Christine et al., “Protecting Contents of Storage,” U.S. Appl. No. 14/941,549, filed Nov. 14, 2015, pp. 1-25. |
| List of IBM Patents or Patent Applications Treated as Related, Mar. 17, 2016, pp. 1-2. |
| Notice of Allowance and Fee Due for U.S. Appl. No. 14/676,866, dated Mar. 21, 2017, 23 pages. |
| Final Office Action for U.S. Appl. No. 14/941,549, dated Mar. 29, 2017, 8 pages. |
| Final Office Action for U.S. Appl. No. 14/941,548, dated Mar. 8, 2017, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160292085 A1 | Oct 2016 | US |
