Software configuration verification system, confidential computing device, software configuration verification method, and program
The software configuration verification system addresses the challenge of verifying software configurations within isolated execution environments by generating and comparing configuration tables, ensuring legitimacy and resistance to attacks.
Patent Information
- Application Number
- PCT/JP2025/017192
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-12
- Publication Date
- 2026-11-19
AI Technical Summary
Existing systems fail to verify the software configuration within isolated execution environments, such as VMs, provided by external cloud providers, ensuring legitimacy and intended configuration.
A software configuration verification system comprising an image management device, a confidential computing device, and a verification device, which generates and compares software configuration tables to ensure the legitimacy of the software configuration within the isolated execution environment.
The system enables verification of the software configuration within isolated execution environments, ensuring legitimacy and intended configuration, providing resistance to tampering and replay attacks.
Smart Images

Figure JP2025017192_19112026_PF_FP_ABST
Abstract
Description
Software configuration verification system, confidential computing device, software configuration verification method, program
[0001] The present disclosure relates to a software configuration verification system, a confidential computing device, a software configuration verification method, and a program that verify the configuration of software operating in an isolated execution environment when a confidential computing environment (hereinafter also referred to as an isolated execution environment) is started up.
[0002] As a means for visualizing the configuration of software included in a computing environment such as a VM (Virtual Machine), SBOM (Software Bill of Materials) is known. By using SBOM, it is possible to obtain a list of software configurations included in the computing environment. SBOM is currently used for the purpose of externally visualizing the software configuration of the running computing environment.
[0003] Further, in the field of confidential computing, verification of attestation reports by remote attestation is utilized as a method for verifying the legitimacy of an execution environment (Non-Patent Document 1).
[0004] H. Birkholz, D. Thaler, M. Richardson, N. Smith, W. Pan, "RFC 9334 - Remote ATtestation procedureS (RATS) Architecture", [online], January 2023, [retrieved on May 1, 2025], Internet <URL: https: / / www.rfc-editor.org / rfc / rfc9334.html>
[0005] However, the above attestation report could only verify the legitimacy of the execution environment, such as whether the launched confidential computing environment was running on a TEE (Trusted Execution Environment).
[0006] Therefore, when an external cloud provider or similar entity provides the confidential computing environment to a user in the form of a VM or similar, there was a problem in that it was not possible to verify whether the software configuration included in the launched VM image was configured as intended.
[0007] Therefore, the purpose of this disclosure is to provide a software configuration verification system that can verify the configuration of software running within an isolated execution environment when the isolated execution environment is started.
[0008] The software configuration verification system of this disclosure includes an image management device, a confidential computing device, and a verification device. The image management device includes an image file generation unit, a first software configuration table generation unit, and an environment startup unit. The confidential computing device includes an isolated execution environment control unit and a second software configuration table generation unit. The verification device includes a software configuration table verification unit.
[0009] The image file generation unit generates an image file. The first software configuration table generation unit generates a first software configuration table containing the correct values from the image file. The environment startup unit sends a startup instruction containing the image file to the confidential computing device. The isolated execution environment control unit starts the isolated execution environment based on the startup instruction. The second software configuration table generation unit generates a second software configuration table based on the software running in the isolated execution environment and sends it to the verification device. The software configuration table verification unit receives the first software configuration table and verifies the second software configuration table.
[0010] According to the software configuration verification system disclosed herein, the configuration of software running within an isolated execution environment can be verified when the isolated execution environment is started.
[0011] A block diagram showing the functional configuration of the software configuration verification system of Example 1. A sequence diagram showing the operation of the software configuration verification system of Example 1. A block diagram showing the functional configuration of the software configuration verification system of Modification 1. A sequence diagram showing the operation of the software configuration verification system of Modification 1. A block diagram showing the functional configuration of the software configuration verification system of Example 2. A sequence diagram showing the operation of the software configuration verification system of Example 2. A block diagram showing the functional configuration of the software configuration verification system of Modification 2. A sequence diagram showing the operation of the software configuration verification system of Modification 2. A block diagram showing the functional configuration of the software configuration verification system of Example 3. A sequence diagram showing the operation of the software configuration verification system of Example 3. A block diagram showing the functional configuration of the software configuration verification system of Example 4. A sequence diagram showing the operation of the software configuration verification system of Example 4. A diagram showing an example of the functional configuration of a computer.
[0012] The embodiments of this disclosure will be described in detail below. Components having the same function will be numbered the same, and redundant explanations will be omitted.
[0013] In Example 1, a software configuration verification system is disclosed that, as a means of guaranteeing the legitimacy of the software group constituting a confidential computing environment realized by TEE, etc., at startup, verifies the legitimacy of the software configuration table generated in response to the generation of a VM image, etc. (hereinafter referred to as the first software configuration table) by comparing and verifying it with a software configuration table generated within the confidential computing environment after the confidential computing environment has started (hereinafter referred to as the second software configuration table), using the first software configuration table generated in response to the generation of a VM image, etc., as the correct value.
[0014] This embodiment shows the system configuration and operation when targeting a CVM (Controller Virtual Machine) running on an isolated execution environment.
[0015] It is assumed that the validity of the CVM's operation in the isolated execution environment has already been verified using methods such as remote attestation.
[0016] As shown in Figure 1, the software configuration verification system 1 of this embodiment includes an image management device 11, a confidential computing device 12, and a verification device 13.
[0017] The image management device 11 is responsible for generating and managing image files to be executed by the confidential computing device 12. The confidential computing device 12 operates as the host of the confidential computing environment. The verification device 13 verifies the legitimacy of the confidential computing device 12. These devices are assumed to be connected to each other in a manner that allows them to communicate with one another. Furthermore, users who utilize the isolated execution environment controlled by the confidential computing device 12, and their terminals, are referred to as environment users 9.
[0018] As shown in the figure, the image management device 11 includes an image file generation unit 111, an image repository 112, a first software configuration table generation unit 113, a software configuration table repository 114, and an environment startup unit 115. The confidential computing device 12 includes an isolated execution environment control unit 121, and within the isolated execution environment (see the dashed-dotted frame in the figure), a second software configuration table generation unit 122 and a software function unit 123. The verification device 13 includes a software configuration table verification unit 131.
[0019] The operation of each component will be explained below with reference to Figure 2.
[0020] <Image File Generation Unit 111> The image file generation unit 111 generates an image file and records it in the image repository 112 (S111). As mentioned above, in this embodiment, a CVM is used as an example, so in this step, an image file of the CVM to be started is generated.
[0021] <Image Repository 112> The image repository 112 is a repository that stores and saves the image files generated by the image file generation unit 111. The image files are VM images, etc., and in this embodiment, they are CVM image files.
[0022] The image repository 112 manages image files using an identification ID as a key and returns the image file corresponding to the identification ID received from the environment startup unit 115.
[0023] The image repository 112 may be configured as an integrated repository with the software configuration table repository 114, which will be described later.
[0024] <First Software Configuration Table Generation Unit 113> The first software configuration table generation unit 113 generates a first software configuration table (SBOM) which is the correct value from the image file (CVM image in this embodiment) generated in step S111 and records it in the software configuration table repository 114 (S113).
[0025] <Software Configuration Table Repository 114> The software configuration table repository 114 is a repository that stores and saves the software configuration tables generated in step S113 for each identification ID.
[0026] The software configuration table repository 114 returns a first software configuration table (correct value) corresponding to the identification ID received from the software configuration table verification unit 131, which will be described later.
[0027] <Environment User 9> Environment user 9 sends a startup request to the image management device 11 specifying the identification ID of the image file to be started. The startup request may also be executed by a user other than environment user 9. If a user other than environment user 9 executes the startup request, it is preferable to notify environment user 9 of the identification ID specified in the startup request.
[0028] <Environment Activation Unit 115> When the environment activation unit 115 receives an activation request from an environment user 9 or the like (S115a), it sends an activation instruction to the confidential computing device 12 that includes an image file obtained from the image repository 112 (S115b).
[0029] <Isolated Execution Environment Control Unit 121> The isolated execution environment control unit 121 of the confidential computing device 12 starts the isolated execution environment (CVM in this embodiment) based on the start instruction received from the image management device 11 (S121a). The isolated execution environment control unit 121 can perform not only start control but also stop control of the isolated execution environment.
[0030] <Environment User 9> Environment user 9 sends a command to generate a second software configuration table to the confidential computing device 12. This generation command shall include an identification ID for the image file.
[0031] <Second Software Configuration Table Generation Unit 122> When the second software configuration table generation unit 122 receives a generation command from the environment user 9 or the like (S122a), it measures the software group operating in the isolated execution environment, generates a second software configuration table based on these software groups, and transmits it to the verification device 13 along with the identification ID of the image file (S122b).
[0032] Furthermore, the functionality of the second software configuration table generation unit 122 can be protected from tampering by using a remote attestation mechanism performed when the isolated execution environment is started. The integrity of the second software configuration table can also be ensured by RA (Remote Attestation).
[0033] <Software Configuration Table Verification Unit 131> The software configuration table verification unit 131 of the verification device 13 receives the second software configuration table and the identification ID of the image file from the confidential computing device 12, generates a correct answer value request including the identification ID, and transmits the correct answer value request to the image management device 11 (S131a).
[0034] The software configuration table repository 114 of the image management device 11 returns a first software configuration table (correct value) corresponding to the identification ID received from the software configuration table verification unit 131.
[0035] The software configuration table verification unit 131 of the verification device 13 receives the first software configuration table (correct value) and compares and verifies it with the second software configuration table (S131b).
[0036] The software configuration table verification unit 131 generates a notification of the comparison and verification results and sends it to the environment user 9 (S131c).
[0037] If the comparison and verification results in the inability to verify the legitimacy of the operation of the confidential computing device 12, the software configuration table verification unit 131 may send a stop command to the confidential computing device 12, and the isolation execution environment control unit 121 may stop the isolation execution environment (see the dashed arrow extending from 131 to 121 in Figure 1).
[0038] The comparison and verification results may also be sent to the environment user 9 via the isolated execution environment (see the dashed arrows extending from 131 to 122 and from 122 to 9 in Figure 1).
[0039] <Effects> While conventional remote attestation systems could only guarantee the legitimacy of the execution environment of a confidential computing environment, the software configuration verification system 1 of this embodiment can verify the legitimacy of the software configuration, including the software running in the initial state of the confidential computing environment, by utilizing the software configuration table.
[0040] [Modification 1] Hereinafter, a software configuration verification system according to Modification 1, which is a modification of Embodiment 1, will be described with reference to FIG. 3. As shown in the figure, the software configuration verification system 1-1 of the present modification includes the same image management apparatus 11 as that in Embodiment 1, a confidential computing apparatus 12-1 different from that in Embodiment 1, and the same verification apparatus 13 as that in Embodiment 1. The confidential computing apparatus 12-1 includes the same isolated execution environment control unit 121 as that in Embodiment 1, the same software function unit 123 as that in Embodiment 1, and a second software configuration table generation unit 122-1 different from that in Embodiment 1.
[0041] The operation of the second software configuration table generation unit 122-1 will be described with reference to FIG. 4.
[0042] <Second Software Configuration Table Generation Unit 122-1> The second software configuration table generation unit 122-1 of the present modification generates a correct value request including an identification ID, and transmits the request to the image management apparatus 11 (S122-1a). The software configuration table repository 114 of the image management apparatus 11 returns the first software configuration table (correct value) corresponding to the identification ID received from the second software configuration table generation unit 122-1.
[0043] The second software configuration table generation unit 122-1 receives the first software configuration table (correct value) from the software configuration table repository 114 of the image management apparatus 11 (S122-1b).
[0044] The second software configuration table generation unit 122-1 identifies the software configuration group to be measured from the first software configuration table, and generates a second software configuration table based on the identification result (S122-1b).
[0045] As described above, in the present modification, when the confidential computing apparatus 12-1 generates the second software configuration table, it is configured to refer to the first software configuration table which is the correct value.
[0046] In Embodiment 1 and Modification 1, the verification of the software configuration operating in the isolated execution environment is performed by the verification apparatus 13 which is an external apparatus, but the present invention is not limited to this. For example, the confidential computing apparatus itself may have the verification function.
[0047] Hereinafter, with reference to FIG. 5, the apparatus and functional configuration of the software configuration verification system according to Embodiment 2, in which the confidential computing device itself has a verification function, will be described. As shown in the figure, the software configuration verification system 2 of the present embodiment includes the same image management apparatus 11 as in Embodiment 1, and a confidential computing device 22 different from that in Embodiment 1, and has a configuration in which the verification apparatus 13 included in Embodiment 1 is omitted.
[0048] In the present embodiment, the verification function resides within an isolated execution environment. As shown in the figure, the confidential computing device 22 of the present embodiment includes the same isolated execution environment control unit 121 as in Embodiment 1, and within the isolated execution environment, includes the same second software configuration table generation unit 122 as in Embodiment 1, the same software functional unit 123 as in Embodiment 1, and a software configuration table verification unit 221 different from that in Embodiment 1.
[0049] As shown in FIG. 6, the software configuration table verification unit 221 executes the same processing as the software configuration table verification unit 131 of the verification apparatus 13 in Embodiment 1.
[0050] That is, the software configuration table verification unit 221 receives the second software configuration table and the identification ID of the image file from the second software configuration table generation unit 122, generates a correct value request including the identification ID, and transmits the correct value request to the image management apparatus 11 (S221a).
[0051] The software configuration table repository 114 of the image management apparatus 11 returns the first software configuration table (correct value) corresponding to the identification ID received from the software configuration table verification unit 221.
[0052] The software configuration table verification unit 221 receives the first software configuration table (correct value), and compares and verifies it with the second software configuration table (S221b).
[0053] The software configuration table verification unit 221 generates a notification of the comparison and verification result, and transmits the notification to the environment using user 9 (S221c).
[0054] As shown in Modification 1, the confidential computing device 22 may be configured to refer to the first software configuration table, which is the correct value, when generating the second software configuration table.
[0055] [Modification 2] In Example 1, Modification 1, and Example 2, the second software configuration table generation unit 122 generates a second software configuration table triggered by the receipt of a generation command from the environment user 9. However, this is not limited to this configuration, and the sending and receiving processing of generation commands from the environment user 9 may be omitted. Modification 2 is an example in which the sending and receiving processing of generation commands from the environment user 9 is omitted from the software configuration verification system 2 of Example 2.
[0056] As shown in Figure 7, the modified software configuration verification system 2-1 includes the same image management device 11 as in Examples 1 and 2, and a confidential computing device 22-1 which is a modified version of the confidential computing device 22 of Example 2.
[0057] The confidential computing device 22-1 includes the same isolated execution environment control unit 121 as in Example 2, and includes the same second software configuration table generation unit 122 as in Example 2, the same software function unit 123 as in Example 2, and a different software configuration table verification unit 221-1 within the isolated execution environment.
[0058] As shown in Figure 8, when the isolated execution environment is started (S121a), the software configuration table verification unit 221-1 sends an SBOM generation instruction to the second software configuration table generation unit 122 (S221-1). In this modified example, it is preferable that the image file identification ID is initially stored in the image file, or that it be configured to be obtainable from the isolated execution environment control unit 121 within the isolated environment.
[0059] Hereafter, as in Example 2, SBOM generation (S122b), generation and transmission of the correct answer request (S221a), verification (S221b), and generation and transmission of the comparison and verification result notification (S221c) are performed.
[0060] The systems of Examples 1 and 2 (Modified Examples 1 and 2) operate on the premise that the second software configuration table sent from the second software configuration table generation unit 122 has not been affected by tampering or other such means.
[0061] However, if the verification device is configured as an external device, for example, the second software configuration sheet is sent to the verification device via a general communication channel, which inherently carries the risk of tampering on the communication channel or attacks such as replay attacks by reusing old software configuration sheets.
[0062] Therefore, in Example 3, when verifying the generated second software configuration table, a signature verification process using signatures obtained through cooperation with a remote attestation station is applied as a method to guarantee the validity of the second software configuration table.
[0063] As shown in Figure 9, the software configuration verification system 3 of this embodiment is an extension of the software configuration verification system 1 of Embodiment 1, with the same image management device 11 as in Embodiment 1, a different confidential computing device 32 than in Embodiment 1, and a different verification device 33 than in Embodiment 1.
[0064] As shown in the figure, the confidential computing device 32 of this embodiment includes the same isolated execution environment control unit 121 as in Embodiment 1 and a signature assignment unit 322 different from that of Embodiment 1. Within the isolated execution environment, it includes the same second software configuration table generation unit 122 as in Embodiment 1, the same software function unit 123 as in Embodiment 1, and a hash generation unit 321 different from that of Embodiment 1. The verification device 33 includes the same software configuration table verification unit 131 as in Embodiment 1 and a signature verification unit 331 different from that of Embodiment 1. The operation of the added configuration requirements will now be explained with reference to Figure 10.
[0065] <Hash generation unit 321> The hash generation unit 321 hashes the second software configuration table generated by the second software configuration table generation unit 122 (S321). If hashing is not required, the hash generation unit 321 can be omitted.
[0066] <Signature Assignment Unit 322> The signature assignment unit 322 assigns a signature to the hash value of the second software configuration table generated in step S321 (S322). If hashing is omitted, the signature assignment unit 322 assigns a signature to the second software configuration table generated in step S122b (S322).
[0067] The signature assignment unit 322 can be implemented using a TPE-compatible CPU or the like that realizes an isolated execution environment, and components that have general signature functions such as a TPM (Trusted Platform Module) and encryption functions.
[0068] <Signature Verification Unit 331> The signature verification unit 331 verifies the validity of the signature attached to the second software configuration table (or the hash value of the second software configuration table) (S331).
[0069] In this embodiment, it is even preferable to include the signed second software configuration table (or the hash value of the signed second software configuration table) in any item of the attestation report.
[0070] In this case, the verification device 33 is preferable because, during the Remote Attestation sequence, it can perform verification of the attestation report, simultaneously with comparing and verifying the first software configuration table (or the hash value of the first software configuration table) and the second software configuration table (or the hash value of the second software configuration table) stored in the verification device 33, as well as verifying the signature.
[0071] <Effects> The software configuration verification system 3 of this embodiment provides resistance to attacks that were problematic in the systems of Embodiments 1 and 2 (Modifications 1 and 2), such as attacks by tampering with the configuration table and replay attacks carried out by reusing old configuration tables.
[0072] It has been known that it is possible to create Attestation Reports for programs and data residing within a TEE. For example, in the case of SEV (Secure Encrypted Virtualization)-SNP (Secure Nested Paging), the attestation report in RA (Remote Attestation) is known to have an area called REPORT_DATA that can store an arbitrary bit sequence.
[0073] In Example 4, based on the apparatus and functional configuration of Example 1, a system is disclosed that generates a hash value of the generated second software configuration table and stores it in a predetermined area of the attestation report (for example, the REPORT_DATA area described above), thereby enabling verification of the validity of this configuration table, including its validity, within the verification process of the attestation report.
[0074] In this embodiment, the verification device can verify the validity of the software configuration included on the launched CVM simply by verifying the attestation report, without verifying the second software configuration table itself.
[0075] Therefore, in this embodiment, the software configuration table verification unit 131 of Embodiment 1, Modification 1, and Embodiment 3 can be replaced with configuration requirements for verifying the attestation report.
[0076] As shown in Figure 11, the software configuration verification system 4 of this embodiment includes an image management device 41 different from that of Embodiment 1, a confidential computing device 42 different from that of Embodiment 1, and a verification device 43 different from that of Embodiment 1.
[0077] The image management device 41 includes the same image file generation unit 111, the same image repository 112, the same first software configuration table generation unit 113, and the same environment startup unit 115 as in Example 1, in addition to a first hash generation unit 411 different from that of Example 1 and a reference value generation unit 412 different from that of Example 1.
[0078] The confidential computing device 42 includes the same isolated execution environment control unit 121 as in Embodiment 1 and a signature assignment unit 423 different from that in Embodiment 1. Within the isolated execution environment, it includes the same second software configuration table generation unit 122 as in Embodiment 1, the same software function unit 123 as in Embodiment 1, an evidence generation unit 421 different from that in Embodiment 1, and a second hash generation unit 422 different from that in Embodiment 1.
[0079] Furthermore, the verification device 43 includes a reference value storage unit 431 that is different from that of Embodiment 1, and an attestation report verification unit 432 that is different from that of Embodiment 1. The operation of the configuration elements that differ from those of Embodiment 1 will be described below with reference to Figure 12.
[0080] <First hash generation unit 411> The first hash generation unit 411 generates a hash value of the first software configuration table (S411).
[0081] <Reference Value Generation Unit 412> The reference value generation unit 412 generates a reference value that includes the hash value of the first software configuration table (correct value) and transmits it to the verification device 43 (S412).
[0082] <Reference Value Storage Unit 431> The reference value storage unit 431 of the verification device 43 receives and stores the reference value (S431).
[0083] <Evidence Generation Unit 421> The evidence generation unit 421 receives a generation command from the environment user 9, etc. (S421a), generates an SBOM generation instruction, and transmits it to the second software configuration table generation unit 122 to generate an attestation report (S421b). The second software configuration table generation unit 122, having received the SBOM generation instruction, generates a second software configuration table based on the software operating in the isolated execution environment, similar to the first embodiment (S122b).
[0084] <Second Hash Generation Unit 422> The second hash generation unit 422 generates a hash value for the second software configuration table and records it in a predetermined area of the attestation report (for example, the REPORT_DATA area described above) (S422).
[0085] <Signature Assignment Unit 423> The signature assignment unit 423 assigns a signature to the attestation report (S423). The second hash generation unit 422 transmits the signed attestation report to the verification device 43 (S423). At this time, the identification ID of the image file is also transmitted to the verification device 43.
[0086] <Attestation Report Verification Unit 432> The attestation report verification unit 432 receives the attestation report and verifies the attestation report based on the reference value (S432). The method of verifying the report shall follow the normal RA (Remote Attestation) procedure.
[0087] Thus, according to the software configuration verification system 4 of this embodiment, the verification process for the validity of the second software configuration table can be absorbed into the report verification function of a normal remote attestation protocol.
[0088] [Devices for using the methods of this disclosure via a network] Devices (terminals) for using the devices, systems, or methods of this disclosure via a network (telecommunication lines) may also be provided. The "devices (terminals) for use" may be equipped with functions necessary to obtain the effects of implementing the devices, systems, or methods of this disclosure (e.g., control functions, decoding functions, restoration functions, input / output functions, etc.).
[0089] [Processors, Programs, Recording Media] The functions realized by the components described herein may be implemented in a circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor includes transistors and other circuits and is considered a circuitry or processing circuitry. A processor may be a programmed processor that executes a program stored in memory.
[0090] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.
[0091] If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.
[0092] The various processes described above can be carried out by loading a program that executes each step of the above method into the recording unit 10020 of the computer 10000 shown in Figure 13, and then causing the control unit 10010, input unit 10030, output unit 10040, display unit 10050, etc. to operate.
[0093] The program describing this process can be recorded on a computer-readable recording medium. Any computer-readable recording medium can be used, such as a magnetic recording device, optical disc, magneto-optical recording medium, or semiconductor memory.
[0094] A program describing this process may be included in a computer program product.
[0095] Furthermore, this program may be distributed, for example, by selling, transferring, or lending portable recording media such as DVDs or CD-ROMs on which the program is recorded. Alternatively, the program may be stored in the storage device of a server computer and distributed by transferring the program from the server computer to other computers via a network.
[0096] A computer executing such a program may, for example, first store the program recorded on a portable storage medium or a program transferred from a server computer in its own storage device. Then, when processing is to be executed, the computer reads the program stored on its own storage medium and executes the processing according to the read program. Alternatively, the computer may directly read the program from the portable storage medium and execute the processing according to that program, or it may sequentially execute the processing according to the received program each time a program is transferred to it from a server computer. Furthermore, the processing may be executed using a so-called ASP (Application Service Provider) type service, where the processing function is realized only by issuing execution instructions and obtaining results, without transferring the program from the server computer to this computer.In addition, the processing may be executed using a so-called SaaS (Software as a Service) type service, where a part of the server computer is made available to the user along with the program. Furthermore, the term "program" in this form includes information used for processing by an electronic computer that is equivalent to a program (data, etc., that is not a direct instruction to the computer but has the property of defining the processing of the computer).
[0097] Furthermore, in this configuration, the device is configured by executing a predetermined program on a computer, but at least a part of these processes may be implemented in hardware.
Claims
1. A software configuration verification system including an image management device, a confidential computing device, and a verification device, wherein the image management device includes an image file generation unit that generates an image file, a first software configuration table generation unit that generates a first software configuration table with correct values from the image file, and an environment startup unit that transmits a startup instruction including the image file to the confidential computing device, the confidential computing device includes an isolated execution environment control unit that starts an isolated execution environment based on the startup instruction, and a second software configuration table generation unit that generates a second software configuration table based on software operating in the isolated execution environment and transmits it to the verification device, and the verification device includes a software configuration table verification unit that receives the first software configuration table and verifies the second software configuration table.
2. A software configuration verification system according to claim 1, wherein the second software configuration table generation unit receives the first software configuration table from the image management device, identifies a group of software configurations to be measured from the first software configuration table, and generates the second software configuration table.
3. A software configuration verification system including an image management device and a confidential computing device, wherein the image management device includes an image file generation unit that generates an image file, a first software configuration table generation unit that generates a first software configuration table with correct values from the image file, and an environment startup unit that transmits a startup instruction including the image file to the confidential computing device, and the confidential computing device includes an isolated execution environment control unit that starts an isolated execution environment based on the startup instruction, a second software configuration table generation unit that generates a second software configuration table based on software operating in the isolated execution environment, and a software configuration table verification unit that receives the first software configuration table and verifies the second software configuration table.
4. A software configuration verification system according to claim 1, wherein the confidential computing device includes a signature granting unit that grants a signature to the second software configuration table, and the verification device includes a signature verification unit that verifies the signature granted to the second software configuration table.
5. A software configuration verification system including an image management device, a confidential computing device, and a verification device, wherein the image management device includes an image file generation unit that generates an image file, a first software configuration table generation unit that generates a first software configuration table which is the correct value from the image file, a first hash generation unit that generates a hash value of the first software configuration table, a reference value generation unit that generates a reference value including the hash value of the first software configuration table and transmits it to the verification device, and an environment startup unit that transmits a startup instruction including the image file to the confidential computing device, the confidential computing device includes an isolated execution environment control unit that starts an isolated execution environment based on the startup instruction, an evidence generation unit that generates an attestation report, a second software configuration table generation unit that generates a second software configuration table based on software operating in the isolated execution environment, and a second hash generation unit that generates a hash value of the second software configuration table and records it in a predetermined area of the attestation report, and the verification device includes an attestation report verification unit that receives the attestation report and verifies the attestation report based on the reference value.
6. A confidential computing device in a software configuration verification system including an image management device, a confidential computing device, and a verification device, wherein the confidential computing device includes: a first software configuration table transmitted from the image management device to the verification device; an isolated execution environment control unit which, upon receiving a startup instruction that includes an image file corresponding to the first software configuration table and generated by the image management device, starts an isolated execution environment based on the startup instruction; and a second software configuration table generation unit which generates a second software configuration table based on software operating in the isolated execution environment and transmits it to the verification device.
7. A software configuration verification method performed by an image management device, a confidential computing device, and a verification device, wherein the image management device performs the steps of: generating an image file; generating a first software configuration table with correct values from the image file; and transmitting a startup instruction including the image file to the confidential computing device; the confidential computing device performs the steps of: starting an isolated execution environment based on the startup instruction; generating a second software configuration table based on the software operating in the isolated execution environment and transmitting it to the verification device; and the verification device performs the steps of: receiving the first software configuration table and verifying the second software configuration table.
8. A program that causes a computer to execute the software configuration verification method described in claim 7.
