Generating hybrid security certificates using multiple cryptosystems

Abstract

A method and apparatus for facilitating processing within a computing environment by generating a hybrid security certificate using multiple cryptosystems, the generating including obtaining data for inclusion in the hybrid security certificate, generating a first digital signature associated with a first cryptosystem covering the data, and generating a second digital signature associated with a second cryptosystem covering the data, the generating further including providing a hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, the first digital signature independent of a key of the second cryptosystem or the second digital signature, and the second digital signature independent of a key of the first cryptosystem or the first digital signature.

Description

[Technical Field]

[0001] One or more aspects relate generally to facilitating processing within a computing environment, and more particularly to facilitating secure communications within a computing environment. Cryptographic systems may be used in various computing environments to facilitate secure communications between entities of the environment. [Background technology]

[0002] A computing environment may include different types of processors to enhance processing. As an example, a computing environment may include one or more central processing units (CPUs), which are considered main processors, and one or more auxiliary processors, which are considered associated with the CPUs. An auxiliary processor typically performs a specific type of task. For example, a particular example of an auxiliary processor is a crypto card used to perform cryptographic operations. Summary of the Invention

[0003] Certain shortcomings of the prior art are overcome, and further advantages are provided, in one or more aspects through the provision of a computer program product for facilitating processing within a computing environment. The computer program product includes one or more computer-readable storage media and program instructions collectively stored on the one or more computer-readable storage media for performing a method. The method includes generating a hybrid security certificate using multiple cryptosystems. The generating includes obtaining data to be included in the hybrid security certificate, generating a first digital signature associated with a first cryptosystem of the multiple cryptosystems covering the data, and generating a second digital signature associated with a second cryptosystem of the multiple cryptosystems covering the data. Generating the hybrid security certificate includes providing a hybrid security certificate, the security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, wherein the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature. Advantageously, the inclusion of a first digital signature and a second digital signature in a hybrid security certificate can provide a more flexible and robust security certificate. Furthermore, the multiple cryptosystems used to generate the hybrid security certificate can include any available first and second cryptosystems. Furthermore, generating a hybrid security certificate using multiple cryptosystems as disclosed herein advantageously facilitates cryptographic security migration from one cryptosystem standard to another. In accordance with one or more aspects, there is no dependency between the first and second digital signatures of a hybrid security certificate.

[0004] In one or more embodiments, generating a first digital signature associated with a first cryptosystem covers data independent of a second cryptosystem, and generating a second digital signature associated with a second cryptosystem covers data independent of the first cryptosystem, where the data does not include or depend on attributes or keys of the first cryptosystem or the second cryptosystem. Advantageously, with the hybrid security certificate generation disclosed herein, signatures do not need to be updated or modified if attributes of a matching signature change. Furthermore, because each signature over data is independent of the others, each signature is easier to code and analyze.

[0005] In one embodiment, the first cryptosystem includes an asymmetric cryptosystem and the second cryptosystem includes a quantum-resistant cryptosystem. In one embodiment, the quantum-resistant cryptosystem includes a lattice-based cryptography approach. As an example, the first cryptosystem is an Elliptic Curve Cryptography (ECC) cryptosystem and the second cryptosystem is a Dilithium cryptosystem. Advantageously, the hybrid security credential generation disclosed herein can include a first cryptosystem that is a certified security system, such as a certified asymmetric cryptosystem, and a second cryptosystem that is a non-certified, but more quantum-resistant, security system. For example, in one implementation, the first cryptosystem can be a National Institute of Standards and Technology (NIST)-certified security system and the second cryptosystem can be, for example, a non-certified quantum-resistant cryptosystem.

[0006] In one or more embodiments, generating a hybrid security certificate includes associating a first public key with the data, the first public key being associated with a first cryptosystem, and generating a first digital signature using a first private key in generating a first digital signature associated with the first cryptosystem covering the data, the generating the first digital signature using a property of the first public key. In one or more further embodiments, generating a hybrid security certificate includes associating a second public key with the data, the second public key being associated with a second cryptosystem. Furthermore, generating a second digital signature uses a second private key to generate a second digital signature associated with the second cryptosystem covering the data, the generating the second digital signature using a property of the second public key. Advantageously, generation of the first digital signature is independent of attributes of the second public key, the second digital signature, or the second cryptosystem, and generation of the second digital signature is independent of attributes of the first public key, the first digital signature, or the first cryptosystem, and the first digital signature and the second digital signature each independently cover data.

[0007] In one or more embodiments, generating a hybrid security certificate further includes generating a third digital signature associated with a third cryptosystem that covers the data, and providing a hybrid security certificate includes providing a hybrid security certificate having the data, a first digital signature associated with the first cryptosystem, a second digital signature associated with the second cryptosystem, and a third digital signature associated with the third cryptosystem, where no dependency exists between the first digital signature, the second digital signature, and the third digital signature. Advantageously, the hybrid security certificate generation disclosed herein is scalable to accommodate any number N of signature types or cryptosystems (where N≧2), e.g., three or more independent signatures, to be utilized in a certificate to cover the data, without dependency between the signatures. In this manner, a more robust hybrid security certificate is provided.

[0008] In one embodiment, providing the hybrid security certificate further includes packaging the data, the first digital signature, and the second digital signature in a single Distinguished Encoding Rules (DER) sequence.

[0009] Additionally, in one or more implementations, the hybrid security certificate includes a SignerInfo block that includes a first public key associated with the first cryptosystem, a first digital signature, and a second public key associated with the second cryptosystem and the second digital signature.

[0010] Computer systems and computer-implemented methods 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.

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

[0012] One or more aspects of the present invention are particularly pointed out and distinctly claimed by way of example in the claims at the conclusion of the specification. The above and other objects, features, and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0013] [Figure 1A] 1 illustrates one embodiment of a computing environment for incorporating and using one or more aspects of the present invention. [Figure 1B] 1 illustrates another embodiment of a computing environment for incorporating and using one or more aspects of the present invention. [Figure 2] 1 illustrates one embodiment of a process flow within a computing environment with secure communications in accordance with one or more aspects of the present invention. [Figure 3] 1 is a block diagram illustrating an exemplary hybrid security certificate in accordance with one or more embodiments of the present invention. [Figure 4] FIG. 2 is a block diagram illustrating a more detailed example of a hybrid security certificate, in accordance with one or more embodiments of the present invention. [Figure 5A] 1 illustrates one embodiment of aspects related to facilitating processing within a computing environment in accordance with one or more aspects of the present invention. [Figure 5B] 1 illustrates one embodiment of aspects related to facilitating processing within a computing environment in accordance with one or more aspects of the present invention. [Figure 6A] 1 illustrates an example computing environment for incorporating and using one or more aspects of the present invention. [Figure 6B] 1 illustrates another example of a computing environment for incorporating and using one or more aspects of the present invention. [Figure 6C]6C illustrates an example of further details of the memory of FIG. 6B, in accordance with one or more embodiments of the present invention. [Figure 6D] 6C illustrates another example of further details of the memory of FIG. 6B, in accordance with one or more embodiments of the present invention. [Figure 7A] 1 illustrates another example of a computing environment for incorporating and using one or more aspects of the present invention. [Figure 7B] 7B illustrates further details of the memory of FIG. 7A in accordance with one or more embodiments of the present invention. [Figure 8] 1 illustrates an embodiment of a cloud computing environment in accordance with one or more aspects of the present invention. [Figure 9] FIG. 2 illustrates an example of an abstraction model layer, in accordance with one or more aspects of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] The accompanying drawings, in which like reference numerals refer to identical or functionally similar elements throughout the different views, and which are incorporated in and constitute a part of this specification, further illustrate the present invention and, together with the detailed description of the present invention, serve to explain aspects of the present invention. In this regard, it should be noted that descriptions of well-known systems, devices, cryptographic systems, processing techniques, and the like are omitted so as not to unnecessarily obscure the details of the present invention. However, it should be understood that the detailed description and the specific examples, while illustrating aspects of the present invention, are intended for purposes of illustration only and not limitation. Various substitutions, modifications, additions, or other arrangements, or combinations thereof, within the spirit or scope of the underlying inventive concept will become apparent to those skilled in the art from this disclosure. Furthermore, it should be noted that numerous inventive aspects and features are disclosed herein and, unless inconsistent, each disclosed aspect or feature can be combined with any other disclosed aspect or feature as desired for a particular application of the concepts disclosed herein.

[0015] Also, while exemplary embodiments are described below using specific code, designs, architectures, cryptographic systems, protocols, layouts, circuit diagrams, or tools, it should be noted that this is by way of example only and not by way of limitation. Furthermore, exemplary embodiments are described in specific instances using specific software, tools, or data processing environments, and by way of example only for clarity of explanation. The exemplary embodiments may be used in combination with other comparable or similar purpose structures, systems, applications, or architectures. One or more aspects of the exemplary embodiments may be implemented in hardware, software, or a combination thereof.

[0016] As will be appreciated by those skilled in the art, program code referred to herein can include both software and hardware. For example, the program code in certain embodiments of the present invention may include fixed-function hardware, while other embodiments may utilize software-based implementations of the described functionality. Certain embodiments combine both types of program code. An example of program code, also referred to as one or more programs or program instructions, is depicted in FIG. 6A as one or more of an application program 616, computer-readable program instructions 620, or cryptographic system 622, or a combination thereof, stored in memory 606 of computer system 602, and a program 636 and computer-readable program instructions 638 stored in data storage device 634 accessed by computer system 602.

[0017] As mentioned above, encryption systems can be used in various computing environments to facilitate secure communications. In one or more embodiments, an encryption system (or cryptosystem) provides security credentials, or digital certificates, to facilitate secure communications, such as within or between computing systems.

[0018] In particular, cryptography is an essential tool for secure processing. Cryptography is commonly used when an application must communicate with other distributed elements or when the validity of data being processed must be asserted or verified. As previously mentioned, in one or more embodiments, a computing environment may include different types of processors to enhance processing. As an example, a computing environment may include one or more central processing units (CPUs), which are considered main processors, and one or more auxiliary processors, which are considered associated with the CPUs. An auxiliary processor typically performs a specific type of task. For example, a specific type of auxiliary processor is a crypto card used to perform cryptographic processing.

[0019] One example of a cryptographic card offered by International Business Machines Corporation (Armonk, New York, USA) is the IBM® 4769 PCIe Cryptographic Coprocessor, a hardware security module (HSM) containing a secure coprocessor mounted on a high-security, tamper-resistant, programmable Peripheral Component Interconnect Express (PCIe) board. (IBM is a registered trademark of International Business Machines Corporation in at least one jurisdiction.) Specialized cryptographic electronics, a microprocessor, memory, and a random number generator are housed within a tamper-resistant environment to provide a highly secure subsystem capable of performing data processing and encryption. Sensitive keys are never exposed in clear format outside of a physically secure boundary.

[0020] The IBM 4769 PCIe Cryptographic Coprocessor is designed to meet Federal Information Processing Standard (FIPS) 140-2 Level 4, the highest level of certification available for commercially available cryptographic devices. This cryptographic card can be used as part of a wide range of encryption and enterprise security systems.

[0021] For example, an example of a cryptographic card application offered by International Business Machines Corporation of Armonk, New York, USA, is the channel-attached Crypto Express™ card (Crypto Express is a trademark of International Business Machines Corporation in at least one jurisdiction). The Crypto Express card is defined to support multiple types of commands, such as commands using encryption keys, commands using clear keys, hash commands, query commands, and random number generator commands. Additionally, the Crypto Express card is designed to support multiple modes, such as Common Cryptographic Architecture (CCA) mode, accelerator mode, and Enterprise Public Key Cryptography Standard (PKCS) (also known as XCP / EP11 - Enterprise PKCS #11 mode). Each mode can be configured to process a specific type of command. By way of example, applications can include financial PIN transactions, bank-to-clearing house transactions, credit transactions for integrated circuit (chip)-based credit cards, and general-purpose cryptographic applications using symmetric key algorithms, hash algorithms, public key algorithms, and the like. In one or more implementations, an operational key (a symmetric or asymmetric private key (RSA or elliptic curve)) is generated on the coprocessor and then stored encrypted under that coprocessor's master key, for example in a keystore file or in application memory. Any coprocessor with the same matching key can use that key. In one or more implementations, a cryptosystem and / or card as described herein can be supported on certain mainframe computing environments, such as the IBM z / Architecture® computing environment (where z / Architecture® is a registered trademark of International Business Machines Corporation in at least one jurisdiction).

[0022] A certificate (referred to herein as a security certificate or digital certificate) is an electronic document or data file used to prove the ownership and authenticity of a cryptographic key. Certificates in current use typically incorporate a single cryptosystem; that is, a certificate contains one key and one signature, both generated using the same cryptosystem. In practice, the cryptosystem is typically an asymmetric cryptosystem, such as Elliptic Curve Cryptography (ECC).

[0023] Currently used asymmetric cryptosystems are vulnerable to attacks by algorithms running on quantum computers. Therefore, there is a desire to move to cryptosystems that are more resistant to attacks from both classical and quantum computers. Dilithium cryptography is one of several lattice-based cryptographic approaches that can maintain its robustness even in the presence of quantum computers, and is one candidate for such a cryptosystem.

[0024] Dilithium keys and signatures are much larger than currently used ECC keys and signatures. For example, an ECC public key is approximately 160 bytes, an ECC signature is just over 200 bytes, and an ECC private key is approximately 250 bytes (although the private key can be reconstructed almost instantly from 72 bytes of secret data). In comparison, the corresponding values ​​for Dilithium-strength keys are approximately 2400 bytes, just under 4700 bytes, and over 7500 bytes, respectively. Furthermore, a Dilithium private key can be reconstructed from approximately 64 bytes of secret data.

[0025] Currently, standardization and certification organizations (such as the National Institute of Standards and Technology (NIST)) have not yet reached a standard quantum-safe cryptosystem and will not certify implementations that rely solely on such cryptosystems for security. As a solution, a hybrid security certification approach, such as that disclosed herein, can be adopted.

[0026] As described herein, in one or more implementations, program code executing on one or more processors generates a hybrid security credential including two keys and two signatures, one set generated using a first cryptosystem and the other set generated using a second cryptosystem. For example, in only one implementation, the first cryptosystem is a NIST-certified asymmetric cryptosystem, and the other cryptosystem is a quantum-resistant cryptosystem that has not yet been certified by NIST. In this manner, the hybrid security credential generation functionality provides broad support for non-disruptive upward migration between different cryptosystem standards. The hybrid security credential generation functionality disclosed herein can be adapted to accommodate future changes in cryptosystem standards, such as changes in key and / or signature lengths. For example, in one implementation, to achieve certification, a cryptographic adapter / card such as the one described above may continue to use a certified cryptosystem approach, such as an ECC cryptosystem, and may also include a more quantum-resistant cryptosystem approach that has not yet been certified. Thus, in one or more embodiments, to maintain NIST compliance, the hybrid security certificate generation functionality disclosed herein utilizes multiple cryptosystems to provide a hybrid security certificate that includes multiple keys and multiple digital signatures, where the key and signature pairs are independent of each other.

[0027]

[0006] Embodiments of the present invention include computer program products, computer systems, and methods, where program code executing on one or more processors (e.g., one or more coprocessors or auxiliary processors) generates a hybrid security certificate using multiple cryptosystems. The generating includes obtaining data to be included in the hybrid security certificate, generating a first digital signature associated with a first cryptosystem of the multiple cryptosystems covering the data, and generating a second digital signature associated with a second cryptosystem of the multiple cryptosystems covering the data. Generating the hybrid security certificate further includes providing a hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, where the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature.

[0028] In one or more embodiments, program code executing on one or more processors generates a first digital signature associated with a first cryptosystem to cover data independent of a second cryptosystem, and generates a second digital signature associated with the second cryptosystem to cover data independent of the first cryptosystem, the data not including or dependent on any attributes or keys of the first cryptosystem or the second cryptosystem. In one embodiment, the data includes metadata to be secured, and the generation of the certificate can be associated with (for example) a miniboot process or an authentication process (such as an outbound authentication manager process), or both. Furthermore, in one embodiment, the first cryptosystem is an asymmetric cryptosystem and the second cryptosystem is a quantum-safe cryptosystem, such as a lattice-based cryptosystem. In one particular embodiment, the first cryptosystem is an elliptic curve cryptography (ECC) cryptosystem and the second cryptosystem is a Dilithium cryptosystem.

[0029] In one or more implementations, generating the hybrid security certificate further includes program code executing on one or more processors, associating a first public key with the data, the first public key being associated with a first cryptosystem, and generating the first digital signature using a first private key in generating a first digital signature associated with the first cryptosystem covering the data. Generating the first digital signature further uses a property of the first public key. In one or more further embodiments, program code executing on the one or more processors generates the hybrid security certificate by associating a second public key with the data, the second public key being associated with a second cryptosystem, and generating the second digital signature using a second private key to generate a second digital signature associated with the second cryptosystem covering the data. Also, generating the second digital signature uses a property of the second public key.

[0030] In one or more embodiments, program code executing on one or more processors generates a hybrid security certificate by generating a third digital signature associated with a third cryptosystem covering data, wherein providing the hybrid security certificate includes providing a hybrid security certificate having the data, a first digital signature associated with the first cryptosystem, a second digital signature associated with the second cryptosystem, and a third digital signature associated with the third cryptosystem, wherein there is no dependency or overlap among the first digital signature, the second digital signature, and the third digital signature.

[0031] In one or more embodiments, generating the hybrid security certificate further includes packaging the data, the first digital signature, and the second digital signature in a single Distinguished Encoding Rules (DER) sequence. Additionally, in one embodiment, the generated hybrid security certificate includes a SignerInfo block that includes a first public key associated with the first cryptosystem, the first digital signature, and a second public key associated with the second cryptosystem and the second digital signature.

[0032]

[0006] Embodiments of the present invention are inextricably linked to computing and offer significantly more than existing approaches to security credentials. For example, embodiments of the present invention provide program code executing on one or more processors that utilizes computing-centric data processing techniques to generate a hybrid security certificate using multiple cryptosystems. Advantageously, the program code executing on one or more processors provides a hybrid security certificate, the hybrid certificate including data protected by the certificate, a first digital signature associated with a first cryptosystem, and a second digital signature associated with a second cryptosystem, wherein the first digital signature is independent of attributes or keys of the second cryptosystem or the second digital signature, and the second digital signature is independent of attributes or keys of the first cryptosystem or the first digital signature.

[0033] Both the interconnectivity of the computing elements, systems, or nodes utilized and the computer-exclusive data processing techniques utilized by the program code enable various aspects of the present invention. Furthermore, embodiments of the present invention significantly exceed existing approaches to generating security certificates by providing a hybrid security certificate in which signature sections or subsections do not need to be updated or modified when attributes of a matching signature section or subsection change. Furthermore, each signature in a hybrid certificate is easier to code and easier to parse because each signature covering data is independent of the others. Furthermore, each certificate field or subsection is not required to be zeroed or have a specific value before a given signature in a hybrid security certificate is determined. Furthermore, the hybrid security certificate generation functionality disclosed herein is extensible to any number N of signature formats or cryptosystems, such as three or more independent signatures utilized to cover the data to be protected.

[0034] Advantageously, the inclusion of the first digital signature and the second digital signature provides a more robust security credential, particularly in the presence of quantum computers. In one or more implementations, the first cryptosystem may be a NIST-certified security system, and the second cryptosystem may be, for example, a quantum-safe cryptosystem that has not yet been certified.

[0035] By way of example only, one embodiment of a computing environment incorporating and using one or more aspects of the present invention is described with reference to FIG. 1A. By way of example, computing environment 100 includes at least one central processing unit 102 and at least one auxiliary processor (AP) 104, each of which is coupled to at least a portion of memory referred to as system memory 106. By way of example, system memory 106 includes hardware system areas that are indirectly accessible and invisible to programs executing on the central processing unit. (Indirectly accessible is used herein to mean that the hardware system areas, or auxiliary processor queues (described below) stored therein, are accessible only by certain limited instructions and are not otherwise accessible (e.g., cannot be loaded into, programs do not know the addresses, etc.).) Located within the system memory are one or more auxiliary processor queues 108. These queues are not directly visible to user programs, but instead are considered part of the machine (i.e., the machine including the central processing unit, system memory, and auxiliary processors). The central processing unit may access the queues in system memory, for example, by issuing instructions to queue requests and / or remove replies from the queues, but the auxiliary processors may access the queues directly, for example, via the transport layer 110, and are responsible for dequeuing requests, processing requests, and placing replies to requests in the queues.

[0036] Another embodiment of a computing environment incorporating and using one or more aspects of the present invention is described with reference to FIG. 1B. In this embodiment, the machine includes virtualization support, and there is at least one host central processing unit 150 that includes multiple guests 152 (e.g., guest operating systems and / or guest programs). The host central processing unit is coupled to at least a portion of memory referred to as system memory 154. Additionally, there is at least one coprocessor 156, which is also coupled to system memory 154, e.g., via transport layer 160. By way of example, system memory 154 includes a hardware system area, and located within the system memory are one or more coprocessor queues 158.

[0037] As shown, there are various types of auxiliary processors, including, but not limited to, cryptographic cards and adapters. An example of a cryptographic card is the Crypto Express card offered by International Business Machines Corporation of Armonk, New York. While an example of a cryptographic card is provided, other cryptographic cards offered by International Business Machines Corporation and / or other companies may incorporate and / or use one or more aspects of the present invention. Additionally, other types of processors may incorporate and / or use one or more aspects of the present invention.

[0038] In one embodiment, an auxiliary processor such as a cryptographic card (e.g., a Crypto Express card) can support multiple modes, including, by way of example and not limitation, a coprocessor mode, an accelerator mode, and an Enterprise Public Key Cryptography Standard (PKCS) mode (e.g., XCP / EP11-Enterprise PKCS#11). In other examples, additional, fewer, or other modes, or combinations thereof, may be supported. Each mode may have its own AP message structure and format.

[0039] As an example, an auxiliary processor message may consist of multiple data segments, which may not be adjacent to each other but may instead be interleaved. These data segments are referred to as scatter-gather data segments. As an example, a cryptographic card may not have direct access to an enqueued AP message; a portion of the message (e.g., the bottom portion of the AP message) contains data that the cryptographic card uses to execute the AP command. Therefore, the AP command transport layer (e.g., transport layer 110, 160) copies the relevant data from the AP command request message, packages it into a format the cryptographic card can understand (e.g., a cryptographic card command request message), and sends it to the cryptographic card. Similarly, after the AP command is executed by the cryptographic card, the AP command transport layer uses various portions of the AP command request message and the cryptographic card command reply message to generate an AP command reply message and send it to the AP queue to be later dequeued by a program.

[0040] Aspects of the hybrid security certificate functionality are described herein with respect to a particular architecture, such as the z / Architecture® hardware architecture offered 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-12, 13th Edition, September 2019, which is incorporated herein by reference in its entirety. However, the z / Architecture The hardware architecture is just one exemplary architecture. Aspects of the invention may also be based on other architectures, including, but not limited to, the Intel x86 architecture, other architectures from International Business Machines Corporation, or architectures from other companies, or combinations thereof.

[0041] By way of example, Figure 2 illustrates one embodiment of a computing environment 200 in which command request / response messages (i.e., data) can use cryptographic adapter / card processing to obtain hybrid security credentials as described herein. In the Figure 2 embodiment, the cryptographic processor can be an auxiliary processor as described above in connection with the Figures 1A and 1B embodiment. Referring to Figure 2, in one embodiment, a cryptographic request 210 is made by a requestor such as a guest 202 (e.g., a guest application or guest operating system in a cloud environment, at step 210). In one example, an AP command request message can be encoded and provided to a hypervisor 204.

[0042] In step 220, the cryptographic request is obtained (e.g., received, obtained, provided, etc.) from guest 202 by hypervisor 204 and processed for forwarding. This processing may include, for example, consideration of the allowable command types to be processed for the requestor based on the requestor's computing policy. Hypervisor 204 provides a request message 210 to an auxiliary processor (e.g., cryptographic processor 208). For example, hypervisor 204 sends or forwards the request message to the auxiliary processor, for example, via system bus 206, or the auxiliary processor obtains (e.g., retrieves) the request message via system bus 206.

[0043] An auxiliary processor, such as crypto processor 208 (in this example), processes the request at step 230. Assuming the request is authorized, it is processed (e.g., the command's operation is performed) and a crypto processor reply 240 is generated at step 240, which in one embodiment may include placing the reply in an AP command reply message and sending it, for example, via a transport layer (e.g., transport layer) to guest 202 at step 250. The reply may include the results of the processing, such as a generated hybrid security certificate as described herein.

[0044] FIG. 3 depicts one embodiment of a hybrid security certificate 300 format in accordance with one or more aspects of the present invention. As described herein, the depicted certificate broadly supports non-disruptive upward migration between different cryptographic standards, i.e., different cryptosystem approaches. Thus, as future cryptographic standards, including key lengths and signatures, change, the disclosed hybrid certificate format can be used to facilitate migration from one cryptographic standard to another. In the depicted embodiment, hybrid security certificate 300 includes multiple sections or subsections, including a data section 310, a first cryptosystem public key and digital signature section 320, and a second cryptosystem public key and digital signature section 330. Note that the two cryptosystem public key and digital signature sections are provided for illustrative purposes only. As described herein, generating hybrid security certificates can be easily extended to use more than two cryptosystems, in which case each cryptosystem would have its own section or subsection within the hybrid security certificate format depicted in FIG. 3.

[0045] As shown in FIG. 3 , data section 310 is the certificate body and may contain messages / data (e.g., metadata) to be processed and / or secured. First cryptosystem public key and digital signature 320 covers only data 310 and is completely independent of any fields or data in second cryptosystem public key and digital signature 330, and second cryptosystem public key and digital signature 330 covers data 310 and is independent of any fields or data in first cryptosystem public key and digital signature 320. In this way, no signature or key section of the certificate needs to be updated if attributes of the matching signature or key section change. Furthermore, as previously mentioned, the hybrid security certificate generation functionality disclosed herein is extensible to any N signature formats, where N is two or more signatures over the certificate body data to be secured.

[0046] As shown, in one implementation, a Distinguished Encoding Rules (DER) sequence 301 may be used to encapsulate or encode the entire hybrid security certificate. Alternatively, in one or more other implementations, each section 310, 320, 330 may be encapsulated in its respective DER sequence. In one embodiment, the first cryptosystem public key and digital signature section 320 and the second cryptosystem public key and digital signature section 330 may be grouped as a SignerInfo block associated with the data section 310, as shown. In such an embodiment, the SignerInfo blocks may be encapsulated in their respective DER sequences.

[0047] Figure 4 illustrates a more detailed representation of a hybrid digital certificate in accordance with one or more aspects of the present invention. In the embodiment of Figure 4, hybrid digital certificate 400 includes data for inclusion in certificate 410. For example, in one embodiment, the data to be protected includes metadata such as version number 411, serial number 412, and / or a message or other data. Data 410 is covered or protected by a first cryptosystem public key and digital signature 420 and a second cryptosystem public key and digital signature 430, where the first and second cryptosystem information are completely independent of each other and there is no overlap in keys, signatures, or other attributes between the first and second cryptosystem information.

[0048] As shown, in one embodiment, first cryptosystem public key and digital signature 420 may include first signature algorithm ID 421, first public key information 422, and first certificate signature algorithm 423, and that information, as well as data 410, is digitally signed or secured by first digital signature 424 associated with (e.g., provided in accordance with) the first cryptosystem.

[0049] Similarly, second cryptosystem public key and digital signature 430 may include, for example, second signature algorithm ID 431, second public key information 432, and second certificate signature algorithm 433, which, along with data 410, are digitally signed or secured by second digital signature 434 associated with (e.g., provided in accordance with) the second cryptosystem. In this manner, the first and second cryptosystem public keys and digital signatures are completely independent of each other, yet both still protect the data within the hybrid digital certificate.

[0050] Details of one embodiment of aspects relating to facilitating processing within a computing environment are summarized below with reference to FIGS. 5A-5B.

[0051] 5A , in one embodiment, a processor, such as an auxiliary processor, generates a hybrid security certificate using multiple cryptosystems (500). Generating the hybrid security certificate includes obtaining data for inclusion in the hybrid security certificate (502), generating a first digital signature associated with a first cryptosystem of the multiple cryptosystems covering the data (504), and generating a second digital signature associated with a second cryptosystem of the multiple cryptosystems covering the data (506). Further, generating the hybrid security certificate includes providing a hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, wherein the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature (508).

[0052] In one embodiment, generating a first digital signature associated with a first cryptosystem covers data independent of a second cryptosystem, and generating a second digital signature associated with a second cryptosystem covers data independent of the first cryptosystem, the data not including or dependent on attributes or keys of the first cryptosystem or the second cryptosystem (510).

[0053] In one or more embodiments, the first cryptosystem includes an asymmetric cryptosystem and the second cryptosystem includes a quantum-safe cryptosystem (512). In one embodiment, the quantum-safe cryptosystem includes a lattice-based cryptography approach. For example, in one or more embodiments, the first cryptosystem includes an elliptic curve cryptography (ECC) cryptosystem and the second cryptosystem includes a Dilithium cryptosystem (516).

[0054] Referring to FIG. 5B, in one embodiment, generating the hybrid security certificate further includes associating a first public key with the data, the first public key being associated with a first cryptosystem, and generating the first digital signature using a first private key in generating the first digital signature associated with the first cryptosystem that covers the data, and generating the first digital signature using properties of the first public key (518).

[0055] In one embodiment, generating the hybrid security certificate further includes associating a second public key with the data, the second public key being associated with a second cryptosystem, and generating the second digital signature using a second private key to generate a second digital signature associated with the second cryptosystem that covers the data, and generating the second digital signature using properties of the second public key (520).

[0056] In one or more embodiments, generating the hybrid security certificate further includes generating a third digital signature associated with a third cryptosystem covering the data, and providing the hybrid security certificate includes providing a hybrid security certificate having the data, the first digital signature associated with the first cryptosystem, the second digital signature associated with the second cryptosystem, and the third digital signature associated with the third cryptosystem, wherein no dependency exists between the first digital signature, the second digital signature, and the third digital signature (522).

[0057] In one embodiment, providing the hybrid security certificate includes packaging the data, the first digital signature, and the second digital signature in a single Distinguished Encoding Rules (DER) sequence 524. In one or more embodiments, the hybrid security certificate includes a SignerInfo block that includes a first public key associated with the first cryptosystem, the first digital signature, and a second public key associated with the second cryptosystem and the second digital signature 526.

[0058] Advantageously, the hybrid security certificate generation functionality and hybrid security certificate formats disclosed herein can be used in a variety of computing environments, including, for example, public key infrastructure environments. In such environments, cryptographic systems can be used to communicate securely over public channels. For example, some cryptographic systems provide confidentiality by encrypting messages, and some cryptographic systems provide authenticity through digital signatures. Many cryptographic systems include protocols that use cryptographic keys. For example, in a public key infrastructure (PKI), the cryptographic keys include a public key and a private key for each entity, and a certification authority can issue security certificates that certify the public keys. In one or more implementations, the certification authority can utilize hybrid security certificates as disclosed herein.

[0059] Other variations and embodiments are possible.

[0060] The hybrid security credential functionality of one or more aspects of the present invention can be incorporated into and used in many computing environments. An example computing environment is described with reference to FIG. 6A. As an example, the computing environment is based on the z / Architecture® hardware architecture offered by International Business Machines Corporation of Armonk, New York. However, the z / Architecture hardware architecture is only one example architecture. The computing environment may also be based on other architectures, including, but not limited to, the Intel x86 architecture, other architectures from International Business Machines Corporation, or architectures from other companies, or combinations thereof.

[0061] 6A, computing environment 600 includes a computer system 602, shown, for example, in the form of a general-purpose computing device. Computer system 602 may include, but is not limited to, one or more processors or processing units 604 (e.g., central processing units (CPUs)), memory 606 (e.g., system memory, main memory, main storage, central storage, or storage), and one or more input / output (I / O) interfaces 608, coupled together via one or more buses and / or other connections 610.

[0062] Bus 610 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 or local bus using any of a variety of bus architectures. By way of example, and without limitation, such architectures include Industry Standard Architecture (ISA), Micro Channel Architecture (MCA), Enhanced ISA (EISA), Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI).

[0063] The memory 606 may include a cache 612, such as a shared cache, that may be coupled to a local cache 614 of the processor 604, for example. Additionally, the memory 606 may include one or more programs or applications 616, at least one operating system 618, one or more computer-readable program instructions 620, and multiple cryptographic systems 622. The computer-readable program instructions 620 and the cryptographic systems 622 may be configured to perform the functions of embodiments of aspects of the present invention.

[0064] In one embodiment, memory 606 (e.g., at least the hardware system area of ​​memory 606) is coupled to one or more auxiliary processors 621 via one or more auxiliary processor buses 623 and, in one or more embodiments, via an AP transport layer.

[0065] The computer system 602 can communicate with one or more external devices 630, such as a user terminal, a tape drive, a pointing device, a display, and one or more data storage devices 634, for example, via an I / O interface 608. The data storage devices 634 can store one or more programs 636, one or more computer-readable program instructions 638, or data, or a combination thereof, etc. The computer-readable program instructions can be configured to perform the functions of embodiments of aspects of the present invention.

[0066] The computer system 602 may also communicate with a network interface 632, for example, via the I / O interface 608, which enables the computer system 602 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 computer devices or systems.

[0067] Computer system 602 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 (typically referred to as a "hard drive"), a magnetic disk drive for reading from and writing to removable, non-volatile magnetic disks (e.g., "floppy disks"), or an optical disk drive for reading from and writing to removable, non-volatile optical disks, such as CD-ROMs, DVD-ROMs, or other optical media, or a combination thereof. It should be understood that other hardware and / or software components may be used in combination with computer system 602. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archive storage systems.

[0068] Computer system 602 is operational 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 602 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.

[0069] Another example of a computing environment for incorporating and using one or more aspects of the present invention is described below with reference to Figure 6B. By way of example, the computing environment of Figure 6B may be based on the z / Architecture® hardware architecture offered by International Business Machines Corporation. However, the z / Architecture The hardware architecture is only one exemplary architecture. Again, the computing environment may be based on other architectures, including, but not limited to, the Intel x86 architecture, other architectures from International Business Machines Corporation, or other companies, or combinations thereof.

[0070] In one example, computing environment 650 includes a central electronics complex (CEC) 652. CEC 652 includes multiple components, such as, for example, memory 654 (also known as system memory, main memory, main storage, central storage, storage) coupled to one or more processors (also known as central processing units (CPUs)) 656 and an input / output (I / O) subsystem 658. Further, in one embodiment, memory 654 (e.g., at least the hardware system area of ​​memory 654) is coupled to one or more auxiliary processors 657 via one or more auxiliary processor buses, and in one or more embodiments, via an AP transport layer.

[0071] I / O subsystem 658, which may be part of or separate from the central electronics complex, directs the flow of information between main storage 654 and input / output control unit 660 and input / output (I / O) devices 662 coupled to the central electronics complex.

[0072] Many types of I / O devices can be used. One particular type is a data storage device 664. The data storage device 664 can store one or more programs 666, one or more computer readable program instructions 668, or data, or a combination thereof, etc. The computer readable program instructions can be configured to perform the functions of embodiments of aspects of the present invention.

[0073] Central electronics complex 652 can include and / or couple to removable / non-removable, volatile / non-volatile computer system storage media. For example, it can include and / or couple to non-removable, non-volatile magnetic media (typically referred to as a "hard drive"), magnetic disk drives for reading from and writing to removable, non-volatile magnetic disks (e.g., "floppy disks"), or optical disk drives for reading from and writing to removable, non-volatile optical disks, such as CD-ROMs, DVD-ROMs, or other optical media, or combinations thereof. It should be understood that other hardware and / or software components can be used in combination with central electronics complex 652. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data archive storage systems, and the like.

[0074] Additionally, central electronics complex 652 is operational 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 central electronics complex 652 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.

[0075] Central electronics complex 652, in one or more embodiments, provides logical partitioning and / or virtualization support. In one embodiment, as shown in FIG. 6C , memory 654 includes, for example, one or more logical partitions 670, a hypervisor 672 that manages the logical partitions, and processor firmware 674. One example of hypervisor 672 is Processor Resource / System Manager (PR / SM) offered by International Business Machines Corporation of Armonk, New York. As used herein, firmware 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, trusted software or microcode specific to the underlying hardware, including proprietary code typically delivered as microcode that controls operating system access to system hardware.

[0076] Each logical partition 670 is capable of functioning as a separate system. That is, each logical partition can be reset independently, can execute guest operating systems 676, such as the z / OS® operating system offered by International Business Machines Corporation of Armonk, New York, or control code 678, such as Coupling Facility Control Code (CFCC), and can operate with different programs 680. An operating system or application program running in a logical partition appears to have access to a complete and flawless system, but in reality, only a portion of it is available. While z / OS is provided as an example, other operating systems can be used in accordance with one or more aspects of the present invention.

[0077] Memory 654 is coupled to CPU 656 (FIG. 6B), which is a physical processor resource that can be assigned to a logical partition. For example, logical partition 670 includes one or more logical processors, each of which represents all or a share of physical processor resource 656 that can be dynamically assigned to a logical partition.

[0078] In yet another embodiment, the central electronics complex provides virtual machine support (with or without logical partitioning support). As shown in FIG. 6D , memory 654 of central electronics complex 652 includes, for example, one or more virtual machines 690, a virtual machine manager such as hypervisor 692 that manages the virtual machines, and processor firmware 694. One example of hypervisor 692 is the z / VM® hypervisor offered by International Business Machines Corporation of Armonk, New York. A hypervisor is sometimes referred to as a host. z / OS and z / VM are trademarks or registered trademarks of International Business Machines Corporation in at least one jurisdiction.

[0079] The CPC's virtual machine support provides the ability to operate multiple virtual machines 690, each running a different program 696 and capable of running a guest operating system 698, such as the Linux® operating system. Each virtual machine 690 can function as a separate system; that is, each virtual machine can be reset independently, run a guest operating system, and run a different program. An operating system or application program running within a virtual machine appears to have access to a complete and flawless system, but in reality, only a portion of it is available. While z / VM and Linux are provided as examples, other virtual machine managers and operating systems can be used in accordance with one or more aspects of the present invention. The registered trademark Linux® is used under sublicense from the Linux Foundation, the exclusive worldwide trademark owner of Linus Torvalds.

[0080] Another embodiment of a computing environment incorporating and using one or more aspects of the present invention is described with reference to FIG. 7A. In this example, computing environment 710 includes, for example, a native central processing unit (CPU) 712, memory 714, and one or more input / output devices or interfaces 716 coupled to each other, for example, via one or more buses 718 and / or other connections. By way of example, computing environment 710 may include a PowerPC® processor offered by International Business Machines Corporation of Armonk, New York, an HP Superdome with an Intel Itanium II processor offered by Hewlett Packard Co. of Palo Alto, California, or other machines based on architectures offered by International Business Machines Corporation, Hewlett Packard, Intel Corporation, Oracle, or others, or a combination thereof. PowerPC is a trademark or registered trademark of International Business Machines Corporation in at least one jurisdiction. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

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

[0082] Additionally, native central processing unit 712 executes instructions and code stored in memory 714. In one particular example, the central processing unit executes emulator code 722 stored in memory 714. This code allows a computing environment configured with one architecture to emulate another architecture. For example, emulator code 722 allows machines based on architectures other than the z / Architecture hardware architecture, such as PowerPC processors or HP Superdome servers, to emulate the z / Architecture hardware architecture and execute software and instructions developed based on the z / Architecture hardware architecture.

[0083] Further details related to emulator code 722 are described with reference to FIG. 7B . Guest instructions 730 stored in memory 714 include software instructions (e.g., correlating to machine instructions) developed to execute on an architecture other than that of native CPU 712. For example, guest instructions 730 may have been designed to execute on a processor based on the z / Architecture hardware architecture, but instead are emulated on native CPU 712, which may be, for example, an Intel Itanium II processor. In one example, emulator code 722 includes an instruction fetch routine 732 that retrieves one or more guest instructions 730 from memory 714 and optionally provides local buffering for the retrieved instructions. It also includes an instruction translation routine 734 that determines the type of the retrieved guest instruction and translates the guest instruction into one or more corresponding native instructions 736. This translation includes, for example, identifying a function to be performed by the guest instruction and selecting a native instruction to perform that function.

[0084] Additionally, emulator code 722 includes an emulation control routine 740 that causes native instructions to be executed. Emulation control routine 740 causes native CPU 712 to execute a routine of native instructions that emulates one or more previously fetched guest instructions, and upon completion of such execution, may return control to an instruction fetch routine to emulate the fetch of the next guest instruction or instructions. Execution of native instructions 736 may include loading data from memory 714 into registers, storing data from registers back to memory, or performing some type of arithmetic or logical operation, as determined by the translation routine.

[0085] Each routine may, for example, be implemented in software, stored in memory, and executed by the native central processing unit 712. In other examples, one or more of the routines or operations may be implemented in firmware, hardware, software, or some combination thereof. The emulated processor's registers may be emulated using the native CPU's registers 20 or by using locations in memory 714. In an embodiment, the guest instructions 30, native instructions 36, and emulator code 722 may reside in the same memory or may be distributed among different memory devices.

[0086] Additionally, in one embodiment, computing environment 710 includes one or more auxiliary processors 715 coupled to memory 714. The one or more auxiliary processors are defined in one architecture and configured to emulate another architecture. For example, the auxiliary processor(s) may take guest commands of the emulated architecture, translate the guest commands into native commands of one architecture, and execute the native commands.

[0087] The computing environments described above are merely examples of computing environments that may be used. Other environments may be used, including, but not limited to, non-partitioned, partitioned, cloud, or emulated environments, or combinations thereof, and embodiments are not limited to any one environment. While various examples of computing environments are described herein, one or more aspects of the present invention may be used with many types of environments. The computing environments provided herein are merely examples.

[0088] Each computing environment may be configured to include one or more aspects of the present invention, for example, each may be configured for hybrid security certificate functionality in accordance with one or more aspects of the present invention.

[0089] While various embodiments have been described herein, many modifications and other embodiments are possible without departing from the spirit of the aspects of the present invention. It should be noted that, unless specifically contradictory, each aspect or feature described herein, and variations thereof, can be combined with any other aspect or feature.

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

[0091] Although this disclosure includes detailed descriptions of cloud computing, implementation of the teachings described herein is not limited to cloud computing environments. Rather, embodiments of the invention can be practiced in conjunction with any other type of computing environment now known or later developed.

[0092] 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 released with minimal management effort or interaction with the service provider. This cloud model may include at least five characteristics, at least three service models, and at least four implementation models.

[0093] The characteristics are as follows: On-Demand Self-Service: Cloud consumers can unilaterally provision computing capacity, such as server time or network storage, automatically as needed, without the need for human interaction with the service provider. Broad network access: Computing power is available over the network and can be accessed through standard mechanisms, facilitating use by heterogeneous thin or thick client platforms (e.g., cell phones, laptops, PDAs). Resource Pooling: Computing resources from a provider are pooled and offered to multiple consumers using a multi-tenant model. Various physical and virtual resources are dynamically allocated and reallocated based on demand. Consumers generally have no control or knowledge of the exact location of the resources they are provided with, resulting in a sense of location independence. However, consumers may be able to determine location at a higher level of abstraction (e.g., country, state, data center). Rapid Elasticity: Computing capacity can be provisioned quickly and elastically, sometimes automatically, to instantly scale out and quickly release to instantly scale in. To the consumer, the computing power available for provisioning often appears unlimited, and can be purchased at any time and in any quantity. Metered Services: Cloud systems leverage measurement capabilities at a level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, active user accounts) to automatically control and optimize resource usage. Resource usage can be monitored, controlled, and reported to provide transparency to both providers and consumers of utilized services.

[0094] The service model is as follows: Software as a Service (SaaS): The functionality offered to the consumer is the availability of a provider's applications running on a cloud infrastructure that can be accessed from a variety of client devices through a thin client interface such as a web browser (e.g., webmail). The consumer does not manage or control the underlying cloud infrastructure, including the network, servers, operating systems, storage, or even individual application functionality, except for limited user-specific application configuration settings. Platform as a Service (PaaS): The capability offered to consumers is to deploy applications they create or acquire 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 the network, servers, operating systems, or storage, but does have control over the deployed applications and, in some cases, the configuration of their hosting environment. Infrastructure as a Service (IaaS): The functionality offered to consumers is the provisioning of processors, storage, networking, and other basic computing resources on which they 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 system, storage, and deployed applications, and in some cases partial control over some network components (e.g., host firewalls).

[0095] The deployment model is as follows: Private Cloud: This cloud infrastructure is dedicated to a specific organization and can be managed by that organization or a third party, and can exist on-premise or off-premise. Community Cloud: This cloud infrastructure is shared by multiple organizations to support a specific community with common concerns (e.g., mission, security requirements, policies, and compliance). This cloud infrastructure can be managed by those organizations or a third party and can exist on-premises or off-premises. Public cloud: This cloud infrastructure is available to the general public or large industry organizations and is owned by an organization that sells cloud services. Hybrid cloud: This cloud infrastructure combines two or more cloud models (private, community, or public), each of which retains its inherent nuances but is bound by standards or specific technologies that enable data and application portability (e.g., cloud bursting for load balancing between clouds).

[0096] A cloud computing environment is a service-oriented environment that emphasizes statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure that includes a network of interconnected nodes.

[0097] Referring to FIG. 8, an exemplary cloud computing environment 50 is shown. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 52, with which local computing devices used by cloud consumers (e.g., a personal digital assistant (PDA) or mobile phone 54A, a desktop computer 54B, a laptop computer 54C, or an automobile computer system 54N, or combinations thereof) can communicate. The nodes 52 can communicate with each other. The nodes 52 can be physically or virtually grouped (not shown) in one or more networks, such as, for example, a private, community, public, or hybrid cloud, or combinations thereof, as described above. This enables the cloud computing environment 50 to provide infrastructure, platform, or software as a service, or combinations thereof, for which the cloud consumer does not need to maintain resources on the local computing device. It should be understood that the types of computing devices 54A-N shown in FIG. 8 are merely exemplary, and that the computing nodes 52 and the cloud computing environment 50 can communicate with any type of electronic device via any type of network or network-addressable connection (e.g., using a web browser), or both.

[0098] Referring to Figure 9, a set of functional abstraction model 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 merely exemplary, and embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided:

[0099] Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframe 61, reduced instruction set computer (RISC) architecture-based server 62, server 63, blade server 64, storage device 65, and network and network components 66. In some embodiments, software components include network application server software 67 and database software 68.

[0100] The virtualization layer 70 provides an abstraction layer from which the following virtual entities can be provided, for example: virtual servers 71, virtual storage 72, virtual networks including virtual private networks 73, virtual applications and operating systems 74, and virtual clients 75.

[0101] By way of example, the management layer 80 may provide the following functions: Resource provisioning 81 enables dynamic procurement of computing and other resources utilized to execute tasks within the cloud computing environment; Metering and pricing 82 enables cost tracking as resources are utilized within the cloud computing environment and billing or invoicing for the consumption of these resources; By way of example, these resources may include application software licenses; Security enables identification and verification of cloud consumers and tasks, as well as 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 enables allocation and management of cloud computing resources so that requested service levels are met; Service level agreement (SLA) planning and fulfillment 85 enables advance arrangement and procurement of anticipated future cloud computing resources required in accordance with SLAs.

[0102] The workload layer 90 provides examples of functionality available to a cloud computing environment. Examples of workloads and functionality that can be provided from this layer include mapping and navigation 91, software development and lifecycle management 92, virtual classroom instruction delivery 93, data analytics processing 94, transaction processing 95, and hybrid security certificate processing 96.

[0103] The present invention may be a system, method, or computer program product, or combination thereof, integrated at any possible level of technical detail. The computer program product may include a computer-readable storage medium having stored thereon computer-readable program instructions for causing a processor to carry out aspects of the present invention.

[0104] A computer-readable storage medium may be a tangible device capable of retaining and storing instructions for use by an instruction execution device. The computer-readable storage medium may be, by way of example only, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or a suitable combination thereof. More specific examples of computer-readable storage media include portable computer diskettes, hard disks, RAM, ROM, EPROM (or flash memory), SRAM, CD-ROMs, DVDs, memory sticks, floppy disks, mechanically encoded devices having instructions recorded thereon, such as punch cards or ridge-in-groove structures, and suitable combinations thereof. As used herein, a computer-readable storage medium should not be construed as a transitory signal per se, such as an electric wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or an electrical signal transmitted over a wire.

[0105] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device or to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof). The network may be comprised of copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface in each computing / processing device receives the 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.

[0106] Computer-readable program instructions for carrying out operations of the present invention may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or object-oriented programming languages ​​such as Smalltalk, C++, etc., and procedural programming languages ​​such as the "C" programming language and similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, as a standalone software package, or partially on the user's computer. Alternatively, the computer may be executed partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via 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) can execute computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the computer-readable program instructions in order to carry out aspects of the present invention.

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

[0108] These computer-readable program instructions can be provided to a processor of a computer or other programmable data processing apparatus to create a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions can also be stored in a computer-readable storage medium connectable to a computer, programmable data processing apparatus, or other device, or combination thereof, that functions in a particular way, such that the computer-readable storage medium having the instructions stored thereon configures one of the products including instructions that implement aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0109] Computer-readable program instructions, such as instructions to perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams on a computer, other programmable apparatus, or other device, can also be loaded into a computer, other programmable data processing apparatus, or other device to perform a series of operational steps on the computer, other programmable apparatus, or other device to generate a computer-implemented process.

[0110] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of executable 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 portion of instructions, which constitute one or more executable instructions for implementing the specified logical function(s). In some alternative embodiments, the functions shown in the blocks may occur out of the order shown in the figures. For example, two blocks shown in succession may actually be accomplished as a single step, executed concurrently, substantially concurrently, partially, or fully in a time-overlapping manner, or the blocks may be executed in the reverse order depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a special-purpose hardware-based system that performs the specified functions or operations or executes a combination of special-purpose hardware and computer instructions.

[0111] In addition to the above, one or more aspects may be provided, offered, deployed, managed, serviced, etc. by a service provider that offers management of a customer environment. For example, the service provider may create, maintain, support, etc., computer code and / or computer infrastructure that implements one or more aspects for one or more customers. In return, the service provider may receive payments from the customer, by way of example, based on 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.

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

[0113] As a further aspect, a computing infrastructure may be deployed that includes computer-readable code integrated into a computing system, where the code in combination with the computing system is capable of performing one or more embodiments.

[0114] As yet another aspect, a process for integrating a computing infrastructure may be provided, the process comprising integrating computer-readable code into a computer system including a computer-readable medium, the computer medium including one or more embodiments, the code in combination with the computer system being capable of executing one or more embodiments.

[0115] Although various embodiments have been described above, they are merely illustrative. For example, computing environments of other architectures may be used to incorporate one or more embodiments. Furthermore, different instructions, commands, or operations may be used. Furthermore, different types of indications or tags may be specified. Many variations are possible.

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

[0117] Additionally, other types of computing environments may also be beneficial and may be used. As an example, a data processing system suitable for storing and / or executing program code may be used that includes at least two processors coupled directly or indirectly to memory elements via a system bus. The memory elements may include, for example, local memory employed during the actual execution of the program code, bulk 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 bulk storage during execution.

[0118] Input / output or I / O devices (including but not limited to keyboards, displays, pointing devices, DASDs, tapes, CDs, DVDs, thumb drives, and other memory media, etc.) may be coupled to the system either directly or through intervening 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 intervening private or public networks. Modems, cable modems, and Ethernet cards are just a few of the available types of network adapters.

[0119] 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 include the plural forms unless the context makes clear otherwise. It will be further understood that as used herein, the terms "comprises" and / or "comprising" specify the presence of stated features, integers, steps, operations, elements, or components, or combinations thereof, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof, or combinations thereof.

[0120] Corresponding structure, materials, acts, and equivalents of all means or step-plus-function elements in the following claims are intended to include any structure, material, or acts for performing the function in combination with the elements of other claims as specifically claimed. The description of one or more embodiments has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosed form. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described to best explain various aspects and applications, and to enable those skilled in the art to recognize a variety of different embodiments with various modifications as suited to the particular use contemplated.

Claims

1. 1. A computer program for facilitating processing within a computing environment, comprising: obtaining, by an auxiliary processor of a machine in the computing environment, a request for security credentials from a main processor of the machine, the request being obtained from a memory of the machine via a transport layer of the machine; the main processor, the auxiliary processor, the memory, and the transport layer are part of a common machine within the computing environment; The computer program includes program instructions that cause the main processor and the auxiliary processor to perform the following method: The method comprises: generating a hybrid security certificate using a plurality of cryptosystems, said generating comprising: obtaining data to be included in the hybrid security certificate; generating a first digital signature associated with a first cryptosystem of the plurality of cryptosystems covering the data; generating a second digital signature associated with a second cryptosystem of the plurality of cryptosystems covering the data; providing the hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, wherein the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature; the first digital signature associated with the first cryptosystem covers the data independent of the second cryptosystem, and the second digital signature associated with the second cryptosystem covers the data independent of the first cryptosystem, and the data does not include or depend on attributes or keys of the first cryptosystem or the second cryptosystem; Computer program.

2. the first cryptosystem comprises an asymmetric cryptosystem; the second cryptosystem includes a quantum-safe cryptosystem; 2. The computer program of claim 1.

3. The computer program product of claim 2 , wherein the quantum-safe cryptography system comprises a lattice-based cryptography approach.

4. 2. The computer program product of claim 1, wherein the first cryptosystem comprises an Elliptic Curve Cryptography (ECC) cryptosystem and the second cryptosystem comprises a Dilithium cryptosystem.

5. generating the hybrid security certificate includes: further comprising associating a first public key with the data, the first public key being associated with the first cryptosystem; generating the first digital signature uses a first private key in generating the first digital signature associated with the first cryptosystem covering the data, and generating the first digital signature uses properties of the first public key; 2. The computer program of claim 1.

6. generating the hybrid security certificate includes: associating a second public key with the data, the second public key being associated with the second cryptosystem; generating the second digital signature uses a second private key to generate the second digital signature associated with the second cryptosystem covering the data, and generating the second digital signature uses a property of the second public key; 6. A computer program according to claim 5.

7. generating the hybrid security certificate includes: generating a third digital signature associated with a third cryptosystem covering the data; providing the hybrid security certificate, The data; the first digital signature associated with the first cryptosystem; the second digital signature associated with the second cryptosystem; and and the third digital signature associated with the third cryptosystem; There is no dependency relationship between the first digital signature, the second digital signature, and the third digital signature.

2. The computer program of claim 1.

8. providing the hybrid security certificate, The data; the first digital signature; and 2. The computer program product of claim 1, further comprising enclosing the second digital signature and the first digital signature in a single Distinguished Encoding Rules (DER) sequence.

9. The hybrid security certificate comprises: a first public key associated with the first cryptosystem; and the first digital signature; and a second public key associated with the second cryptosystem and the second digital signature; and 9. The computer program of claim 8, further comprising a SignerInfo block including:

10. 1. A computer system for facilitating processing in a computing environment, the computer system comprising: Memory and at least a main processor and a coprocessor in communication with said memory; The computer system includes: obtaining, by the auxiliary processor of a machine in the computing environment, a request for a security credential from the main processor of the machine, the request being obtained from the memory of the machine via a transport layer of the machine; the main processor, the auxiliary processor, the memory, and the transport layer are part of a common machine within the computing environment; The computer system is configured to perform a method, the method comprising: generating a hybrid security certificate using a plurality of cryptosystems, said generating comprising: obtaining data to be included in the hybrid security certificate; generating a first digital signature associated with a first cryptosystem of the plurality of cryptosystems covering the data; generating a second digital signature associated with a second cryptosystem of the plurality of cryptosystems covering the data; providing the hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, wherein the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature; the first digital signature associated with the first cryptosystem covers the data independent of the second cryptosystem, and the second digital signature associated with the second cryptosystem covers the data independent of the first cryptosystem, and the data does not include or depend on attributes or keys of the first cryptosystem or the second cryptosystem; Computer system.

11. 11. The computer system of claim 10, wherein the first cryptosystem comprises an asymmetric cryptosystem, and the second cryptosystem comprises a quantum-safe cryptosystem, the quantum-safe cryptosystem comprising a lattice-based cryptography approach.

12. associating a first public key with the data, the first public key being associated with the first cryptosystem, and generating the first digital signature using a first private key in generating the first digital signature associated with the first cryptosystem that covers the data, and wherein generating the first digital signature uses a property of the first public key; associating a second public key with the data, the second public key being associated with the second cryptosystem, and generating the second digital signature using a second private key to generate the second digital signature associated with the second cryptosystem covering the data, the generating the second digital signature using a property of the second public key; The computer system of claim 10 further comprising:

13. generating a third digital signature associated with a third cryptosystem covering the data; providing the hybrid security certificate includes providing the hybrid security certificate having the data, the first digital signature associated with the first cryptosystem, the second digital signature associated with the second cryptosystem, and the third digital signature associated with the third cryptosystem, wherein no dependency exists between the first digital signature, the second digital signature, and the third digital signature.

11. The computer system of claim 10.

14. 11. The computer system of claim 10, wherein providing the hybrid security certificate includes wrapping the data, the first digital signature, and the second digital signature in a single Distinguished Encoding Rules (DER) sequence.

15. 1. A computer-implemented method for facilitating processing in a computing environment, comprising: obtaining, by an auxiliary processor of a machine in the computing environment, a request for security credentials from a main processor of the machine, the request being obtained from a memory of the machine via a transport layer of the machine; the main processor, the auxiliary processor, the memory, and the transport layer are part of a common machine within the computing environment; The computer-implemented method comprises: generating a hybrid security certificate using a plurality of cryptosystems, said generating comprising: obtaining data to be included in the hybrid security certificate; generating a first digital signature associated with a first cryptosystem of the plurality of cryptosystems covering the data; generating a second digital signature associated with a second cryptosystem of the plurality of cryptosystems covering the data; providing the hybrid security certificate, the hybrid security certificate including the data, the first digital signature associated with the first cryptosystem, and the second digital signature associated with the second cryptosystem, wherein the first digital signature is independent of a key of the second cryptosystem or the second digital signature, and the second digital signature is independent of a key of the first cryptosystem or the first digital signature; the first digital signature associated with the first cryptosystem covers the data independent of the second cryptosystem, and the second digital signature associated with the second cryptosystem covers the data independent of the first cryptosystem, and the data does not include or depend on attributes or keys of the first cryptosystem or the second cryptosystem; Computer-implemented methods.

16. 16. The computer-implemented method of claim 15, wherein the first cryptosystem comprises an asymmetric cryptosystem, and the second cryptosystem comprises a quantum-safe cryptosystem, the quantum-safe cryptosystem comprising a lattice-based cryptography approach.

17. generating the hybrid security certificate includes: associating a first public key with the data, the first public key being associated with the first cryptosystem, and generating the first digital signature using a first private key in generating the first digital signature associated with the first cryptosystem that covers the data, and wherein generating the first digital signature uses a property of the first public key; associating a second public key with the data, the second public key being associated with the second cryptosystem, and generating the second digital signature using a second private key to generate the second digital signature associated with the second cryptosystem covering the data, the generating the second digital signature using a property of the second public key; The computer-implemented method of claim 15 further comprising:

Images