How to reserve security modules, system

The method secures cryptographic adapters for secure guests by reserving them through trusted firmware, addressing vulnerabilities in computing environments where untrusted hypervisors can compromise cryptographic operations, ensuring secure and uninterrupted operation.

JP7578368B2Active Publication Date: 2024-11-06INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022541600
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-01-29
Filing Date
2020-12-10
Publication Date
2024-11-06
Estimated Expiration
2040-12-10

AI Technical Summary

Technical Problem

In computing environments, particularly in cloud environments, secure guests are vulnerable to unauthorized access and configuration changes by untrusted hypervisors, which can compromise the security and integrity of cryptographic operations due to the reassignment of cryptographic adapters at inappropriate times.

Method used

A method and system for securing cryptographic adapters for secure guests by reserving them exclusively through trusted firmware, ensuring that the adapters are only accessible to the intended secure guests and protecting the cryptographic operations from hypervisor interference.

Benefits of technology

Ensures the secure and uninterrupted operation of cryptographic operations for secure guests by preventing unauthorized access and reassignment of cryptographic adapters, maintaining the confidentiality and integrity of guest data throughout its lifetime.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578368000001
    Figure 0007578368000001
  • Figure 0007578368000002
    Figure 0007578368000002
  • Figure 0007578368000003
    Figure 0007578368000003
Patent Text Reader

Abstract

A security module, such as a cryptographic adapter, is reserved for a secure guest of a computing environment. The reserving includes binding one or more queues of the security module to the secure guest. The one or more queues are then managed based on one or more actions related to the reservation.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] One or more aspects relate generally to processing within computing environments, and in particular to protecting data within such environments. [Background technology]

[0002] In a computing environment, cryptographic elements are useful technological components in protecting data. Information may be stored or transmitted in a cryptographically secured form to avoid unauthorized access to the stored or transmitted information. In some cases, software-based techniques may be used to perform such data protection, while in other cases, hardware assistance and security-specific elements may be used. These specific elements may be called Hardware Security Modules (HSMs), and they may be used as part of a computer or information transmission system in a computing environment.

[0003] Hardware security modules may include specialized circuitry to provide data encryption and data decryption functions. These functions may also include generating and storing encryption keys for use by guest systems, also referred to as guests. Various guests (e.g., virtual machines, virtual servers, etc.) are controlled by a hypervisor or virtual machine manager. Different guests managed by a common hypervisor may be created by different owners. A traditional hypervisor has complete control over the guests it hosts. In particular, the hypervisor has the ability to inspect and even modify the memory of the hosted guests. In a cloud environment, the hypervisor and its administrators should be fully trusted.

[0004] Some guests managed by a hypervisor are secure guests. A secure guest is a guest hosted by one or more hypervisors that are not fully trusted. The image of such a guest is protected when it is loaded, and protection of the contents of resources (e.g., memory, central processing unit (CPU) registers, etc.) allocated to that guest is preserved for the entire life of the guest. Protection of the guest includes at least integrity protection (e.g., the hypervisor cannot maliciously modify any guest state), and may additionally include preserving confidentiality of the initial image, code, and data executed within the guest. Examples of environments that are secure guest-enabled include AMD SEV (Advanced Micro Devices Secure Encrypted Virtualization) and POWER® Protected Computation. POWER is a trademark or registered trademark of International Business Machines Corporation in at least one jurisdiction. Summary of the Invention

[0005] The shortcomings of the prior art are overcome and further advantages are provided through the provision of a computer program product for facilitating processing within a computing environment. The computer program product includes at least one computer-readable storage medium readable by at least one processing circuit and having instructions stored thereon for performing a method. The method includes reserving a security module for a secure guest of the computing environment. The reserving includes binding one or more queues to the secure guest that are used to provide the reservation and to communicate with the security module. The one or more queues are managed based on one or more actions related to the reservation.

[0006] Computer-implemented methods and systems relating to one or more aspects are also described and claimed herein. Additionally, services relating to one or more aspects may also be described and claimed herein.

[0007] Additional features and advantages are realized through the techniques described herein.Other embodiments and aspects are described in detail herein and are considered a part of the claimed aspects.

[0008] One or more aspects are particularly pointed out and distinctly claimed as examples in the appended claims. The foregoing, as well as objects, features, and advantages of one or more aspects will become apparent from the following detailed description taken in conjunction with the accompanying drawings, in which the word "reserved" in the drawings is understood to mean "reserved." [Brief description of the drawings]

[0009] [Figure 1A] FIG. 1 illustrates an example of a computing environment that incorporates and uses one or more aspects of the present invention. [Figure 1B] FIG. 1B illustrates further details of the computing environment of FIG. 1A in accordance with one or more embodiments of the present invention. [Diagram 2] 2 illustrates an example of reserving a security module (e.g., a cryptographic adapter) for a guest (e.g., a secure guest) according to an embodiment of the present invention. [Diagram 3] FIG. 2 illustrates an example flow for initiating a guest with a cryptographic adapter in accordance with one or more aspects of the present invention. [Figure 4] FIG. 1 illustrates an example flow for terminating a guest with a cryptographic adapter in accordance with one or more aspects of the present invention. [Diagram 5] FIG. 2 illustrates an example of a flow for sending a request to a cryptographic adapter, in accordance with one or more aspects of the present invention. [Figure 6] FIG. 2 illustrates an example flow for fetching a response from a cryptographic adapter, in accordance with one or more aspects of the present invention. [Figure 7A] FIG. 1 illustrates another example of a computing environment incorporating and using one or more aspects of the present invention. [Figure 7B] FIG. 7B shows further details of the memory of FIG. 7A. [Figure 8] FIG. 1 illustrates one embodiment of a cloud computing environment. [Figure 9] FIG. 2 illustrates an example of an abstraction model layer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] One or more aspects provide the ability to reserve one or more security modules for a guest (e.g., a secure guest). In one example, the security module is a hardware security module (HSM), e.g., a component that is pluggable or individually connected to a computer system. As one particular example, the hardware security module is a cryptographic card or cryptographic adapter (also referred to as a cryptographic adapter), although other examples exist. In one embodiment, a cryptographic adapter (or other security module) is reserved (hereinafter referred to as reserved) for exclusive use by a secure guest if, for example, the cryptographic adapter is in a list of accessible cryptographic adapters included in the metadata used to initiate the secure guest, and the cryptographic adapter has not been reserved (reserved) by another secure guest.

[0011] One embodiment of a computing environment incorporating and using one or more aspects of the present invention is described with reference to Figure 1A. In one example, the computing environment is based on the z / Architecture® hardware architecture provided by International Business Machines Corporation of Armonk, New York. One embodiment of the z / Architecture® hardware architecture is described in "z / Architecture Principles of Operation," IBM Publication No. SA22-7832-11, 12th Edition, September 2017, which is incorporated herein by reference in its entirety. IBM and z / Architecture are registered trademarks or trademarks of International Business Machines Corporation in at least one jurisdiction.

[0012] The computing environment may be based on other architectures; the z / Architecture(R) hardware architecture is only one example.

[0013] 1A, computing environment 100 includes a computer system 102, shown, for example, in the form of a general-purpose computing device. Computer system 102 may include, but is not limited to, one or more processors or processing units 104 (e.g., central processing unit (CPU)), memory 106 (also known, for example, as system memory, main memory, primary storage, central storage, or storage), and one or more input / output (I / O) interfaces 108 coupled together via one or more buses or other connections 120 or both.

[0014] Bus 120 represents any one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor bus or local bus using any of a variety of bus architectures, including, by way of example and not limitation, Industry Standard Architecture (ISA), MicroChannel Architecture (MCA), Enhanced ISA (EISA), Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI).

[0015] Memory 106 may include a cache, such as, for example, a shared cache 122, which may be coupled to a local cache 123 of processor 104. Additionally, memory 106 may include one or more application programs 124, an operating system 126, and one or more computer readable program instructions 128. Computer readable program instructions 128 may be configured to perform functions of embodiments of aspects of the present invention.

[0016] Computer system 102 may communicate with one or more external devices 130, one or more network interfaces 132, and / or one or more data storage devices 134, for example, via I / O interface 108. Exemplary external devices include user terminals, tape drives, pointing devices, displays, etc. Network interface 132 enables computer system 102 to communicate with one or more networks, such as a local area network (LAN), a general wide area network (WAN), or a public network (e.g., the Internet), or a combination thereof, to provide communication with other computing devices or systems.

[0017] The data storage device 134 may store one or more programs 136, one or more computer readable program instructions 138, or data, or a combination thereof, etc. The computer readable program instructions may be configured to perform the functions of an embodiment of an aspect of the present invention.

[0018] The computer system 102 may include and / or be coupled to removable / non-removable, volatile / non-volatile computer system storage media. For example, it may include and / or be coupled to non-removable, non-volatile magnetic media (commonly referred to as a "hard drive"), a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a "floppy disk"), and / or an optical disk drive for reading from and writing to a removable, non-volatile optical disk, such as a CD-ROM, DVD-ROM, or other optical media, or a combination thereof. It should be understood that other hardware and / or software components may be used in conjunction with the computer system 102. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archiving and storage systems.

[0019] Computer system 102 can operate with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, or configurations, or combinations thereof, that may be suitable for use with computer system 102 include, but are not limited to, personal computer (PC) 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.

[0020] Further details of one embodiment of a computing environment (e.g., computing environment 100) incorporating and / or using one or more aspects of the present invention are described with reference to Figure 1B. In one example, computing environment 100 is a shared computing environment that includes a system, such as computer system 102, and a security module, such as hardware security module (HSM) 150. In the examples herein, the security module is a hardware security module, and in one particular example is a cryptographic adapter 152, although in other embodiments other security modules may be used.

[0021] Computer system 102, in one example, includes trusted components such as trusted firmware 160 and a hypervisor 170 that interacts with one or more guests (e.g., virtual machines (VMs)), including one or more secure guests 180. The firmware (e.g., trusted firmware 160) includes, for example, processor microcode. It includes, for example, hardware level instructions and / or data structures used in implementing higher level machine code. In one embodiment, it includes, for example, proprietary code, which includes trusted software or microcode that is specific to the underlying hardware, typically provided as microcode, that controls operating system access to the system hardware.

[0022] A hypervisor (e.g., hypervisor 170) may also be referred to as a host. One example of a hypervisor 170 is the z / VM® hypervisor offered by International Business Machines Corporation of Armonk, New York. z / VM is a registered trademark or trademark of International Business Machines Corporation in at least one jurisdiction. The hypervisor manages guests that run within the computer system.

[0023] A guest or guest system is, for example, an operating system running in a virtual machine (VM) on a hypervisor. The hypervisor is used to assign one or more specific hardware security modules (e.g., hardware security module 150) to a guest system. The specific hardware security module (e.g., hardware security module 150) assigned to a guest may be configured with a cryptographic master key (also known as a master key or wrapping key) that is used to wrap the guest's key to provide a secure key for the guest.

[0024] One or more of the guests are considered secure guests (e.g., secure guest 180). A secure guest is a guest whose state and memory are protected from hypervisor access. A secure guest is initiated, for example, using metadata that is sent to a trusted component (e.g., trusted firmware 160) in a confidentiality-protecting and integrity-protecting manner.

[0025] In one example, trusted firmware 160 includes multiple control blocks, including, for example, a secure guest control block 162 and a security module control block, such as hardware security module control block 164. Secure guest control block 162 includes configuration information for each secure guest that pertains to one or more security modules reserved for each guest. In the example herein, the security modules reserved for the guest are cryptographic adapters, and thus, in one example, the configuration is referred to as a secure guest cryptographic adapter configuration 166. Secure guest control block 162, in one example, includes a configuration 166 for each secure guest in the system. A particular secure guest's configuration 166 includes, for example, a list of accessible cryptographic adapters included in the metadata used to start that secure guest.

[0026] In one example, hardware security module control block 164 includes one or more queues 168 used by a system (e.g., computer system 102) to communicate with each cryptographic adapter to which the system has access, and reservation information 169 for each cryptographic adapter. As one example, one or more queues 168 include at least one request queue 168a used to contain requests sent to a cryptographic adapter assigned to that queue, and at least one response queue 168b for receiving responses from the cryptographic adapter. In one example, the same queue may be used for requests and / or responses for a particular cryptographic adapter. Other examples are possible.

[0027] The reservation information 169 includes, for example, an indication of whether the cryptographic adapter is reserved and, if so, by which guest. In one example, when a cryptographic adapter (or other security module) is reserved for a guest (e.g., secure guest 180), the guest has exclusive access to the cryptographic adapter.

[0028] In systems that support virtualization, such as System z® offered by International Business Machines Corporation (System z is a trademark or registered trademark of International Business Machines Corporation in at least one jurisdiction), the hypervisor may change the configuration of a guest at any time during the guest's life. For example, a malicious or poorly programmed hypervisor may configure the access of a cryptographic adapter from being accessible first by a first guest and then by a second guest. Due to the asynchronous nature of most cryptographic requests to a cryptographic adapter, it may therefore occur that for a request issued by a first guest, the response is accessible by a second guest. However, for secure guests, the assumption is that they are executed securely even if the hypervisor is not trusted, and therefore the system should prevent a second guest's access to a cryptographic adapter assigned to a first secure guest while the first secure guest is running or retrieving the results of a cryptographic request issued by the first secure guest to the cryptographic adapter. In addition, a secure guest should be able to detect when the master key for a cryptographic adapter is changed while the secure guest has access to that adapter.

[0029] One or more aspects of the present invention address, at a minimum, the above-mentioned problems with reassigning cryptographic adapters at inopportune times. According to one or more aspects of the present invention, one or more cryptographic adapters (or other security modules, or both) are reserved for a guest such that the guest has exclusive access to the cryptographic adapters. Details regarding reserving cryptographic adapters for a secure guest are described with reference to FIGS. 2-6. In particular, FIG. 2 illustrates an example of logic for reserving a security module (e.g., a cryptographic adapter) for a secure guest, FIG. 3 illustrates an example of logic for initiating a guest with a cryptographic adapter, FIG. 4 illustrates an example of logic for terminating a guest with a cryptographic adapter, FIG. 5 illustrates an example of logic for sending a request to a cryptographic adapter, and FIG. 6 illustrates an example of logic for fetching a response from a cryptographic adapter.

[0030] 2, to secure a security module for a secure guest (e.g., secure guest 180), in step 200, a trusted component (e.g., trusted firmware 160) obtains a request to secure a security module (e.g., cryptographic adapter 152) for the secure guest. By way of example, such a request may be obtained by the trusted component upon initiating the secure guest, or the request may be submitted by the secure guest if the security module was not successfully secured when the secure guest was initiated, or if the security module was lost due to loss (e.g., temporary loss) of the security module. Other examples are possible.

[0031] Based on obtaining the request, a determination is made at inquiry 202 whether the security module is included in a list of accessible security modules included in the metadata used to start the guest. In one embodiment, this is determined using secure guest configuration 166. If the security module is not on the list, the process is completed and, in one embodiment, an error code is returned. The security module is not reserved for the guest. However, if the security module is on the list of accessible security modules, a further determination is made at inquiry 204 as to whether the security module has already been reserved, e.g., by another guest. This is determined, for example, by checking reservation information 169. If it has already been reserved, e.g., by another guest, the process is completed and, in one embodiment, an error code is returned. However, if the security module has not already been reserved, at step 206, the security module is reserved for the guest. Reservation may include, for example, at step 208, binding one or more queues (e.g., request queue 168a / response queue 168b) to the guest. Binding includes indicating the reservation in a control block, such as in reservation information 169 of HSM control block 164.

[0032] Based on reserving the security module for the guest, in step 210, one or more queues bound to the guest are used and / or managed, and / or the events and / or the reservation itself are managed based on an action related to the reservation. For example, the action may include submitting a request to a queue, where managing may include verifying that the security module is reserved for the secure guest and allowing the action based on verifying that the security module is reserved for the secure guest and the request was issued by the secure guest, and / or the action may include fetching a response from a queue, where managing may include verifying that the security module is reserved for the secure guest and allowing the action based on verifying that the security module is reserved for the secure guest and the fetch action was issued by the secure guest. Still further, the action may include losing access to the security module, where managing may include flushing one or more queues. As a further example, the action may include terminating the secure guest and managing may include removing one or more pending requests from one or more queues. As further examples, a request from the secure guest may be refused to be sent to a queue not reserved for the secure guest; a response to the secure guest that was fetched from a queue not reserved for the secure guest may be refused to be passed; and / or an error code may be returned to the secure guest when the secure guest attempts to access a queue not reserved for the secure guest. Many other actions, events, and / or management may occur. Additionally, as shown herein, the examples refer to a cryptographic adapter, but this logic applies equally to other security modules.

[0033] Further details regarding securing the security module to secure guests are described with reference to FIGS.

[0034] 3, one embodiment of starting a guest (e.g., secure guest 180) with a cryptographic adapter (e.g., cryptographic adapter 152) is described. Initially, a hypervisor (e.g., hypervisor 170) requests, at step 300, to start a secure guest (e.g., secure guest 180) that is to be configured with a cryptographic adapter (e.g., cryptographic adapter 152, or other security module). A trusted component (e.g., trusted firmware 160) receives the request, at step 302, and checks whether the cryptographic adapter has already been reserved, for example, by another guest. This may include, for example, checking reservation information 169. If the cryptographic adapter is reserved, at query 304, the cryptographic adapter is not accessible to the secure guest, and therefore, at step 306, the guest is not started with the cryptographic adapter. In this case, another request may be issued to start the guest with a different cryptographic adapter (or other security module), or a single request may include multiple cryptographic adapters (or other security modules, or both), and the process may be repeated until the guest is successfully started with the cryptographic adapter or there are no other cryptographic adapters (or other security modules) included in the request.

[0035] Returning to inquiry 304, if the cryptographic adapter has not been reserved, e.g., by another guest, in one example, trusted firmware 160 resets the cryptographic adapter. Resetting the cryptographic adapter includes, e.g., in step 308, emptying a request-response queue (e.g., request-response queue 168) in a control block (e.g., HSM control block 164) of the cryptographic adapter maintained by trusted firmware 160. Emptying the request queue removes pending requests (e.g., all pending requests) to the adapter and their associated data, and pending responses (e.g., all pending responses) from the adapter and their associated data. In one example, emptying the queue is performed following determining that there is data to be emptied. In another example, the emptying or clearing operation is performed regardless of whether there is data to be cleared in the queue.

[0036] Additionally, the trusted firmware 160 reserves the cryptographic adapter for the secure guest, step 310. In one example, this involves placing an identifier of the secure guest in reservation information 169, for example in HSM control block 164 maintained by the trusted firmware, step 310. In other embodiments, different and / or other types of instructions in the same and / or different locations may be provided. The cryptographic adapter is then made accessible to the secure guest, step 312.

[0037] In another aspect, the reservation of a cryptographic adapter for a secure guest may be terminated, as further described with reference to Figure 4. In one example, a secure guest configured for a cryptographic adapter is terminated, step 400. Accordingly, trusted firmware 160 resets the cryptographic adapter, step 402, which may include, for example, emptying a request-response queue (e.g., request-response queue 168) in a control block maintained by trusted firmware 160, step 404.

[0038] Additionally, in one embodiment, trusted firmware 160 removes the reservation in the trusted firmware's control block (e.g., reservation information 169) maintained by the trusted firmware in step 406. In other embodiments, other and / or different instructions in the same and / or different locations may also be removed.

[0039] In another embodiment, the termination of the secure guest may occur even if the secure guest is not terminated. Other variations are possible.

[0040] One embodiment of sending a request from a guest to a cryptographic adapter is described with reference to Figure 5. Initially, in step 500, a guest (e.g., secure guest 180) sends a request to a cryptographic adapter (e.g., cryptographic adapter 152). The request may be a request to encrypt or decrypt data, a request to generate a key for a cryptographic operation, etc.

[0041] Upon issuing the request, in step 502, a trusted component (e.g., trusted firmware 160) intercepts the request and checks whether the cryptographic adapter is reserved, and if so, whether it is reserved by another guest. In one example, this check is a check of reservation information 169. If, in inquiry 504, the cryptographic adapter is reserved by another guest, the operation fails in step 506. However, if the cryptographic adapter is not reserved by another guest, in inquiry 508, a check is made as to whether the guest is not a secure guest, or, if the guest is a secure guest, whether the request is issued by a cryptographic adapter reserved by the secure guest. Again, in one example, reservation information 169 is checked to see whether the cryptographic adapter is reserved by a secure guest. Additionally, in one example, to see whether the guest is a secure guest, firmware (e.g., trusted firmware 160) checks a control block maintained for the guest that includes an indication of whether the guest is secure. If the guest is a secure guest and the cryptographic adapter is not reserved by the secure guest, the operation fails at step 510. Further, if the cryptographic adapter is not reserved by another guest at inquiry 504 and either the guest is not a secure guest or the guest is a secure guest and the cryptographic adapter is reserved by the secure guest at inquiry 508, the trusted firmware pushes the request to a request queue (e.g., request queue 168a) for the cryptographic adapter and, in one example, returns a return code to the secure guest at step 512 indicating success of the operation.

[0042] One embodiment of fetching a response from a cryptographic adapter is described with reference to FIG. 6. First, in step 600, a guest (e.g., secure guest 180) issues an operation to fetch a response from the cryptographic adapter. Based on the issuance of this operation, a trusted firmware (e.g., trusted firmware 160) intercepts the operation in step 602 and checks whether the cryptographic adapter is reserved, and if so, whether it is reserved by another guest. In one example, this check is a check of the reservation information 169. If, in query 604, the cryptographic adapter is reserved by another guest, the operation fails in step 606. However, if the cryptographic adapter is not reserved by another guest, then in query 608 a check is made as to whether the guest is not a secure guest, or, if the guest is a secure guest, whether a cryptographic adapter reserved by the secure guest is issuing the operation. Again, in one example, the check is a check of the reservation information 169 whether the cryptographic adapter is reserved by a secure guest. Further, in one example, to see if the guest is a secure guest, the firmware (e.g., trusted firmware 160) checks a control block maintained for the guest that includes an indication of whether the guest is secure. If the guest is a secure guest and the cryptographic adapter is not reserved by the secure guest, the operation fails at step 610. Further, if the cryptographic adapter is not reserved by another guest at inquiry 604 and either the guest is not a secure guest or the guest is a secure guest and the cryptographic adapter is reserved by the secure guest at inquiry 608, the trusted firmware pulls the response from the cryptographic adapter's response queue (e.g., response queue 168b) and returns it to the secure guest at step 612.

[0043] Described herein is the ability to reserve a security module, such as a hardware security module, and in particular a cryptographic adapter, for a particular guest. In one embodiment, a cryptographic adapter is reserved for exclusive use by a secure guest if the cryptographic adapter is in a list of accessible cryptographic adapters included in the metadata used to start the secure guest and has not been reserved by another secure guest. That metadata will be cryptographically linked to the boot image of the secure guest and transmitted over a secure channel to the trusted firmware.

[0044] The reservation is performed by the trusted firmware when the secure guest is initiated by indicating the reservation in a control block of the trusted firmware (e.g., HSM control block 164) that the system uses in communicating with the cryptographic adapter to queue requests to and responses from the cryptographic adapter. The reservation can be for the lifetime of the guest, and the reservation is protected from the hypervisor. The guest's I / O configuration, including the reservation, is protected from hypervisor misconfiguration, including an uncooperative hypervisor.

[0045] In one example, if reservation of a cryptographic adapter fails when a secure guest is started or the reservation is cancelled because the adapter is unplugged (and replugged), the system may provide, for example, every secure guest with the option to request the trusted firmware to reserve the adapter, in which case the trusted firmware checks whether the adapter is available, whether the secure guest may access the adapter according to the metadata of the secure guest, and whether there are any conflicting reservations of the adapter, and if so, reserves the adapter for the secure guest.

[0046] In one aspect, the trusted firmware maintains a control block (e.g., secure guest control block 162) that is inaccessible to the hypervisor, represents the guest for the lifetime of the secure guest, and contains data from the secure guest's metadata. The trusted firmware maintains reservation of the cryptographic adapter until the secure guest is terminated, so that the hypervisor cannot interfere with the reservation maintained by the trusted firmware for a running guest. The trusted firmware rejects any request from a secure guest that is not targeted to the cryptographic adapter reserved for that guest, and rejects any request from any guest to a cryptographic adapter reserved for another guest.

[0047] If the system detects that a cryptographic adapter has been removed, in one embodiment, the system revokes any reservation for that cryptographic adapter.

[0048] For each cryptographic adapter that the system has access to, the trusted firmware maintains a control block (e.g., control block 164) that, in one example, contains at least a queue of requests, including an indication of whether a queue entry has yet to be submitted to the cryptographic adapter, or a queue of responses from the cryptographic adapter. Each such control block also maintains an indication of whether the cryptographic adapter is reserved, and if so, by which guest it is reserved.

[0049] The cryptographic adapter's control blocks (and reservation instructions) cannot be directly accessed by the hypervisor or guest. In one example, they can only be accessed by firmware on behalf of the hypervisor or guest.

[0050] At system startup, in one embodiment, all cryptographic adapters are marked as unreserved.

[0051] In one or more aspects, the trusted firmware initiates the secure guest, and then in one embodiment, it secures cryptographic adapters that are defined in both the hypervisor guest configuration and the cryptographic adapter list in the metadata of the secure guest. The securing succeeds for all non-secured cryptographic adapters and fails for all reserved cryptographic adapters. The trusted firmware configures the secure guest such that the reserved cryptographic adapters are accessible to the guest in a hypervisor-passive mode, and attempts to access adapters that are not reserved for the secure guest fail. In one example, the hardware security module is configured for the secure guest in a hypervisor-passive mode such that cryptographic operations issued by the guest are not intercepted by the hypervisor (e.g., hypervisor 170). Instead, they are intercepted by a trusted component (e.g., trusted firmware 160) and bypass the hypervisor. This configuration is done in one example of the z / Architecture® hardware architecture by configuring, for example, a cryptographic control block of, for example, a start interpretative execution (SIE) instruction of the z / Architecture® hardware architecture.

[0052] In one or more aspects, firmware managing the cryptographic adapter's control block verifies the identity of the requesting guest when a request is to be pushed into a request queue of a reserved hardware security module and denies the operation if the identity does not match the identity of the guest owning the reservation. Firmware managing the cryptographic adapter's control block verifies the identity of the requesting guest when a response is to be pulled from a request queue of a reserved cryptographic adapter and denies the operation if the identity does not match the identity of the guest owning the reservation.

[0053] In one or more aspects, when the trusted firmware terminates a secure guest, for example, for all cryptographic adapters reserved for that secure guest, the trusted firmware instructs the cryptographic adapters to abort any pending requests and flushes the request-response queues of the cryptographic adapters.

[0054] In one or more aspects, if a secured cryptographic adapter functioning as a Hardware Security Module (HSM) is lost and reappears, the trusted firmware ensures that the cryptographic adapter does not service any pending requests, flushes the request-response queue of the cryptographic adapter, and deconfigures the HSM from the secure guest or places it in a state where each request to the adapter from the secure guest will result in an error.

[0055] In one or more aspects, the trusted firmware can provide an interface, accessible only by the secure guest, that the secure guest can use to request re-establishment of lost entitlements, and the hypervisor can fulfill the request to re-establish entitlements only for cryptographic adapters that are in both the secure guest's hypervisor configuration and the list of cryptographic adapters in the secure guest's metadata, for example.

[0056] In one embodiment, to ensure that the master key in the HSM is the master key belonging to the secure guest, the secure guest must verify the master key verification pattern before using the adapter for the first time or whenever security is re-established for a lost adapter.

[0057] Various aspects are described herein. Many variations and embodiments are possible without departing from the spirit of the aspects of the present invention. It should be noted that each aspect or feature described herein, and variations thereof, can be combined with any other aspect or feature, unless otherwise inconsistent.

[0058] One or more aspects of the present invention are integrally tied to computer technology and facilitate processing in a computer to improve its performance. Embodiments of the present invention are integrally tied to computing at least because they address problems unique to computing and are directed to providing technical approaches that are also in this field. An embodiment of the present invention reserves a security module, such as a cryptographic adapter, for a particular guest. Given that both the problems and approaches described above are specific to computing, an embodiment of the present invention is integrally tied to computing.

[0059] Other types of computing environments may incorporate and be used with one or more aspects of the present invention, including, but not limited to, emulation environments, one example of an emulation environment is described with reference to FIG. 7A. In this example, computing environment 35 includes, for example, a native central processing unit (CPU) 37, memory 39, and one or more input / output devices or interfaces 41, coupled with each other, for example, via one or more buses 43 or other connections or both. By way of example, computing environment 35 may include a PowerPC® processor offered by International Business Machines Corporation of Armonk, New York, or other machines based on architectures offered by International Business Machines Corporation, Intel Corporation, or other companies, or both. PowerPC is a trademark or registered trademark of International Business Machines Corporation in at least one jurisdiction. Intel is a trademark or registered trademark of Intel Corporation and its affiliates in the United States and other countries.

[0060] The native central processing unit 37 includes one or more native registers 45, such as one or more general purpose registers and / or one or more special purpose registers, that are used during processing within the environment. These registers contain information that represents the state of the environment at any particular time.

[0061] Additionally, the native central processing unit 37 executes instructions and code stored in memory 39. In one particular example, the central processing unit executes emulator code 47 stored in memory 39. This code enables a computing environment configured with one architecture to emulate another architecture. For example, the emulator code 47 enables a machine based on an architecture other than the z / Architecture® hardware architecture, such as a PowerPC® processor or other server or processor, to emulate the z / Architecture® hardware architecture and execute software and instructions developed based on the z / Architecture® hardware architecture.

[0062] Further details regarding the emulator code 47 are described with reference to FIG. 7B. The guest instructions 49 stored in memory 39 include software instructions (e.g., correlated to machine instructions) developed to execute in an architecture other than that of the native CPU 37. For example, the guest instructions 49 may be designed to execute on a z / Architecture® processor, but are instead emulated on the native CPU 37, which may be, for example, an Intel® processor. In one example, the emulator code 47 includes an instruction fetch routine 51 for retrieving one or more guest instructions 49 from the memory 39, and optionally providing local buffering of the retrieved instructions. It also includes an instruction conversion routine 53 for determining the type of the retrieved guest instruction and converting the guest instruction into one or more corresponding native instructions 55. This conversion may include, for example, identifying a function performed by the guest instruction and selecting a native instruction to perform the function.

[0063] Additionally, emulator code 47 includes an emulation control routine 57 that causes native instructions to be executed. Emulation control routine 57 may cause native CPU 37 to execute a routine of native instructions that emulates one or more previously fetched guest instructions and, upon completion of execution, returns control to an instruction fetch routine to emulate the fetch of the next guest instruction or group of guest instructions. Execution of native instructions 55 may include loading data from memory 39 into registers, storing data from registers back to memory, or performing any type of arithmetic or logical operation, depending on the determination of the translation routine.

[0064] Each routine may be implemented, for example, as software that is stored in memory and executed by native central processing unit 37. In other examples, one or more of the routines or operations are implemented as firmware, hardware, software, or any combination thereof. Registers of the emulated processor may be emulated using registers 45 of the native CPU or by using locations in memory 39. In embodiments, guest instructions 49, native instructions 55, and emulator code 47 may reside in the same memory or may be distributed among different memory devices.

[0065] One or more aspects may relate to cloud computing.

[0066] Although this disclosure includes detailed descriptions of cloud computing, it should be understood that implementation of the teachings described herein is not limited to a cloud computing environment. Rather, embodiments of the invention can be implemented in conjunction with any other type of computing environment now known or later developed.

[0067] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and made available with minimal administrative effort or interaction with service providers. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

[0068] The characteristics are as follows:

[0069] On-Demand Self-Service: Cloud consumers can unidirectionally provision computing capacity, such as server time or network storage, automatically, as needed, without the need for human interaction with the service provider.

[0070] Broad network access: Capabilities are available over the network and accessed through standard mechanisms that facilitate use by heterogeneous thin- or thick-client platforms (e.g., cell phones, laptops, and PDAs).

[0071] Resource Pooling: Provider computing resources are pooled to serve multiple consumers using a multi-tenant model, with various physical and virtual resources dynamically allocated and reallocated as needed. Consumers generally have no control or knowledge regarding the exact location of the resources provided, but there is a sense of location independence in that location can be specified at a high level of abstraction (e.g., country, state, or data center).

[0072] Rapid Elasticity: Capacity can be rapidly and elastically provisioned, in some cases automatically, to scale up quickly, release quickly, and scale down quickly. To the consumer, the capacity available to provision often appears infinite and can be purchased at any time and in any quantity.

[0073] Metered Services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported to provide transparency to both providers and consumers of the services utilized.

[0074] The service model is as follows:

[0075] Software as a Service (SaaS): The capability offered to the consumer is the ability to use a provider's applications running on a cloud infrastructure. The applications can be accessed from a variety of client devices through thin-client interfaces such as web browsers (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, storage, or even individual application capabilities except possibly limited user-specific application configuration settings.

[0076] Platform as a Service (PaaS): The ability offered to a consumer is the ability to deploy applications created or acquired by the consumer, written using programming languages ​​and tools supported by the provider, onto a cloud infrastructure. The consumer does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but does have control over the deployed applications and potentially the application host environment configuration.

[0077] Infrastructure as a Service (IaaS): The ability provided to the consumer is the ability to provision processing, storage, network, and other basic computing resources onto which the consumer can deploy and run any software, which may include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure, but has control over the operating systems, storage, deployed applications, and possibly limited control over selected networking components (e.g., host firewalls).

[0078] The deployment model is as follows:

[0079] Private Cloud: The cloud infrastructure is operated exclusively for one organization. It is managed by that organization or a third party and can be on-premise or off-premise.

[0080] Community Cloud: The cloud infrastructure is shared by several organizations to support a specific community with shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It is managed by those organizations or a third party and can reside on-premise or off-premise.

[0081] Public Cloud: The cloud infrastructure is made available to the general public or large industry groups and is owned by an organization that sells cloud services.

[0082] Hybrid Cloud: A cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technologies (e.g. cloud bursting for load balancing between clouds) that enable data and application portability.

[0083] A cloud computing environment is a set of services that emphasize statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure that includes a network of interconnected nodes.

[0084] Referring now to FIG. 8, an exemplary cloud computing environment 50 is depicted. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 52 with which local computing devices used by cloud consumers, such as personal digital assistants (PDAs) or cellular phones 54A, desktop computers 54B, laptop computers 54C, or automobile computer systems 54N, or combinations thereof, may communicate. The nodes 52 may communicate with each other. They may be physically or virtually grouped (not shown) as one or more networks, such as private, community, public, or hybrid clouds, or combinations thereof, as described herein above. This enables the cloud computing environment 50 to provide infrastructure, platform, and / or software as a service, for which the cloud consumers do not need to maintain resources on their local computing devices. It will be understood that the types of computing devices 54A-N shown in FIG. 8 are intended to be merely exemplary, and that the computing nodes 52 and cloud computing environment 50 can communicate with any type of computerized device through any type of network or network-addressable connection (e.g., using a web browser), or combination thereof.

[0085] Referring now to Figure 9, a set of functional abstraction layers provided by cloud computing environment 50 (Figure 8) is shown. It should be understood in advance that the components, layers, and functions shown in Figure 9 are intended to be merely exemplary, and embodiments of the present invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

[0086] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes 61, RISC (reduced instruction set computer) architecture based servers 62, servers 63, blade servers 64, storage devices 65, and networks and networking components 66. In some embodiments, the software components include network application server software 67 and database software 68.

[0087] The virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities are provided: virtual servers 71; virtual storage 72; virtual networks, including virtual private networks 73; virtual applications and operating systems 74; and virtual clients 75.

[0088] In one example, the management layer 80 may provide the following functions: Resource provisioning 81 provides dynamic procurement of computing and other resources utilized to perform tasks within the cloud computing environment. Metering and pricing 82 provides cost tracking as resources are utilized within the cloud computing environment and billing or invoicing for the consumption of those resources. In one example, the resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, and protection for data and other resources. User portal 83 provides consumers and system administrators with access to the cloud computing environment. Service level management 84 provides allocation and management of cloud computing resources such that required service levels are met. Service level agreement (SLA) planning and fulfillment 85 provides proactive configuration and procurement of cloud computing resources in anticipation of future needs in accordance with SLAs.

[0089] The workload tier 90 provides examples of functions for which cloud computing environments are utilized. Examples of workloads and functions provided from this tier include mapping and navigation 91, software development and lifecycle management 92, virtual classroom instructional delivery 93, data analytics processing 94, transaction processing 95, and assurance processing 96.

[0090] Aspects of the invention may be systems, methods, and / or computer program products at any possible level of integration of technical detail. The computer program product may include a computer-readable storage medium(s) having computer-readable program instructions for causing a processor to implement aspects of the invention.

[0091] A computer readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer readable storage medium may be, for example, but 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 above. A non-exhaustive list of more specific examples of computer readable storage media includes portable computer diskettes, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static random access memories (SRAM), portable compact disk read-only memories (CD-ROM), digital versatile disks (DVD), memory sticks, floppy disks, mechanically encoded devices such as punch cards or raised structures in grooves in which instructions are recorded, and any suitable combination of the above. The computer-readable storage medium as used in the present invention should not be construed as a transitory signal per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses through a fiber optic cable), or electrical signals transmitted over electrical wires.

[0092] The computer readable program instructions described herein may be downloaded from a computer readable storage medium to each computing / processing device or to an external computer or storage device via a network, such as the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof. The network may include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface within each computing / processing device receives the computer readable program instructions from the network and transfers the computer readable program instructions for storage within a computer readable storage medium within the respective computing / processing device.

[0093] The computer readable program instructions for carrying out the operations of the present invention may be either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, configuration data for an integrated circuit, or source or object code written in any combination of one or more programming languages, including object oriented programming languages ​​such as Smalltalk®, C++, and procedural programming languages ​​such as the “C” programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partially on the user's computer, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server, as a stand-alone software package. 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 wide area network (WAN), or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may execute computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry to perform aspects of the invention.

[0094] 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.

[0095] Those computer readable program instructions may be provided to a processor of a computer or other programmable data processing apparatus to produce a machine such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for performing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. Those computer readable program instructions may be stored in a computer readable storage medium capable of directing a computer, programmable data processing apparatus, or other device, or combination thereof, to function in a particular manner such that the computer readable storage medium on which the instructions are stored constitutes an article of manufacture including instructions implementing aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0096] The computer readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to produce a computer-implemented process, such that the instructions, which execute on the computer, other programmable apparatus, or other device, perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0097] The flowcharts 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 flowcharts or block diagrams may represent a module, segment, or part of an instruction, which includes one or more executable instructions for performing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may actually be realized as one step, may be executed simultaneously, may be executed substantially simultaneously, or may be executed with partial or complete overlap in time, or the blocks may sometimes be executed in reverse order depending on the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, are implemented by a special-purpose hardware-based system that performs the specified functions or acts or implements a combination of special-purpose hardware and computer instructions.

[0098] In addition to the above, one or more aspects may be provided, supplied, deployed, managed, serviced, etc., by a service provider that provides management of a customer environment. For example, a service provider may create, maintain, support, etc., computer code and / or computer infrastructure that performs one or more aspects for one or more customers. In return, the service provider may receive payments from the customer, for example under a subscription and / or fee agreement. Additionally or alternatively, the service provider may receive payments from the sale of advertising content to one or more third parties.

[0099] In one aspect, an application may be deployed to perform one or more embodiments. By way of example, deploying the application may include providing a computer infrastructure operable to perform one or more embodiments.

[0100] As a further aspect, a computing infrastructure is deployed that includes integrating computer readable code into a computing system, the code being capable of performing one or more embodiments in combination with the computing system.

[0101] As yet a further aspect, there may be provided a process for integrating a computing infrastructure comprising integrating computer readable code into a computer system, the computer system comprising a computer readable medium, the computer medium comprising one or more embodiments, the code in combination with the computer system capable of performing one or more embodiments.

[0102] Although various embodiments have been described above, they are merely examples. For example, one or more embodiments may be incorporated and used using computing environments of other architectures. Further, other trusted components and / or security modules may be used. Additionally, other control blocks and / or securing instructions may be used.

[0103] Additionally, other types of computing environments may be beneficially utilized. As an example, a data processing system suitable for storing and / or executing program code may be utilized that includes at least two processors coupled directly or indirectly through a system bus to memory elements. The memory elements may include, for example, local memory used during the actual execution of the program code, mass storage, and cache memory that provides temporary storage of at least some of the program code to reduce the number of times the code must be retrieved from mass storage during execution.

[0104] Input / output or I / O devices (including but not limited to keyboards, displays, pointing devices, DASD, tapes, CDs, DVDs, thumb drives and other memory media, etc.) may be coupled to the system either directly or through intermediary I / O controllers. Network adapters may also be coupled to the system to enable the data processing system to be coupled to other data processing systems or remote printers or storage devices through intermediary private or public networks. Modems, cable modems, and Ethernet® cards are just a few of the available types of network adapters.

[0105] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a," "an," and "the" are intended to encompass the plural unless the context clearly indicates otherwise. Furthermore, it will be understood that the terms "comprises" and / or "comprises" as used herein specify the presence of stated features, integers, steps, operations, elements, or components, or combinations thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof, or combinations thereof.

[0106] The corresponding structures, materials, acts, and equivalents (if any) of all means-plus-function or step-plus-function elements in the appended claims are intended to encompass any structure, material, or act for performing a function in combination with other claimed elements as specifically claimed. The description of one or more embodiments has been presented for purposes of illustration and description and is not intended to be exhaustive or limited to the disclosed forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments have been selected and described to best explain various aspects and practical applications and to enable those skilled in the art to understand the various embodiments with various modifications suitable for the particular use contemplated.

Claims

1. 1. A computer program product for facilitating processing within a computing environment, comprising: At least one computer-readable storage medium readable by at least one processing circuit and storing instructions for performing a method, said method comprising: reserving a security module for a secure guest of the computing environment, the reserving including reserving one or more queues used to communicate with the security module by binding them to the secure guest; managing the one or more queues based on one or more actions related to the reservation; the one or more actions include losing access to the security module, and the managing includes flushing the one or more queues; A computer program product that causes a computer to execute the above.

2. 2. The computer program product of claim 1, wherein the one or more actions include terminating the secure guest and the managing includes removing one or more pending requests from the one or more queues.

3. 2. The computer program product of claim 1, wherein the one or more queues include at least one request queue, the one or more actions include an operation of submitting a request to a request queue of the at least one request queue, and the managing includes verifying that the security module is reserved for the secure guest and allowing the operation based on verifying that the security module is reserved for the secure guest and that the request was issued by the secure guest.

4. 2. The computer program product of claim 1, wherein the one or more queues include at least one response queue, the one or more actions include an operation of fetching a response from a response queue of the at least one response queue, and the managing includes verifying that the security module is reserved for the secure guest and allowing the operation based on verifying that the security module is reserved for the secure guest and that the fetch operation was issued by the secure guest.

5. 2. The computer program product of claim 1, the method further comprising removing pending requests to the security module based on flushing the one or more queues.

6. 10. The computer program product of claim 1, the method further comprising deleting the reservation based on losing access to the security module.

7. 2. The computer program product of claim 1, wherein the method further comprises refusing to send a request from the secure guest to a queue not reserved for the secure guest.

8. 2. The computer program product of claim 1, wherein the method further comprises refusing to pass a response to the secure guest that was fetched from a queue not reserved for the secure guest.

9. 10. The computer program product of claim 1, wherein the method further comprises returning an error code to a guest based on a guest attempting to access a queue that is not reserved for the guest.

10. 2. The computer program product of claim 1, wherein the method further includes determining whether the security module is in a list of accessible security modules included in metadata used to initiate the secure guest, and wherein a process of reserving the security module continues based on determining that the security module is in the list of accessible security modules included in the metadata.

11. 11. The computer program product of claim 10, wherein the metadata is transmitted over a secure channel to a trusted component for exclusive use by the secure guest, the trusted component making the reservation.

12. 2. The computer program product of claim 1, wherein said binding comprises including an indication of said reservation within a control block of a trusted component used in making said reservation.

13. 1. A computer system for facilitating processing within a computing environment, comprising: Memory, a processor in communication with the memory, the computer system being configured to perform a method, the method comprising: reserving a security module for a secure guest of the computing environment, the reserving including reserving one or more queues used to communicate with the security module by binding them to the secure guest; managing the one or more queues based on one or more actions related to the reservation; the one or more actions include losing access to the security module, and the managing includes flushing the one or more queues; 1. A computer system comprising:

14. 14. The computer system of claim 13, wherein the one or more actions include terminating the secure guest and the managing includes removing one or more pending requests from the one or more queues.

15. 14. The computer system of claim 13, wherein the method further includes determining whether the security module is in a list of accessible security modules included in metadata used to initiate the secure guest, and wherein the process of reserving the security module continues based on determining that the security module is in the list of accessible security modules included in the metadata.

16. 14. The computer system of claim 13, wherein the method further comprises returning an error code to a guest based on the guest attempting to access a queue that is not reserved for the guest.

17. 1. A computer-implemented method for facilitating processing in a computing environment, comprising: reserving a security module for a secure guest of the computing environment, the reserving including reserving one or more queues used to communicate with the security module by binding them to the secure guest; managing the one or more queues based on one or more actions related to the reservation; the one or more actions include losing access to the security module, and the managing includes flushing the one or more queues; A computer-implemented method comprising:

18. 20. The computer-implemented method of claim 17, wherein the one or more actions include terminating the secure guest and the managing includes removing one or more pending requests from the one or more queues.

19. 20. The computer-implemented method of claim 17, further comprising determining whether the security module is in a list of accessible security modules included in metadata used to initiate the secure guest, and wherein a process of reserving the security module continues based on determining that the security module is in the list of accessible security modules included in the metadata.

Citation Information

Patent Citations

  • Communication system between virtual machines

    JP2018133758A

  • Hardware security module access management in a cloud computing environment

    US20160092243A1

  • Content based hardware security module assignment to virtual machines

    US20160239667A1

  • Virtual trusted platform module function implementation method and management device

    US20170075717A1

  • Secure userspace networking for guests

    US20190391927A1