Installation control device, installation control method, information processing device, installation control system and program

Abstract

Provided are an installation control device and the like that can reduce not only the risk due to tampering with software, but also the risk due to vulnerabilities in software that has not been tampered with. An installation control device 40 according to an embodiment of the present disclosure is provided with: a certification reception unit 420 that receives verification certification data including first authenticity information of target software and indicating that the safety of the target software has been verified; a comparison unit 430 that compares the first authenticity information included in the verification certification data with second authenticity information of the target software; and a control unit 440 that performs control such that the target software is installed if the first authenticity information is the same as the second authenticity information.

Description

[Technical Field]

[0001] The present disclosure relates to techniques for controlling the installation of software. [Background technology]

[0002] Generally, to prevent the use of tampered software, data called a certificate of authenticity is used to prove that the software is genuine. For example, the hash value of the software being installed is compared with the hash value of that software contained in the software's authenticity information. If the hash value of the software being installed matches the hash value of that software contained in the software's authenticity information, the software is installed. This mechanism reduces the risk of installing an unauthorized backdoor through software tampering.

[0003] Patent Document 1 describes an information processing device that calculates a hash value that can uniquely identify a platform that provides an operating environment for an application and compares the calculated hash value with the hash value of a platform whose reliability is assured. If the information processing device in Patent Document 1 determines that the two hash values ​​do not match, it restricts the use of a main unit that has the platform from which the hash value was generated.

[0004] Patent Documents 2 and 3 describe information processing devices that authenticate update files using update software, a value uniquely calculated from the update software, and a digital signature of the update software.

[0005] Patent document 4 describes a game management device that determines the consistency between a genuine game program stored in a genuine read-only memory that is the basis for certification by a third party and a current game program stored in a current read-only memory. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-008641 [Patent Document 2] Japanese Patent Application Laid-Open No. 2012-150834 [Patent Document 3] Japanese Patent Application Laid-Open No. 2013-254506 [Patent Document 4] Japanese Patent Application Publication No. 10-052549 Summary of the Invention [Problem to be solved by the invention]

[0007] The technologies disclosed in Patent Documents 1 to 3 are technologies that determine whether software has been tampered with by comparing hash values. The technology disclosed in Patent Document 4 is a technology that determines whether software has been tampered with by comparing programs. The technologies disclosed in Patent Documents 1 to 4 cannot reduce the risk that malicious software manufacturers will embed vulnerabilities such as backdoors in the software provided.

[0008] One of the purposes of the present disclosure is to provide an installation control device and the like that can reduce not only the risks due to software tampering but also the risks due to vulnerabilities in software that has not been tampered with. [Means for solving the problem]

[0009] An installation control device according to one embodiment of the present disclosure includes a certification receiving means for receiving verified certification data including first authenticity information of a target software and indicating that the safety of the target software has been verified, a comparison means for comparing the first authenticity information included in the verified certification data with second authenticity information of the target software, and a control means for controlling installation of the target software to be performed if the first authenticity information and the second authenticity information are the same.

[0010] An installation control method according to one embodiment of the present disclosure receives verified certification data that includes first authenticity information for target software and indicates that the safety of the target software has been verified, compares the first authenticity information included in the verified certification data with second authenticity information for the target software, and performs control such that installation of the target software is executed if the first authenticity information and the second authenticity information are the same.

[0011] A storage medium according to one embodiment of the present disclosure stores a program that causes a computer to execute the following steps: a certification receiving process that receives verified certification data, including first authenticity information for target software, indicating that the safety of the target software has been verified; a comparison process that compares the first authenticity information included in the verified certification data with second authenticity information for the target software; and a control process that controls installation of the target software to be performed if the first authenticity information and the second authenticity information are the same.

[0012] A shared system according to one embodiment of the present disclosure includes a certification receiving means for receiving verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; and a notification means for receiving the verified certification data, comparing the first authenticity information included in the verified certification data with second authenticity information of the target software, and notifying an installation control device, which controls the installation of the target software to be executed if the first authenticity information and the second authenticity information are the same, of the verified certification data.

[0013] A sharing method according to one embodiment of the present disclosure includes receiving verified certification data that includes first authenticity information for target software and indicates that the safety of the target software has been verified, receiving the verified certification data, comparing the first authenticity information included in the verified certification data with second authenticity information for the target software, and notifying an installation control device that controls installation of the target software to be performed if the first authenticity information and the second authenticity information are the same.

[0014] A storage medium according to one embodiment of the present disclosure stores a program that causes a computer to execute a certification receiving process that receives inspected certification data, including first authenticity information for the target software and indicating that the safety of the target software has been inspected, and a notification process that receives the inspected certification data, compares the first authenticity information contained in the inspected certification data with second authenticity information for the target software, and, if the first authenticity information and the second authenticity information are the same, notifies an installation control device that controls the installation of the target software to be executed of the inspected certification data.

[0015] One aspect of the present disclosure is also realized by a program stored in the above-mentioned storage medium. [Effects of the Invention]

[0016] The present disclosure has the effect of reducing not only the risk due to software tampering but also the risk due to vulnerabilities in software that has not been tampered with. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a block diagram illustrating an example of the configuration of an installation control device according to a first embodiment of the present disclosure. [Figure 2] FIG. 2 is a flowchart illustrating an example of the operation of the installation control device according to the first embodiment of the present disclosure. [Figure 3]FIG. 3 is a block diagram illustrating an example of the configuration of a shared system according to the second embodiment of the present disclosure. [Figure 4] FIG. 4 is a flowchart illustrating an example of the operation of the sharing system according to the second embodiment of the present disclosure. [Figure 5] FIG. 5 is a block diagram illustrating an example of the configuration of a shared system according to the third embodiment of the present disclosure. [Figure 6] FIG. 6 is a flowchart illustrating an example of the operation of the sharing system according to the third embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart illustrating an example of the operation of the sharing system according to the third embodiment of the present disclosure. [Figure 8] FIG. 8 is a block diagram illustrating an example of the configuration of information processing according to the fourth embodiment of the present disclosure. [Figure 9] FIG. 9 is a flowchart illustrating an example of the operation of the information processing device according to the fourth embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating an example of a hardware configuration of a computer that can realize the shared system, the information processing device, and the installation control device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0019] First Embodiment First, an installation control device according to a first embodiment of the present disclosure will be described in detail with reference to the drawings.

[0020] <Configuration> FIG. 1 is a block diagram illustrating an example of the configuration of an installation control device according to a first embodiment of the present disclosure. In the example illustrated in FIG. 1, the installation control device 40 of this embodiment includes a certificate receiving unit 420, a comparison unit 430, and a control unit 440. The certificate receiving unit 420 receives verified certificate data that includes first authenticity information for the target software and indicates that the safety of the target software has been verified. The comparison unit 430 compares the first authenticity information included in the verified certificate data with second authenticity information for the target software. The control unit 440 controls installation of the target software when the first authenticity information and the second authenticity information are the same. In this embodiment, the target software and the second authenticity information for the target software are acquired in advance.

[0021] <Certification Receiving Department 420> The proof receiving unit 420 receives the inspected proof data of the target software, for example, from a shared system or the like described below. The proof receiving unit 420 may send a request for the inspected proof data of the target software to the shared system or the like, and receive the inspected proof data of the target software sent from the shared system or the like in response to the sent request. In this case, the request sent by the proof receiving unit 420 may include identification information that uniquely identifies the target software. The shared system or the like may hold the inspected proof data of the target software associated with the identification information of the target software.

[0022] The target software is software that is about to be installed. The authenticity information of the target software (each of the first authenticity information and the second authenticity information) is data that proves that the target software is authentic, i.e., that the target software has been provided by the provider of the target software and has not been tampered with. The authenticity information of the target software may be, for example, data generated by encrypting data including a hash value of the target software file with the private key of the provider of the target software.

[0023] The inspected certification data is data that certifies that the inspected certification data was generated by an inspection agency, that the inspected target software is authentic, and the results of the inspection of the target software conducted by the inspection agency. The inspected certification data is data generated, for example, by encrypting data including the authenticity information of the target software provided to the inspection agency (i.e., the above-mentioned first authenticity information) and the results of the inspection using the inspection agency's private key.

[0024] The inspection may include, for example, a vulnerability inspection and a backdoor inspection. The inspection result may include, for example, a combination of information indicating the inspection performed and information indicating the result of the inspection performed. Specifically, the inspection result may include, for example, a combination of information indicating the vulnerability inspection performed and information on vulnerabilities detected by the vulnerability inspection. The inspection result may include a combination of information indicating the type of backdoor inspection performed and information on the detected backdoor. The information on the detected vulnerability may include, for example, a combination of a severity indicating the degree of seriousness of the detected vulnerability and information on the content of the detected vulnerability. If no vulnerability is detected, the information on the detected vulnerability may be predetermined information indicating that no vulnerability was detected. The information on the detected backdoor may include information indicating the type of backdoor detected. If no backdoor is detected by the backdoor inspection, the information on the detected backdoor may be information indicating that no backdoor was detected.

[0025] The fact that the safety of the target software has been inspected may be indicated, for example, by the inspection certification data indicating that no vulnerabilities of a severity greater than a predetermined severity were detected and no backdoors were detected.

[0026] <Comparator 430> The comparison unit 430 compares first authenticity information, which is authenticity information for the target software included in the verified certification data, with second authenticity information, which is previously obtained authenticity information for the target software. The second authenticity information indicates authenticity information provided along with the target software being installed. The comparison unit 430, for example, acquires a public key of an inspection organization and decrypts the verified certification data using the acquired public key. The comparison unit 430 extracts the first authenticity information encrypted with the private key of the manufacturer of the target software from the decrypted verified certification data. The comparison unit 430 may acquire the public key of the manufacturer of the target software and decrypt the extracted first authenticity information encrypted with the private key of the manufacturer of the target software using the acquired public key of the manufacturer of the target software. Furthermore, the comparison unit 430 may decrypt the second authenticity information encrypted with the private key of the manufacturer of the target software using the acquired public key of the manufacturer of the target software. Then, the comparison unit 430 may compare the decrypted first authenticity information with the decrypted second authenticity information.

[0027] <Control unit 440> If the comparison shows that the first authenticity information and the second authenticity information are the same, the control unit 440 performs control so that the target software is installed. The control unit 440 may, for example, permit the activation of an installer for the target software. If the first authenticity information and the second authenticity information are not the same, the control unit 440 performs control so that the target software is not installed. The control unit 440 may, for example, prohibit the activation of an installer for the target software.

[0028] If the inspection results included in the inspection proof data indicate that the target software is not safe, the control unit 440 may control the target software not to be installed. For example, if the inspection results indicate that the detected vulnerabilities include vulnerabilities with a severity level equal to or greater than a predetermined level, the control unit 440 may determine that the target software is not safe. For example, if the inspection results indicate that a backdoor has been detected, the control unit 440 may determine that the target software is not safe.

[0029] Furthermore, if the inspection proof data for the target software cannot be obtained, the control unit 440 may control the target software not to be installed. For example, if, in response to a request for inspection proof data for the target software, the control unit 440 receives a response from the above-mentioned shared system or the like indicating that inspection proof data for the target software does not exist, the control unit 440 may determine that the inspection proof data for the target software has not been obtained. For example, if the requested inspection proof data for the target software is not sent from the above-mentioned shared system or the like within a predetermined time after sending the request for inspection proof data for the target software, the control unit 440 may determine that the inspection proof data for the target software has not been obtained.

[0030] The control unit 440 may permit installation of the target software by, for example, transmitting information permitting installation of the target software to the information processing device attempting to perform the installation. The control unit 440 may prohibit installation of the target software by, for example, transmitting information prohibiting installation of the target software to the information processing device attempting to perform the installation.

[0031] <Operation> FIG. 2 is a flowchart illustrating an example of the operation of the installation control device according to the first embodiment of the present disclosure. When the operation illustrated in FIG. 2 is started, the second authenticity information of the target software has been obtained. In the example illustrated in FIG. 2, first, the certification receiving unit 420 receives verified certification data of the target software from a shared system or the like (step S21). Next, the comparing unit 430 compares the first authenticity information included in the verified certification data with the second authenticity information of the target software (step S22). If the first authenticity information and the second authenticity information are the same (YES in step S23), the control unit 440 controls the target software to be installed (step S24). If the first authenticity information and the second authenticity information are not the same (NO in step S23), the control unit 440 controls the target software not to be installed (step S25).

[0032] <Effects> This embodiment has the advantage of reducing not only the risk of software tampering but also the risk of vulnerabilities in untampered software. This is because the proof receiving unit 420 receives inspected proof data for the target software, which indicates that the target software is safe as a result of the inspection and that the inspection was performed on authentic target software. The inspected proof data indicates that the untampered target software is free of vulnerabilities. Note that backdoors can also be considered a type of vulnerability. The control unit 440 then controls the target software to be installed if the first authenticity information included in the inspected proof data and the second authenticity information for the target software are the same. If the first authenticity information and the second authenticity information are the same, the target software to be installed is the same as the target software that has been shown to be safe by the inspected proof data. In this case, the target software to be installed can be considered not to have been tampered with.

[0033] <Second embodiment> <Configuration> 3 is a block diagram illustrating an example of the configuration of a shared system according to the second embodiment of the present disclosure. In the example illustrated in FIG. 3, the shared system 10 according to the second embodiment of the present disclosure includes a certificate receiving unit 130 and a notification unit 140.

[0034] <Certification Receiving Unit 130> The certification receiving unit 130 receives verified certification data that includes first authenticity information of the target software and indicates that the safety of the target software has been verified.

[0035] The target software of this embodiment is the same as the target software of the first embodiment. The inspected proof data of this embodiment is the same as the inspected proof data of the first embodiment. The authenticity information of this embodiment (i.e., the first authenticity information and the second authenticity information) is the same as the authenticity information of this embodiment. That is, the first authenticity information and the second authenticity information of this embodiment are the same as the first authenticity information and the second authenticity information of the first embodiment, respectively.

[0036] The certification receiving unit 130 may obtain the certified data from a certification device that performs a certification of the target software and generates the certified data that certifies the results of the certification. The certification device may be an information processing device or the like managed by the certification organization that performs the certification.

[0037] <Notification section 140> The notification unit 140 notifies the installation control device of the verified certification data. The installation control device receives the verified certification data. The installation control device compares the first authenticity information included in the verified certification data with the second authenticity information of the target software. If the first authenticity information and the second authenticity information are the same, the installation control device controls the installation of the target software to be performed.

[0038] The installation control device of this embodiment may be the installation control device 40 of the first embodiment. The installation control device of this embodiment may be the installation control device 400 of an embodiment described later.

[0039] <Operation> 4 is a flowchart illustrating an example of the operation of the shared system according to the second embodiment of the present disclosure. In the example illustrated in FIG. 4, the certificate receiving unit 130 receives the inspected certificate data of the target software from, for example, an inspection device that generates the inspected certificate data (step S21). Then, the notification unit 140 notifies the installation control device of the received inspected certificate data (step S22).

[0040] <Effects> This embodiment has the same effects as the first embodiment. This is because the notification unit 140 notifies the installation control device of the inspection proof data. The installation control device then receives the inspection proof data for the target software, which indicates that the target software is safe as a result of the inspection and that the inspection was performed on authentic target software. The inspection proof data indicates that the untampered target software has no vulnerabilities. Note that backdoors can also be considered a type of vulnerability. Furthermore, this is because the installation control device controls the target software to be installed if the first authenticity information included in the inspection proof data is the same as the second authenticity information for the target software. If the first authenticity information and the second authenticity information are the same, the target software to be installed is the same as the target software that has been shown to be safe by the inspection proof data. In this case, the target software to be installed can be considered not to have been tampered with.

[0041] <Third embodiment> <Configuration> FIG. 5 is a block diagram illustrating an example of the configuration of a shared system according to a third embodiment of the present disclosure. In the example illustrated in FIG. 5, the shared system 100 of this embodiment includes a software reception unit 110, a software provision unit 120, a certificate receiving unit 130, a notification unit 140, and an information storage unit 150. The shared system 100 is communicatively connected to each of a software provision device 200, an inspection device 300, an installation control device 400, and an information processing device 500 including the installation control device 400. The certificate receiving unit 130 and the notification unit 140 of this embodiment have functions similar to those of the certificate receiving unit 130 and the notification unit 140 of the second embodiment, respectively. The certificate receiving unit 130 and the notification unit 140 of this embodiment operate similarly to those of the certificate receiving unit 130 and the notification unit 140 of the second embodiment, respectively.

[0042] <Software providing device 200> The software providing device 200 provides the target software and authenticity information of the target software to the software receiving unit 110 of the shared system 100. The software providing device 200 is an information processing device managed by the provider of the target software. The provided target software is data necessary for installing the target software. The target software may be provided in the form of, for example, a single file. The authenticity information of the target software is data proving that the target software was provided by the provider of the target software and has not been tampered with. The authenticity information of the target software may be data generated by encrypting a hash value of the target software file using a private key of the provider of the target software. The software providing device 200 may generate identification information that uniquely identifies the target software and associate the generated identification information with the target software and the authenticity information of the target software. The software providing device 200 may provide the target software and the authenticity information of the target software, with which the identification information is associated, to the software receiving unit 110 of the shared system 100, together with the identification information. The identification information of the target software may be included in the data of the target software.

[0043] As will be described later, the target software and authenticity information of the target software provided from the software providing device 200 to the software receiving unit 110 are provided to the inspection device 300 by the software providing unit 120. In the description of the embodiments of the present disclosure, the authenticity information provided to the inspection device 300 is referred to as first authenticity information.

[0044] Furthermore, the software providing device 200 provides the target software, authenticity information and identification information of the target software to the information processing device 500 via a medium such as a communication network or a storage medium. In the description of the embodiments of the present disclosure, the authenticity information provided to the information processing device 500 together with the target software from the software providing device 200 is referred to as second authenticity information.

[0045] <Inspection device 300> The inspection device 300 receives the target software and authenticity information of the target software from the software providing unit 120 of the shared system 100. The inspection device 300 is, for example, a device that performs the above-mentioned inspection. The inspection device 300 is, for example, an information processing device managed by an inspection organization (hereinafter simply referred to as an inspection organization) that performs the inspection. The inspection device 300 verifies the authenticity of the target software using the received authenticity information. In other words, the inspection device 300 uses the received authenticity information to verify that the target software received from the software providing unit 120 was provided by the provider of the target software and has not been tampered with. If the authenticity information is data generated by encrypting a hash value of the target software file using the private key of the provider of the target software, the inspection device 300 acquires the public key of the provider of the target software. Then, the inspection device 300 verifies the authenticity of the target software using the received authenticity information and the acquired public key of the provider of the target software. The method for acquiring the public key of the provider of the target software and the method for verifying the authenticity of the target software using the received authenticity information and the acquired public key of the provider of the target software may be any existing method. If the authenticity of the target software cannot be verified, the inspection device 300 does not need to inspect the target software.

[0046] Then, the inspection device 300 inspects the target software. Specifically, the inspection device 300 inspects the target software for vulnerabilities, backdoors, etc. The inspection device 300 generates the above-mentioned inspected proof data that represents the results of the inspection.

[0047] The checking device 300 transmits the generated checked proof data to the proof receiving unit 130 of the shared system 100 .

[0048] <Information processing device 500> The information processing device 500 includes an installation control device 400, which will be described later. The information processing device 500 acquires the target software and the second authenticity information of the target software from the software providing device 200 via a medium such as a communications network or a storage medium, as described above. Before installing the acquired target software, the information processing device 500 provides the acquired second authenticity information to the installation control device 400.

[0049] Furthermore, the information processing device 500 is notified (in other words, receives) the first authenticity information of the target software from the notification unit 140 of the shared system 100. The installation control device 400 may request the authenticity information of the target software from the shared system 100 via the information processing device 500. Then, the installation control device 400 may receive the authenticity information of the target software as the first authenticity information from the shared system 100 via the information processing device 500. At this time, the information processing device 500 receives the first authenticity information from the shared system 100 and provides the received first authenticity information to the installation control device 400.

[0050] Then, the information processing device 500 installs the target software under the control of the installation control device 400. Specifically, the information processing device 500 installs the target software when information permitting installation is output from the installation control device 400. The information processing device 500 does not install the target software when information prohibiting installation is output from the installation control device 400.

[0051] <Installation control device 400> The installation control device 400 receives the second authenticity information provided to the information processing device 500 from the software providing device 200. The installation control device 400 further receives the first authenticity information notified by the notifying unit 140.

[0052] The installation control device 400 compares the first authenticity information included in the verified proof data with the second authenticity information of the target software. If the first authenticity information and the second authenticity information are the same, the installation control device 400 controls the installation of the target software to be executed.

[0053] Before launching the installer for the target software, the information processing device 500 may send a request for the inspected proof data of the target software to the shared system 100. The request for the inspected proof data of the target software may include identification information of the target software. The notification unit 140 of the shared system 100 receives the request for the inspected proof data of the target software. The notification unit 140 identifies the requested inspected proof data using the identification information of the target software included in the request. The notification unit 140 then transmits the identified inspected proof data to the information processing device 500. The information processing device 500 receives the inspected proof data of the target software from the notification unit 140 of the shared system 100, and provides the received inspected proof data to the installation control device 400.

[0054] The information processing device 500 is realized, for example, as a computer (for example, a personal computer, a portable terminal device such as a smartphone, or another computer) that includes a memory and a processor that executes a program loaded into the memory. The installation control device 400 is realized by the memory of the information processing device 500 and the processor of the information processing device 500 that executes a program that is loaded into the memory of the information processing device 500 and controls execution of the installer for the target software.

[0055] The installation control device 400 and the information processing device 500 will be described in detail later as a fourth embodiment.

[0056] <Shared System 100> <Software Reception Unit 110> The software reception unit 110 receives the target software and authenticity information of the target software from the software provision device 200. The software reception unit 110 stores the target software and the authenticity information of the target software in the information storage unit 150 from the software provision device 200. More specifically, the software reception unit 110 receives the target software, the authenticity information of the target software, and identification information of the target software from the software provision device 200. The identification information of the target software is associated with the target software and the authenticity information of the target software. The software reception unit 110 stores the target software, the authenticity information of the target software, and the identification information of the target software in the information storage unit 150 from the software provision device 200.

[0057] <Software Providing Department 120> The software providing unit 120 provides (in other words, transmits) the target software and authenticity information of the target software stored in the information storage unit 150 to the inspection device 300. As described above, the authenticity information provided by the software providing device 200 to the inspection device 300 is referred to as first authenticity information. The software providing unit 120 may provide identification information of the target software to the inspection device 300 together with the target software and the authenticity information of the target software.

[0058] The software providing unit 120 may further provide the target software and authenticity information of the target software stored in the information storage unit 150 to the information processing device 500. As described above, the authenticity information provided to the information processing device 500 together with the target software is referred to as second authenticity information. The authenticity information provided to the information processing device 500 by the software providing unit 120 corresponds to the second authenticity information.

[0059] <Certification Receiving Unit 130> The certificate receiving unit 130 receives the above-mentioned inspected certificate data from the inspection device 300. The certificate receiving unit 130 stores the received inspected certificate data in the information storage unit 150. Specifically, the certificate receiving unit 130 receives the inspected certificate data of the target software associated with the identification information of the target software from the inspection device 300. The certificate receiving unit 130 stores the inspected certificate data of the target software associated with the identification information of the target software in the information storage unit 150.

[0060] <Notification section 140> The notification unit 140 reads the inspection proof data of the target software from the information storage unit 150, and notifies (i.e., transmits) the read inspection proof data to the information processing device 500. The information processing device 500 receives the inspection proof data and provides the received inspection proof data to the installation control device 400. In other words, the notification unit 140 reads the inspection proof data of the target software from the information storage unit 150, and notifies (i.e., transmits) the read inspection proof data to the installation control device 400.

[0061] As described above, the installation control device 400 or the information processing device 500 may request the inspection certification data of the target software to be installed from the shared system 100 (specifically, the notification unit 140). In other words, the information processing device 500 may receive the request for the inspection certification data of the target software to be installed output by the installation control device 400. The information processing device 500 may transmit the request for the inspection certification data of the target software to be installed received from the installation control device 400 to the shared system 100 (specifically, the notification unit 140). The request for the inspection certification data of the target software may include identification information of the target software. The notification unit 140 uses the identification information of the target software included in the request to read the requested inspection certification data from the information storage unit 150 from the inspection certification data stored in the information storage unit 150. Specifically, the notification unit 140 reads the inspection certification data associated with the identification information of the target software included in the request from the information storage unit 150. The notification unit 140 transmits the read-out checked certification data, that is, the requested checked certification data, to the information processing device 500 (specifically, the installation control device 400 included in the information processing device 500).

[0062] The information processing device 500 receives the verified certification data notified (i.e., transmitted) from the notification unit 140, and provides the received verified certification data to the installation control device 400. The installation control device 400 receives the verified certification data. Upon receiving the verified certification data, the installation control device 400 operates as described above. Upon receiving the verified certification data, the installation control device 400 may operate in the same manner as the installation control device 400 of the first embodiment. Upon receiving the verified certification data, the installation control device 400 may operate in the same manner as the installation control device 400 of the second embodiment. Upon receiving the verified certification data, the installation control device 400 may operate in the same manner as the installation control device 400 of the fourth embodiment, which will be described later.

[0063] <Operation> Next, the operation of the shared system 100 according to the third embodiment of the present disclosure will be described in detail with reference to the drawings.

[0064] FIG. 6 is a flowchart illustrating an example of the operation of the shared system according to the third embodiment of the present disclosure. FIG. 6 illustrates an example of the operation of the shared system 100 according to this embodiment, in which the shared system 100 receives the target software and the verified proof data. In the example illustrated in FIG. 6, in step S101, the software reception unit 110 receives the target software and the authenticity information from the software provision device 200. In the example of FIG. 6, the authenticity information received in step S101 is provided to the verification device 300, and therefore the authenticity information received in step S101 corresponds to the first authenticity information. In other words, the software reception unit 110 receives the target software and the first authenticity information from the software provision device 200 (step S101). The software reception unit 110 stores the received target software and the first authenticity information in the information storage unit 150. In other words, the information storage unit 150 stores the target software and the first authenticity information (step S102).

[0065] Next, the software providing unit 120 provides the target software and the first authenticity information to the inspection device 300 (step S103). The inspection device 300 inspects the received target software. The inspection device 300 generates inspected proof data including the inspection results and the first authenticity information. The inspection device 300 transmits the generated inspected proof data to the proof receiving unit 130 of the shared system 100. The proof receiving unit 130 receives the inspected proof data from the inspection device 300 (step S104). The proof receiving unit 130 stores the received inspected proof data in the information storage unit 150. The information storage unit 150 stores the inspected proof data received by the proof receiving unit 130 (step S105).

[0066] Fig. 7 is a flowchart illustrating an example of the operation of the shared system according to the third embodiment of the present disclosure. Fig. 7 illustrates an example of the operation of the shared system 100 according to this embodiment to notify checked proof data. In the example illustrated in Fig. 7, the notification unit 140 receives a request for checked proof data of the target software from the installation control device 400 (step S111). The notification unit 140 reads the requested checked proof data from the information storage unit 150 (step S112). The notification unit 140 notifies the installation control device 400 that sent the request of the read checked proof data, i.e., the requested checked proof data (step S113).

[0067] <Effects> The present embodiment described above has the same effects as the second embodiment, for the same reasons as those for which the effects of the second embodiment are obtained.

[0068] <Fourth embodiment> Next, a fourth embodiment of the present disclosure will be described in detail with reference to the drawings. An information processing device 500 according to this embodiment corresponds to the information processing device 500 of the third embodiment. The information processing device 500 according to this embodiment represents a specific example of the information processing device 500 of the third embodiment. An installation control device 400 included in the information processing device 500 according to this embodiment corresponds to the installation control device 400 of the third embodiment. The installation control device 400 included in the information processing device 500 according to this embodiment represents a specific example of the installation control device 400 of the third embodiment.

[0069] <Configuration> FIG. 8 is a block diagram illustrating an example of the configuration of an information processing device according to a fourth embodiment of the present disclosure. In the example illustrated in FIG. 8, an information processing device 500 includes an installation control device 400, a software acquisition unit 510, an execution unit 520, and a certificate acquisition unit 530. The installation control device 400 includes an authenticity information acquisition unit 410, a certificate receiving unit 420, a comparison unit 430, and a control unit 440. The certificate receiving unit 420, the comparison unit 430, and the control unit 440 of this embodiment have the same functions as the certificate receiving unit 420, the comparison unit 430, and the control unit 440 of the first embodiment, respectively. Furthermore, the certificate receiving unit 420, the comparison unit 430, and the control unit 440 of this embodiment perform the same operations as the certificate receiving unit 420, the comparison unit 430, and the control unit 440 of the first embodiment, respectively.

[0070] <Software Acquisition Unit 510> The software acquisition unit 510 acquires the target software and authenticity information of the target software from the software providing device 200, for example, via a communication network or a storage medium. The authenticity information acquired by the software acquisition unit 510 is the second authenticity information described above.

[0071] The software acquisition unit 510 sends the acquired target software to the execution unit 520. The software acquisition unit 510 sends the acquired second authenticity information to the installation control device 400 (specifically, to the authenticity information acquisition unit 410 of the installation control device 400).

[0072] <Executive Department 520> The execution unit 520 receives the target software from the software acquisition unit 510 .

[0073] When the user of the information processing device 500 instructs the installation of the target software, the execution unit 520 executes the installation of the target software under the control of the installation control device 400 (specifically, the control unit 440 of the installation control device 400). The user of the information processing device 500 may instruct the installation of the target software using an input device of the information processing device 500, such as a touch panel, a keyboard, or a mouse.

[0074] Specifically, when a user of the information processing device 500 instructs installation of the target software, the execution unit 520 inquires, for example, of the installation control device 400 (specifically, for example, the certificate receiving unit 420) as to whether or not the target software can be installed. In other words, the execution unit 520 sends a request for information indicating whether or not the target software can be installed to the installation control device 400 (specifically, for example, the certificate receiving unit 420). In response to the request for information indicating whether or not the target software can be installed, the execution unit 520 receives information permitting installation or information prohibiting installation from the control unit 440 of the installation control device 400. If the installation control device 400 outputs information permitting installation, the execution unit 520 installs the target software. If the installation control device 400 outputs information prohibiting installation, the execution unit 520 does not install the target software.

[0075] <Certification Acquisition Department 530> The certification acquisition unit 530 receives the verified certification data of the target software from the shared system 100 (specifically, the notification unit 140 of the shared system 100).

[0076] Specifically, for example, the proof acquisition unit 530 receives a request for inspected proof data of the target software from the proof receiving unit 420 of the installation control device 400. Upon receiving the request for inspected proof data of the target software from the proof receiving unit 420, the proof acquisition unit 530 transmits the request for inspected proof data of the target software to the notification unit 140 of the shared system 100. The proof acquisition unit 530 receives the inspected proof data of the target software from the notification unit 140 of the shared system 100. The proof acquisition unit 530 sends the inspected proof data of the target software received from the notification unit 140 of the shared system 100 to the proof receiving unit 420 of the installation control device 400.

[0077] <Authenticity information acquisition unit 410> The authenticity information acquisition unit 410 receives the second authenticity information of the target software from the software acquisition unit 510. Upon receiving the second authenticity information of the target software from the software acquisition unit 510, the authenticity information acquisition unit 410 may send information indicating that the second authenticity information has been received to the certificate receiving unit 420. The authenticity information acquisition unit 410 sends the second authenticity information of the target software received from the software acquisition unit 510 to the comparison unit 430.

[0078] <Certification Receiving Department 420> The certificate receiving unit 420 receives a request for information indicating whether the target software can be installed from the execution unit 520. When the certificate receiving unit 420 receives a request for information indicating whether the target software can be installed from the execution unit 520, it transmits a request for inspected proof data for the target software to the notification unit 140 of the shared system 100 via the certificate acquisition unit 530. Specifically, the certificate receiving unit 420 sends the request for inspected proof data for the target software to the certificate acquisition unit 530. The certificate acquisition unit 530 receives the request for inspected proof data for the target software from the certificate receiving unit 420. When the certificate acquisition unit 530 receives the request for inspected proof data for the target software from the certificate receiving unit 420, it transmits the received request for inspected proof data for the target software to the notification unit 140 of the shared system 100.

[0079] In response to a request for inspected proof data of the target software, the proof receiving unit 420 receives the inspected proof data sent from the notification unit 140 of the shared system 100 via the proof acquisition unit 530. Specifically, the proof acquisition unit 530 receives the inspected proof data of the target software from the notification unit 140 of the shared system 100. Then, the proof receiving unit 420 receives the inspected proof data of the target software from the proof acquisition unit 530.

[0080] The proof receiving unit 420 sends the received inspected proof data of the target software to the comparing unit 430. For example, if the proof receiving unit 420 does not receive the inspected proof data of the target software within a predetermined time after sending a request for the inspected proof data of the target software, the proof receiving unit 420 may send information indicating that the inspected proof data does not exist to the comparing unit 430. For example, if the proof receiving unit 420 receives information indicating that the inspected proof data of the target software does not exist from the notifying unit 140 of the shared system 10, the proof receiving unit 420 may send information indicating that the inspected proof data does not exist to the comparing unit 430.

[0081] <Comparator 430> The comparison unit 430 receives verified proof data of the target software from the proof receiving unit 420. As described above, the verified proof data of the target software includes first authenticity information of the target software. The comparison unit 430 receives second authenticity information of the target software from the authenticity information acquisition unit 410.

[0082] The comparison unit 430 compares the first authenticity information of the target software included in the verified certification data of the target software with the received second authenticity information of the target software.

[0083] In this case, the comparison unit 430 may, for example, obtain a public key of the inspection organization and decrypt the inspected proof data using the obtained public key. The comparison unit 430 may extract first authenticity information encrypted with the private key of the manufacturer of the target software from the decrypted inspected proof data. The comparison unit 430 may obtain a public key of the manufacturer of the target software and decrypt the extracted first authenticity information encrypted with the private key of the manufacturer of the target software using the obtained public key of the manufacturer of the target software. Furthermore, the comparison unit 430 may decrypt second authenticity information encrypted with the private key of the manufacturer of the target software using the obtained public key of the manufacturer of the target software. The comparison unit 430 may then compare the decrypted first authenticity information with the decrypted second authenticity information.

[0084] The public key of the manufacturer of the target software and the public key of the testing organization may be stored in advance, for example, in the information storage unit 150 of the shared system 100. The comparison unit 430 may obtain the public key of the manufacturer of the target software and the public key of the testing organization from the notification unit 140 of the shared system 100, for example, via the certification acquisition unit 320 and the certification acquisition unit 530.

[0085] For example, the comparison unit 430 may be configured to obtain the public key of the inspection agency from the information storage unit 150 of the shared system 100. The private key of the inspection agency designated by the administrator of the shared system 100 may be stored in advance in the information storage unit 150 of the shared system 100. Private keys of inspection agencies other than the inspection agency designated by the administrator of the shared system 100 may not be stored in the information storage unit 150 of the shared system 100. This makes it possible to limit the inspection agencies that can issue inspected certification data to only the inspection agencies designated by the administrator of the shared system 100. In this case, the shared system 100 certifies the legitimacy of the inspection agency.

[0086] The comparison unit 430 notifies the control unit 440 of the comparison result (i.e., information indicating that the first authenticity information and the second authenticity information are the same, or information indicating that the first authenticity information and the second authenticity information are different). The comparison unit 430 may further send information indicating the result of the inspection, which is included in the inspected proof data, to the control unit 440.

[0087] When the comparison unit 430 receives from the proof receiving unit 420 information indicating that the verified proof data for the target software does not exist, it may transmit to the control unit 440 information indicating that the verified proof data for the target software does not exist. When the comparison unit 430 is unable to decrypt the verified proof data using the private key of the testing organization, it may send to the control unit 440 information indicating that the verified proof data is invalid. When the comparison unit 430 is unable to decrypt the first authenticity information included in the verified proof data using the public key of the manufacturer of the target software, it may send to the control unit 440 information indicating that the verified proof data is invalid. When the comparison unit 430 is unable to decrypt the second authenticity information using the public key of the manufacturer of the target software, it may send to the control unit 440 information indicating that the authenticity information is invalid.

[0088] <Control unit 440> The control unit 440 receives the result of the comparison (i.e., information indicating that the first authenticity information and the second authenticity information are the same, or information indicating that the first authenticity information and the second authenticity information are different) from the comparison unit 430. The control unit 440 may further receive information indicating the result of the inspection from the comparison unit 430.

[0089] If the comparison result indicates that the first authenticity information and the second authenticity information are the same, the control unit 440 performs control so that the target software is installed. The control unit 440 may, for example, permit the activation of an installer for the target software. If the comparison result indicates that the first authenticity information and the second authenticity information are not the same, the control unit 440 performs control so that the target software is not installed. The control unit 440 may, for example, prohibit the activation of an installer for the target software.

[0090] If the inspection results included in the inspection proof data indicate that the target software is not safe, the control unit 440 may control the target software not to be installed. For example, if the inspection results indicate that the detected vulnerabilities include vulnerabilities with a severity level equal to or greater than a predetermined level, the control unit 440 may determine that the target software is not safe. For example, if the inspection results indicate that a backdoor has been detected, the control unit 440 may determine that the target software is not safe.

[0091] The control unit 440 may receive information indicating that no inspected proof data exists for the target software from the comparison unit 430. When information indicating that no inspected proof data exists for the target software is received, that is, when no inspected proof data for the target software is obtained, the control unit 440 may perform control so that the target software is not installed.

[0092] The control unit 440 may receive information indicating that the verified proof data is invalid from the comparison unit 430. When information indicating that the verified proof data is invalid is received, the control unit 440 may perform control so that the target software is not installed.

[0093] The control unit 440 may receive information indicating that the authenticity information is invalid from the comparison unit 430. When the control unit 440 receives information indicating that the authenticity information is invalid, the control unit 440 may perform control so that the target software is not installed.

[0094] The control unit 440 may permit installation of the target software by, for example, transmitting information permitting installation of the target software to the information processing device attempting to perform the installation. The control unit 440 may prohibit installation of the target software by, for example, transmitting information prohibiting installation of the target software to the information processing device attempting to perform the installation.

[0095] <Operation> Next, the operation of the information processing device 500 according to the fourth embodiment of the present disclosure will be described in detail with reference to the drawings.

[0096] FIG. 9 is a flowchart illustrating an example of the operation of the information processing device according to the fourth embodiment of the present disclosure.

[0097] 9, the software acquisition unit 510 acquires the target software and second authenticity information of the target software, for example, via a communication network or a storage medium (step S201). The operation of step S201 may be performed, for example, in accordance with an instruction from the user of the information processing device 500. The software acquisition unit 510 sends the second authenticity information to the comparison unit 430 via the authenticity information acquisition unit 410. Then, the operation from step S202 onwards is started, for example, when the user of the information processing device 500 performs an operation on the information processing device 500 to instruct installation of the target software.

[0098] The proof receiving unit 420 requests the inspected proof data of the target software from the shared system 100 (specifically, the notification unit 140 of the shared system 100) via the proof acquisition unit 530 (step S202). The notification unit 140 of the shared system 100 reads the requested inspected proof data from the information storage unit 150 and sends the read inspected proof data to the information processing device 500. The proof receiving unit 420 receives the inspected proof data of the target software from the notification unit 140 of the shared system 100 via the proof acquisition unit 530 (step S203).

[0099] The comparison unit 430 compares the first authenticity information included in the verified proof data with the second authenticity information (step S204). If the first authenticity information and the second authenticity information are the same (YES in step S205), the control unit 440 permits installation of the target software (step S206). In other words, the control unit 440 controls so that the target software is installed. The execution unit 520 executes installation of the target software (step S207). Then, the information processing device 500 ends the operation shown in FIG. 9.

[0100] If the first authenticity information and the second authenticity information are not the same (NO in step S205), control unit 440 does not permit installation of the target software (step S208). In other words, control unit 440 controls so that the target software is not installed. Then, information processing device 500 ends the operation shown in FIG.

[0101] <Effects> The present embodiment described above has the same effects as the first embodiment, for the same reasons as those for the effects of the first embodiment.

[0102] <Other embodiments> Each of the shared system, information processing device, and installation control device according to the embodiments of the present disclosure can be realized by a computer including a memory into which a program read from a storage medium is loaded and a processor that executes the program. Each of the shared system, information processing device, and installation control device according to the embodiments of the present disclosure can also be realized by dedicated hardware. Each of the shared system, information processing device, and installation control device according to the embodiments of the present disclosure can also be realized by a combination of the aforementioned computer and dedicated hardware.

[0103] FIG. 10 is a diagram illustrating an example of a hardware configuration of a computer 1000 that can realize a shared system, an information processing device, and an installation control device according to an embodiment of the present disclosure. In the example illustrated in FIG. 10, the computer 1000 includes a processor 1001, a memory 1002, a storage device 1003, and an I / O (Input / Output) interface 1004. The computer 1000 can also access a storage medium 1005. The memory 1002 and the storage device 1003 are, for example, storage devices such as RAM (Random Access Memory) and a hard disk. The storage medium 1005 is, for example, a storage device such as RAM or a hard disk, a ROM (Read Only Memory), or a portable storage medium. The storage device 1003 may also be the storage medium 1005. The processor 1001 can read and write data and programs from and to the memory 1002 and the storage device 1003. The processor 1001 can access, for example, other devices via the I / O interface 1004. The processor 1001 can access a storage medium 1005. The storage medium 1005 stores any one of a program that causes the computer 1000 to operate as a shared system according to an embodiment of the present disclosure, a program that causes the computer 1000 to operate as an information processing device according to an embodiment of the present disclosure, and a program that causes the computer 1000 to operate as an installation control device according to an embodiment of the present disclosure.

[0104] The processor 1001 loads a program stored in the storage medium 1005 into the memory 1002. Then, the processor 1001 executes the program loaded into the memory 1002, causing the computer 1000 to operate as any one of a shared system, an information processing device, and an installation control device according to an embodiment of the present disclosure.

[0105] The software acceptance unit 110, the certificate receiving unit 130, the software providing unit 120, and the notification unit 140 can be realized, for example, by a processor 1001 that executes a program loaded into memory 1002. The authenticity information acquisition unit 410, the certificate receiving unit 420, the comparison unit 430, the control unit 440, the software acquisition unit 510, the execution unit 520, and the certificate acquisition unit 530 can be realized, for example, by a processor 1001 that executes a program loaded into memory 1002. The information storage unit 150 can be realized by the memory 1002 or a storage device 1003 such as a hard disk drive included in the computer 1000. Some or all of the software acceptance unit 110, the certificate receiving unit 130, the software providing unit 120, the notification unit 140, and the information storage unit 150 can be realized by dedicated circuits that realize the functions of each unit. Some or all of the authenticity information acquisition unit 410, certificate receiving unit 420, comparison unit 430, control unit 440, software acquisition unit 510, execution unit 520, and certificate acquisition unit 530 can be realized by dedicated circuits that realize the functions of each unit.

[0106] Furthermore, some or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes.

[0107] (Appendix 1) a certification receiving unit that receives verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; a comparison unit that compares the first authenticity information included in the verified proof data with the second authenticity information of the target software; a control unit that controls installation of the target software to be executed when the first authenticity information and the second authenticity information are the same; An installation control device comprising:

[0108] (Appendix 2) The certification receiving unit receives the verified certification data in response to receiving an instruction to install the target software. 10. The installation control device of claim 1.

[0109] (Appendix 3) The control unit controls so that installation of the target software is not executed if the verified proof data is not obtained. 3. The installation control device of claim 1 or 2.

[0110] (Appendix 4) The control unit controls so that installation of the target software is not executed when the first authenticity information and the second authenticity information do not match. 4. An installation control device according to any one of claims 1 to 3.

[0111] (Appendix 5) a software acquisition unit that acquires the verified proof data, the target software, and the second authenticity information; The certificate receiving unit receives the verified certificate data from a shared system that holds the verified certificate data. 5. An installation control device according to any one of claims 1 to 4.

[0112] (Appendix 6) an execution unit that executes installation of the target software under the control of the control unit; 6. An information processing device comprising: an installation control device according to any one of claims 1 to 5.

[0113] (Appendix 7) a certification receiving unit that receives verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; a notification unit that receives the verified certification data, compares the first authenticity information included in the verified certification data with second authenticity information of the target software, and notifies the verified certification data to an installation control device that controls installation of the target software when the first authenticity information and the second authenticity information are the same; A shared system comprising:

[0114] (Appendix 8) The notification unit notifies the verified certification data in response to receiving a request for the verified certification data from the installation control device. 7. A shared system as described in Appendix 7.

[0115] (Appendix 9) a software receiving unit that receives the target software and the first authenticity information; a software providing unit that provides the target software and the first authenticity information to an inspection device that inspects the safety of the target software; Equipped with The certificate receiving unit receives the verified certificate data from the verification device. 9. A sharing system as described in Appendix 7 or 8.

[0116] (Appendix 10) An information storage unit is provided, the software receiving unit stores the received target software and the first authenticity information in the information storage unit; the software providing unit provides the target software and the first authenticity information read from the information storage unit; the certificate receiving unit stores the received verified certificate data in the information storage unit; The notification unit notifies the verified certification data read from the information storage unit. 9. A shared system as described in Appendix 9.

[0117] (Appendix 11) When the installation control device determines that the target software can be installed, the installation control device executes the installation of the target software. A sharing system according to any one of appendices 7 to 10.

[0118] (Appendix 12) receiving verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; comparing the first authenticity information included in the verified proof data with second authenticity information of the target software; performing control such that installation of the target software is executed when the first authenticity information and the second authenticity information are the same; Installation control method.

[0119] (Appendix 13) receiving the verified certification data in response to receiving instructions to install the target software; 13. The installation control method of claim 12.

[0120] (Appendix 14) If the verified certification data is not obtained, the installation of the target software is prevented from being executed. 14. The installation control method according to claim 12 or 13.

[0121] (Appendix 15) If the first authenticity information and the second authenticity information do not match, control is performed so that installation of the target software is not executed. An installation control method according to any one of appendices 12 to 14.

[0122] (Appendix 16) acquiring the verified certification data, the target software, and the second authenticity information; receiving the verified certification data from a shared system that holds the verified certification data; An installation control method according to any one of appendices 12 to 15.

[0123] (Appendix 17) According to the control, the target software is installed. 17. An installation control method according to any one of appendices 12 to 16.

[0124] (Appendix 18) receiving verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; receiving the verified certification data, comparing the first authenticity information included in the verified certification data with second authenticity information of the target software, and notifying the verified certification data to an installation control device that controls installation of the target software when the first authenticity information and the second authenticity information are the same; How to share.

[0125] (Appendix 19) notifying the verified certification data in response to receiving a request for the verified certification data from the installation control device; Sharing method as described in Appendix 18.

[0126] (Appendix 20) receiving the target software and the first authenticity information; providing the target software and the first authenticity information to a testing device that tests the safety of the target software; receiving the inspected certification data from the inspection device; 19. A sharing method as described in Appendix 18 or 19.

[0127] (Appendix 21) storing the received target software and the first authenticity information in an information storage unit; providing the target software and the first authenticity information read from the information storage unit; storing the received verified proof data in the information storage unit; Notify the inspection certificate data read from the information storage unit. Sharing method as described in Appendix 20.

[0128] (Appendix 22) When the installation control device determines that the target software can be installed, the installation control device executes the installation of the target software. 22. A sharing method according to any one of appendices 18 to 21.

[0129] (Appendix 23) a certification receiving process for receiving verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; a comparison process of comparing the first authenticity information included in the verified proof data with second authenticity information of the target software; a control process for controlling installation of the target software to be executed when the first authenticity information and the second authenticity information are the same; A storage medium that stores a program that causes a computer to execute the above.

[0130] (Appendix 24) The certification receiving process receives the verified certification data in response to receiving an instruction to install the target software. 24. The storage medium of claim 23.

[0131] (Appendix 25) The control process controls so that installation of the target software is not performed if the verified certification data is not obtained. 25. A storage medium according to claim 23 or 24.

[0132] (Appendix 26) The control process controls so that installation of the target software is not executed when the first authenticity information and the second authenticity information do not match. 26. A storage medium according to any one of appendices 23 to 25.

[0133] (Appendix 27) The program causing a computer to execute a software acquisition process for acquiring the verified certification data, the target software, and the second authenticity information; The certification receiving process receives the verified certification data from a shared system that holds the verified certification data. 27. A storage medium according to any one of appendices 23 to 26.

[0134] (Appendix 28) The program an execution process that executes installation of the target software in accordance with the control of the control process; 28. The storage medium according to any one of appendices 23 to 27, further causing a computer to execute the steps.

[0135] (Appendix 29) a certification receiving process for receiving verified certification data including first authenticity information of the target software and indicating that the safety of the target software has been verified; a notification process of receiving the verified certification data, comparing the first authenticity information included in the verified certification data with second authenticity information of the target software, and notifying the verified certification data to an installation control device that controls installation of the target software when the first authenticity information and the second authenticity information are the same; A storage medium that stores a program that causes a computer to execute the above.

[0136] (Appendix 30) The notification process notifies the verified certification data in response to receiving a request for the verified certification data from the installation control device. 29. The storage medium of claim 29.

[0137] (Appendix 31) On the computer, a software reception process for receiving the target software and the first authenticity information; a software providing process for providing the target software and the first authenticity information to an inspection device that inspects the safety of the target software; Execute The certification receiving process receives the verified certification data from the verification device. 31. A storage medium according to claim 29 or 30.

[0138] (Appendix 32) the software reception process stores the received target software and the first authenticity information in an information storage unit; the software provision process provides the target software and the first authenticity information read from the information storage unit; The certification receiving process stores the received verified certification data in the information storage unit, The notification process notifies the verified certificate data read from the information storage unit. 32. The storage medium of claim 31.

[0139] (Appendix 33) When the installation control device determines that the target software can be installed, the installation control device executes the installation of the target software. 33. A storage medium according to any one of appendices 29 to 32.

[0140] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. [Explanation of symbols]

[0141] 10 Shared Systems 40 Installation control device 100 Shared Systems 110 Software Reception Department 120 Software Distribution Department 130 Certificate Receiving Department 140 Notification Department 150 Information storage section 200 Software provision device 300 Inspection Equipment 320 Certification Department 400 Installation control device 410 Authenticity Information Acquisition Department 420 Certificate Receiving Department 430 Comparison Section 440 Control Unit 500 Information processing equipment 510 Software Acquisition Department 520 Executive Department 530 Certification Department 1000 computers 1001 processor 1002 memory 1003 Storage device 1004 I / O interface 1005 Storage medium

Claims

1. a certification receiving means for receiving verified certification data including first authenticity information of the target software, indicating that the safety of the target software has been verified, and including severity information indicating the degree of severity of a vulnerability detected in the target software; a comparison means for comparing the first authenticity information included in the verified proof data with the second authenticity information of the target software; a control means for controlling installation of the target software to be executed when the first authenticity information and the second authenticity information are the same and the vulnerability does not include a vulnerability whose severity is equal to or greater than a predetermined severity; An installation control device comprising:

2. The certification receiving means receives the verified certification data in response to receiving an instruction to install the target software. The installation control device according to claim 1 .

3. The control means controls so that installation of the target software is not executed if the verified certification data is not obtained. The installation control device according to claim 1 or 2.

4. The control means controls so that installation of the target software is not executed when the first authenticity information and the second authenticity information do not match. The installation control device according to any one of claims 1 to 3.

5. a software acquisition means for acquiring the verified proof data, the target software, and the second authenticity information; The certification receiving means receives the verified certification data from a shared system that holds the verified certification data. The installation control device according to any one of claims 1 to 4.

6. an execution means for executing installation of the target software in accordance with the control by the control means; An information processing device comprising the installation control device according to claim 1 .

7. A second certification receiving means for receiving the inspected certification data; a notification means for notifying the installation control device of the verified certification data; a shared system comprising: An installation control device according to any one of claims 1 to 4; Including the installation control system.

8. The notifying means notifies the verified certification data in response to receiving a request for the verified certification data from the installation control device. The installation control system of claim 7.

9. The shared system comprises: a software receiving means for receiving the target software and the first authenticity information; a software providing means for providing the target software and the first authenticity information to a testing device that tests the safety of the target software; Equipped with The certification receiving means receives the verified certification data from the verification device.

9. An installation control system according to claim 7 or 8.

10. The shared system comprises: An information storage means is provided, the software receiving means stores the received target software and the first authenticity information in the information storage means; the software providing means provides the target software and the first authenticity information read from the information storage means; the certification receiving means stores the received verified certification data in the information storage means; The notification means notifies the verified certification data read from the information storage means. The installation control system of claim 9.

11. When the installation control device determines that the target software can be installed, the installation control device executes the installation of the target software. An installation control system according to any one of claims 7 to 10.

12. receiving verified certification data including first authenticity information of the target software, indicating that the safety of the target software has been verified, and including severity information indicating the degree of severity of a detected vulnerability; comparing the first authenticity information included in the verified proof data with second authenticity information of the target software; performing control such that installation of the target software is executed when the first authenticity information and the second authenticity information are the same and the detected vulnerabilities do not include vulnerabilities whose severity is equal to or greater than a predetermined severity; Installation control method.

13. a certification receiving process for receiving verified certification data including first authenticity information of the target software, indicating that the safety of the target software has been verified, and including severity information indicating the degree of severity of a detected vulnerability; a comparison process of comparing the first authenticity information included in the verified proof data with second authenticity information of the target software; a control process for controlling installation of the target software when the first authenticity information and the second authenticity information are the same and the detected vulnerabilities do not include vulnerabilities whose severity is equal to or greater than a predetermined severity; A program that causes a computer to execute the following.

Images