Authentication device, authentication device control method and program

The authentication device verifies the legitimacy of data, entities, and procedures in service providing systems, addressing the challenge of system integrity and security in dynamic configurations, ensuring rapid and trustworthy system authentication.

JP7587492B2Active Publication Date: 2024-11-20HITACHI LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021213795
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-12-28
Publication Date
2024-11-20
Estimated Expiration
2041-12-28

AI Technical Summary

Technical Problem

Existing systems lack the ability to determine whether they are operating according to specifications due to frequent changes in configurations, vulnerabilities from developer mistakes or malicious actions, and the inability for users to verify the integrity and soundness of the system without manual verification or third-party authentication.

Method used

An authentication device that includes a processor and memory, with units for data, ID attribute, process, and system authentication to verify the legitimacy of data, processing entities, and procedures, issuing certificates to prove proper construction, allowing users to trust the system's authenticity.

Benefits of technology

Enables rapid authentication of service providing systems, ensuring they are constructed correctly and securely, allowing users to trust the system's integrity without manual verification, and providing a chain of trust for third-party verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007587492000001
    Figure 0007587492000001
  • Figure 0007587492000002
    Figure 0007587492000002
  • Figure 0007587492000003
    Figure 0007587492000003
Patent Text Reader

Abstract

To perform authentication in a service providing system that is constructed to provide a predetermined information processing service by executing a service providing program.SOLUTION: An authentication device is configured to perform authentication in a service providing system that is constructed to provide a prescribed information processing service by executing a service providing program. The authentication device includes a processor and a memory, and includes a data authentication unit that authenticates the validity of data which includes the service providing program and is used for constructing the service providing system, an ID attribute authentication unit that authenticates the validity of a processing subject for constructing the service providing system using the data, a process authentication unit that authenticates the validity of a procedure for constructing the service providing system, and a system authentication unit that authenticates that the service providing system is validly constructed when the validity of the data, the validity of the processing subject, and the validity of the procedure are authenticated.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an authentication device, a control method for an authentication device, and a program. [Background technology]

[0002] In the past, various systems have been developed to provide information processing services by having a computer execute a program, but as the content of information processing services has become more sophisticated, the systems have become larger in scale and more complex in configuration. Furthermore, system changes have become more frequent.

[0003] Therefore, various techniques have been proposed to support the development of such systems and to enable the creation of such systems more efficiently (for example, see Non-Patent Documents 1 to 3). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] RTCA DO-178 Revision C: Software Considerations in Airborne Systems and Equipment Certification1(https: / / www.oviss.jp / view / item / 000000000110) [Non-Patent Document 2] Introducing SLSA, an End-to-End Framework for Supply Chain Integrity(https: / / security.googleblog.com / 2021 / 06 / introducing-slsa-end-to-end-framework.html) [Non-Patent Document 3] Certificate transparency3(Communications of the ACM, Vol.57, Issue 10, October 2014, pp 40-46, https: / / dl.acm.org / doi / fullHtml / 10.1145 / 2659897) Summary of the Invention [Problem to be solved by the invention]

[0005] As examples of such technologies, new development environments and development methods such as OSS (Open Source Software), public clouds, Agile, and Software Defined Networks have become widespread in recent years.

[0006] However, as a result, more people are now involved in system development, and the development process itself is becoming one in which each step of requirements definition, design, development, and testing is repeated many times. Furthermore, the computers that execute programs are themselves being virtualized, and the entire system that provides information processing services is being realized as software. As a result, system configurations are being changed more and more frequently.

[0007] Therefore, even in such a situation, configuration management tools such as Software Supply Chain, git, and terraform are used to properly understand the system configuration and to enable tracking of the dependencies between each component of the system.In addition, technologies such as containers and service meshes are also used to optimize the dependencies between system components and make it easier to understand the calling relationships between components.

[0008] However, such technology cannot determine whether the system is operating according to specifications.

[0009] For example, a developer's mistake or a malicious individual's illegal actions may result in vulnerable code being mixed into a program, causing the system to operate outside of its specifications. Even if the program is in accordance with the specifications, there is a possibility that the system will behave outside of the specifications due to errors in the settings or data. In addition, if malware is running in the environment in which the program runs, even if there are no problems with the deployed program or data, tampering after deployment may cause the system to behave outside of the specifications.

[0010] For this reason, various scenario tests are conducted when a program or system is changed or deployed in order to discover problems in advance.

[0011] In addition, there are techniques such as (1) to (3) below for detecting or preventing tampering after deployment.

[0012] (1) Use hash values ​​to verify that the programs, systems, and data being deployed have not been tampered with. (2) The signature is checked when a program is executed to prevent unauthorized programs from running, and (3) The hash chain of the executable program stored in the tamper-resistant area is verified to detect the running of unauthorized programs.

[0013] However, users of information processing services cannot obtain the information necessary to use these techniques, and therefore cannot use these techniques to grasp the state of the system.

[0014] Therefore, users of information processing services can only grasp the status of the system by using the means described below in (4) and (5).

[0015] (4) Periodically execute the system's API (Application Programming Interface) Check whether the animal is alive or dead. (5) Trust the system and its operators as a whole and consider it to be in good working order.

[0016] Here, in the case of method (4), the alive monitoring uses a standard response to a standard request, so only limited information can be obtained, such as whether the system outputs the expected results. Therefore, it is not possible to confirm whether the system was built using the appropriate components, and whether it was built by the appropriate person in charge using the appropriate procedures.

[0017] On the other hand, in the case of option (5), the user of the information processing service has no prior knowledge of the system's state, and can only grasp the state at the time of use.

[0018] To address the issues faced by system users as described above, there are technologies that allow third-party verification and frameworks to verify the completeness and soundness of the system.

[0019] First, a development methodology is known for systems that require high safety and reliability, such as aircraft, as described in Non-Patent Document 1. Non-Patent Document 1 describes how, for parts that require high safety and reliability, the corresponding relationship between requirements and specifications is clarified, a verification plan is formulated in advance, and the development process and environment are standardized, and then certification is obtained from a third-party organization.

[0020] Also, there is a methodology for protecting programs and systems from malicious changes, as described in Non-Patent Document 2. Non-Patent Document 2 describes how to prevent malicious changes by clarifying the origin of a program and verifying the environment related to its construction and deployment.

[0021] Furthermore, as described in Non-Patent Document 3, there is a method that makes it possible to detect abnormal certificates from among the many certificates that exist on the Web. Non-Patent Document 3 describes how a logstore that allows only appending and not rewriting is used to enable anyone to verify certificates and publish the results, thereby making it possible to detect the presence or absence of abnormalities regardless of the chain of trust or the root of trust.

[0022] However, the method in Non-Patent Document 1 also verifies the validity of specifications, and requires manual verification of the correspondence between requirements and specifications, etc. Therefore, it takes several months to complete the verification, making it difficult to apply to fields where configurations are frequently changed, such as programs and systems.

[0023] Furthermore, the method described in Non-Patent Document 2 aims to detect and defend against the inclusion of malicious code and attacks during the build by checking the source of the code and specifying the use of a build and deployment environment that is less susceptible to external disturbances. However, it cannot prevent unauthorized states that arise from incorrect operations by persons with proper authorization.

[0024] Furthermore, the method in Non-Patent Document 3 is a method that targets server and domain certificates on the Web, and therefore cannot be applied to the detection and verification of abnormal states of a system on which a program is running.

[0025] The present invention has been made in consideration of such problems, and aims to provide an authentication device, a control method for the authentication device, and a program capable of authenticating a service providing system constructed to provide a specified information processing service by executing a service providing program. [Means for solving the problem]

[0026] The authentication device that solves the above problem is an authentication device that authenticates a service providing system that is constructed to provide a predetermined information processing service by executing a service providing program, and includes a processor and a memory, and includes a data authentication unit that authenticates the validity of data used when constructing the service providing system, including the service providing program, an ID attribute authentication unit that authenticates the validity of a processing entity that constructs the service providing system using the data, a process authentication unit that authenticates the validity of a procedure for constructing the service providing system, and certifies that the service providing system has been constructed legitimately when the validity of the data, the validity of the processing entity, and the validity of the procedure are authenticated. and outputting a certificate to prove that the service providing system is legitimately constructed. and a system authentication unit for authenticating the authentication information.

[0027] Other problems and solutions disclosed in the present application will be made clear in the section of the description of the invention and the drawings. Effect of the Invention

[0028] According to the present invention, it is possible to perform authentication of a service providing system that is constructed so as to provide a predetermined information processing service by executing a service providing program. [Brief description of the drawings]

[0029] [Figure 1] FIG. 1 is a diagram illustrating an example of an overall configuration. [Diagram 2] FIG. 11 is a diagram illustrating an example of process log information. [Diagram 3] FIG. 11 is a diagram illustrating an example of deployment log information. [Figure 4] FIG. 11 is a diagram showing an example of ID authentication result information. [Diagram 5] FIG. 11 is a diagram illustrating an example of attribute authentication result information. [Figure 6] FIG. 11 illustrates an example of process authentication result information. [Figure 7] FIG. 11 is a diagram showing an example of data authentication result information. [Figure 8]FIG. 11 is a diagram showing an example of system authentication result information. [Figure 9] FIG. 11 is a diagram illustrating an example of a sequence of attribute authentication. [Figure 10] FIG. 11 is a diagram illustrating an example of a process authentication sequence. [Figure 11] FIG. 11 is a diagram showing an example of a data authentication sequence. [Figure 12] FIG. 11 is a diagram illustrating an example of a system authentication sequence. [Figure 13] FIG. 13 illustrates an example of a certificate. [Figure 14] FIG. 1 is a diagram illustrating an example of an overall configuration. [Figure 15] FIG. 2 is a diagram illustrating an example of the configuration of a construction and deployment device, a system-related device, and an authentication device. [Figure 16] FIG. 2 illustrates an example of a storage device of the construction and deployment device. [Figure 17] FIG. 2 illustrates an example of a storage device for a system-related device. [Figure 18] FIG. 2 illustrates an example of a storage device of the authentication device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment. Furthermore, the embodiment shown below may be applied alone, or multiple or all of the embodiments may be applied in combination.

[0031] ==Overall Configuration== 1 is a diagram logically illustrating the overall configuration of an information processing system A00 including an authentication device A03 according to an embodiment of the present invention. The information processing system A00 is configured with an implementation and deployment device A01, a system-related device A02, and an authentication device A03.

[0032] The construction and deployment device A01, the system-related device A02, and the authentication device A03 may be configured using physical computers or virtual computers.

[0033] The building and deployment device A01 is a computer having a function for building a service providing system A22, which will be described later. The service providing system A22 is built so as to provide a predetermined information processing service by executing a service providing program.

[0034] The construction and deployment device A01 also stores various data used when constructing the service providing system A22. In addition to the above-mentioned service providing programs, this data includes reference data used when the service providing programs provide information processing services, and a configuration definition file that represents the configuration of the service providing system A22.

[0035] As shown in FIG. 1, the building and deployment device A01 is configured to include a data repository A10, a build A11, a container repository A12, a deployment A13, and a process log A14.

[0036] Among these, the data repository A10, the container repository A12, and the process log A14 store the above-mentioned data used by the construction and deployment device A01 when constructing the service providing system A22. The build A11 and the deployment A13 are software modules that perform processing to construct the service providing system A22 using the above-mentioned data.

[0037] For example, the build A11 and the deployment A13 are carried out by using various data stored in the data repository A10 and the container repository A12 to provide a service providing system A22. and deploying it in the system-related device A02. Then, the history of the processing performed when constructing the service providing system A22 is recorded in the process log A14.

[0038] The system-related device A02 is a computer that executes the service providing system A22 to provide information processing services.

[0039] In this embodiment, the service providing system A22 is executed on an execution platform constructed by the system-related device A02 executing the system platform A20, and the above-mentioned information processing service is provided. With this aspect, the system-related device A02 can execute the service providing system A22 to provide an information processing service without being restricted by the physical hardware configuration of a processor, memory, network, etc. Also, it becomes possible to flexibly execute a plurality of service providing systems A22 according to the contents of the information processing service to be provided.

[0040] The system-related device A02 is configured to include a system platform A20, a deployment log A21, and a service providing system A22.

[0041] Among these, the deployment log A21 records a history of processing when the deployment A13 deploys the service providing system A22 in the system-related device A02. The system platform A20 is a software module for providing an execution infrastructure for executing the service providing system A22.

[0042] The authentication device A03 is a computer that authenticates the service providing system A22 deployed in the system-related device A02. For example, the authentication device A03 verifies the soundness of the service providing system A22 from the standpoint of development, construction, and deployment.

[0043] The authentication device A03 is configured to include a root authentication unit A30, an ID attribute authentication unit A31, an attribute rule A32, an ID attribute authentication result A33, a process authentication unit A41, a process model A42, a process authentication result A43, a data authentication unit A51, a data quality rule A52, a data authentication result A53, a system authentication unit A61, a system rule A62, and a system authentication result A63.

[0044] The root authentication unit A30 functions as a higher-level authentication authority that authenticates the validity of the ID attribute authentication unit A31, the process authentication unit A41, the data authentication unit A51, and the system authentication unit A61. The root authentication unit A30 authenticates itself.

[0045] The ID attribute authentication unit A31 authenticates the validity of a processing entity that constructs the service providing system A22. The processing entity is, for example, a software module that performs processing to construct the service providing system A22, or a person in charge of constructing the service providing system A22 using a software module. The software module is, for example, the build A11 or the deployment A13. The person in charge includes, for example, the developer or operator of the service providing system A22, and an administrator who manages these persons.

[0046] In this manner, when the service providing system A22 is constructed, it becomes possible to authenticate whether or not a software module that has been improperly modified is being used, or whether or not a user without proper authority is using the software module.

[0047] The process authentication unit A41 authenticates the validity of the procedure for constructing the service providing system A22. For example, the process authentication unit A41 authenticates the validity of the procedure for constructing the service providing system A22 by using the history of the process recorded in the process log A14. By using this, the validity of the procedure for constructing the service providing system A22 is authenticated.

[0048] The data authentication unit A51 authenticates the validity of various data used by the construction and deployment device A01 when constructing the service providing system A22. As described above, the data includes, for example, the service providing program, as well as reference data that the service providing program references to provide an information processing service, and a configuration definition file that represents the configuration of the service providing system A22.

[0049] In this manner, it becomes possible to verify whether the service providing system A22 has been constructed using unauthorized data.

[0050] If the validity of the above-mentioned data, the validity of the processing subject, and the validity of the procedure are authenticated, the system authentication unit A61 certifies that the service providing system A22 has been legitimately constructed. Furthermore, the system authentication unit A61 outputs a digital certificate for proving that the service providing system A22 has been legitimately constructed.

[0051] In this way, according to the authentication device A03 of this embodiment, it becomes possible to authenticate that the construction of the service providing system A22 by the construction and deployment device A01 is being carried out by a legitimate processing entity by processing legitimate data in a legitimate procedure.

[0052] In addition, since an electronic certificate is issued to prove that the service providing system A22 is legitimately constructed, the user of the service providing system A22 can understand the status of the service providing system A22 by checking the electronic certificate issued by the authentication device A03. In this case, the user does not need to perform the verification himself, and only needs to trust the authentication device A03. In particular, in this embodiment, only the root authentication unit A30 needs to be trusted.

[0053] This will be explained in detail below.

[0054] = Construction and deployment equipment = The data repository A10 manages and stores source code of the service providing program that runs on the service providing system A22, data used, configuration definition files of the service providing system A22, etc. The data repository A10 is configured using a software module such as git that manages files in association with repositories, paths, branches, etc., and manages differences when files are changed in association with the date and time, the person who reflected the change, and the hash value of the change content.

[0055] Build A11 tests and builds the source code obtained from Data Repository A10, and also builds a container image by incorporating various data such as middleware into the built image, and stores it in Container Repository A12. Build A11 is configured using software modules that combine a CI server such as Jenkins, various language processing systems, and container construction software such as Docker.

[0056] The container repository A12 manages and stores the container images built by the build A11. The container repository A12 is configured using a software module, such as dockerhub or Harbor, that manages container images by name and tag.

[0057] The deployment A13 creates resources such as containers, volumes, and networks on the system platform A20 according to the contents of the configuration definition file managed in the data repository A10, and deploys containers obtained from the container repository A12. The image is deployed to construct the service providing system A22. The deployment A13 is configured using a software module, such as terraform, that interprets the contents of a configuration definition file and executes the deployment.

[0058] Process log A14 records various commits in data repository A10 and build A1 It records events such as building and testing in A11, registration, updating, deletion and deployment of container images in the container repository A12, creation, updating and deletion of deployment-related resources in A13 and deployment of container images as logs.

[0059] =System-related equipment= The system platform A20 constructs an execution infrastructure for the service providing system A22 having various resources created in response to an instruction from the deployment A13. This is configured using infrastructure software (software modules) such as Kubernetes.

[0060] The deployment log A21 records events such as creation, update, and deletion of resources in the system platform A20 as a log.

[0061] The service providing system A22 is a container that the deployment A13 constructs based on a configuration definition file, and is executed on the system platform A20. A plurality of service providing systems A22 are configured for each type of information processing service, and provide various functions to users.

[0062] =Authentication Device= The root authenticator A30 is a certificate authority that serves as a base of trust and authenticates the validity of the ID attribute authenticator A31, the process authenticator A41, the data authenticator A51, and the system authenticator A61.

[0063] The ID and attribute authentication unit A31 is a certification authority that is delegated by the route authentication unit A30 to certify the validity of the ID and attributes of the processing subject.

[0064] For ID authentication, the ID attribute authentication unit A31 uses information such as ID and credentials stored in the ID attribute authentication result A33 to authenticate processing entities such as developers and operators involved in the service providing system A22, as well as build A11, deployment A13, and system platform A20.

[0065] In addition, when authenticating attributes of developers and operators, the ID attribute authentication unit A31 makes a judgment based on the qualifications and experience held by the developers and operators, as well as the past behavioral history stored in the process log A14, based on the criteria stored in the attribute rules A32, and determines attributes such as whether the developer or operator is capable of committing or reviewing code or whether the developer or operator is capable of issuing deployment instructions. The judgment is stored in the ID attribute authentication result A33, and the attribute authentication is performed using this information.

[0066] The process authentication unit A41 is a certification authority that is delegated by the route authentication unit A30 to authenticate the validity of the process for constructing the service providing system A22.

[0067] The process authentication unit A41 verifies whether the log sequences of source code and data commit, review, testing, system deployment, etc. deviate from the normal process and verifies the role of the person who performed the operation, thereby proving that the operation is problem-free.

[0068] The process authentication unit A41 compares the log sequences stored in the process log A14 and the deployment log A21 with the process model stored in the process model A42, and determines the type of the process and calculates its suitability. The process authentication unit A41 reports the results to the process. The access authentication result is stored in A43.

[0069] The process model is represented by a data structure such as a Petri net, and the process authentication unit A41 uses a method such as process mining to compare the log sequence with the process model.

[0070] The data authentication unit A51 is a certification authority that is delegated by the route authentication unit A30 to perform data authentication.

[0071] The data authentication unit A51 verifies the ID and role of the person who committed and reviewed the source code and data, and proves that the source code and data have not been illegally altered.

[0072] The data authentication unit A51 judges whether the various data stored in the data repository A10 and the container repository A12 are trustworthy based on the rules stored in the data quality rules A52. The data authentication unit A51 stores the result in the data authentication result A53.

[0073] A standard is a set of rules that describes what kind of data can be trusted. Data quality standard A52 states that if the people involved in creating or modifying data have valid IDs and attributes, and the original data has been verified, then the created data can be trusted.

[0074] The system authentication unit A61 is a certification authority that is delegated by the route authentication unit A30 to certify the service providing system A22.

[0075] The system authentication unit A61 authenticates the system platform A20 on which the service providing system A22 runs, and the original images such as containers when the service providing system A22 is deployed. Also, when the service providing system A22 is deployed, it verifies the source code, data, operations, people involved and their attributes, the system platform A20 where the service providing system A22 is deployed, and the images used, and proves that there are no problems that could lead to an unauthorized state in the deployed service providing system A22.

[0076] The system authentication unit A61 judges the validity of the deployed service providing system A22 based on the system rules A62, and judges the soundness of the service providing system A22. The system authentication unit A61 stores the result in the system authentication result A63.

[0077] 2 shows an example of the format of the process log information B00 stored in the process log A14 in this embodiment. The process log information B00 is composed of a list of groups of "process ID", "date and time", "log type", "event name", "log creator", and "context".

[0078] Here, in the "process ID", an identifier of each process log information (hereinafter also referred to as log) B00 is written.

[0079] "Date and time" is the date and time when the log was generated.

[0080] "Log type" is used to distinguish the type of log, and types such as those related to development, those related to operations, and those related to modules such as build and deployment are recorded.

[0081] The "event name" is used to distinguish logs, such as a commit or approval in development, a deployment instruction or approval in operation, or each log output by a module.

[0082] "Log creator" distinguishes the creator of the log, and indicates the ID of the person or software module that generated the log based on the ID attribute authentication result A33.

[0083] "Context" is used to assist in distinguishing log sequences, and by extracting logs using the values ​​stored in this column, it is possible to obtain a sequence of related logs.

[0084] 3 shows an example of the format of data held by the deployment log information C00 stored in the deployment log A21 in this embodiment. The deployment log information C00 is composed of a list of groups of "resource ID", "creation date and time", "deletion date and time", "setting value", and "platform ID".

[0085] Here, the "resource ID" is an identifier for the resource.

[0086] The "creation date and time" is the date and time when the resource was created.

[0087] "Deletion date and time" is the date and time when the resource is deleted, if the resource is deleted.

[0088] A "setting value" is a value set for a resource when the resource is created, such as capacity or performance.

[0089] "Platform ID" is the ID of the system platform A 20 on which the resource was created.

[0090] 4 shows an example of the format of ID authentication result information D00 stored in the ID attribute authentication result A33 in this embodiment. The ID authentication result information D00 is composed of a list of groups of "ID", "Name", "Account type", "Credential", "Created date and time", "Updated date and time", "Public key", and "Is valid".

[0091] Here, "ID" is an identifier for an account held by a processing entity such as a person or module.

[0092] "Name" is a string that makes it easy for people to distinguish accounts.

[0093] The "account type" is a character string used to distinguish the type of account, such as whether the account is for a person or for use by a program or module.

[0094] "Credential" is information used to identify an account, including a password and a reference to an external IdP.

[0095] The "creation date and time" is the date and time when the account was created.

[0096] The "Update Date and Time" is the date and time when the account was updated. The account is periodically verified and updated to verify its validity.

[0097] The "public key" is the public key that corresponds to the private key held by the account user.

[0098] "Is Valid" is a flag to identify whether an account is valid or invalid. Instead of having this column, "is valid" can be managed and published in the form of a CRL, or managed and published on an OCSP server. When others refer to this content, it is provided in the form of an X.509 public key certificate as specified in RFC5280, for example.

[0099] This entry is added when a person who wishes to add an entry submits a certificate signing request to the ID attribute authentication unit A31, which verifies the contents of the request and finds no problems with the contents of the certificate signing request. The entry contents are also verified by the ID attribute authentication unit A31, and if the existence of the entry cannot be confirmed, the value of "is valid" becomes false. The value of "is valid" is also set to false upon request from the certificate issuer.

[0100] 5 shows an example of the data format of the attribute authentication result information E00 stored in the ID attribute authentication result A33 in this embodiment. The attribute authentication result information E00 is composed of a list of groups of "ID", "attribute type", "creation date and time", "update date and time", and "is valid".

[0101] Here, "ID" is the identifier of the account whose attributes are to be certified.

[0102] "Attribute type" is a character string that indicates the attribute of the certification target.

[0103] The "creation date and time" is the date and time when the attribute certificate was created.

[0104] The “update date and time” E04 is the date and time when the attribute certificate was updated. Attributes are updated when the target status is investigated for validity verification and the like.

[0105] "Is valid" is a flag to identify whether the target attribute certificate is valid or invalid. Instead of having this column, "is valid" can be managed and published in the form of a CRL, or managed and published on an OCSP server. When this content is referenced by others, it is provided in the form of an X.509 attribute certificate as specified in RFC5755, for example.

[0106] 6 shows an example of a data format of the process authentication result information F00 stored in the process authentication result A43 in this embodiment. The process authentication result information F00 is composed of a list of sets of "process authentication result ID", "sequence ID", "attribute capable of identifying a set of process IDs", "determination result", "determination date and time", and "is valid".

[0107] Here, the "process authentication result ID" is an identifier for distinguishing authentication results.

[0108] The "sequence ID" is an identifier given to the sequence of the process log to be authenticated.

[0109] The "attribute that can identify a set of process IDs" is a value for identifying the process log set to be judged from the process log information B00 stored in the process log A14, and stores a list of process IDs and extraction conditions such as the type, event name, log generator, and period for extraction.

[0110] The "judgment result" is a character string that indicates what operation the target process log set corresponds to as a result of the judgment, and whether or not the operation is being performed correctly.

[0111] "Determination date and time" is the date and time when the determination was made.

[0112] "Is valid" is a flag that indicates whether the judgment result is valid. When this content is referenced by others, it is provided in a format similar to the data validation certificate defined in RFC3029. In this case, it is provided by storing the validation result for the target sequence in the certs field, for example.

[0113] 7 shows an example of the data format of the data authentication result information G00 stored in the data authentication result A53 in this embodiment. The data authentication result information G00 is composed of a list of sets of "data authentication result ID", "file identifiable attribute", "hash value", "judgment result", "judgment date and time", and "is valid".

[0114] Here, the "data authentication result ID" is an identifier for distinguishing authentication results.

[0115] The "file identifiable attribute" is a value for identifying the file to be authenticated, and stores a set of the URL, branch name, and version of the file in the data repository A10 and the container repository A12.

[0116] The "hash value" is the hash value of the file to be authenticated.

[0117] The "judgment result" is a string that indicates whether the target file was created, updated, and confirmed by an account with proper authority or role as a result of the judgment.

[0118] "Determination date and time" is the date and time when the determination was made.

[0119] "Is valid" is a flag that indicates whether the judgment result is valid or not. Instead of having this column, "is valid" can be managed and published in the form of a CRL, or managed and published on an OCSP server. When others refer to this content, it is provided in a format similar to the data validation certificate specified in RFC3029, for example.

[0120] 8 shows an example of the data format of the system authentication result information H00 stored in the system authentication result A63 in this embodiment. The system authentication result information H00 is composed of a list of sets of "system authentication result ID", "system ID", "sequence ID at the time of deployment", "judgment result", "judgment date and time", "expiration date", "previous system authentication result ID", and "is valid".

[0121] Here, the "system authentication result ID" is an identifier for distinguishing authentication results.

[0122] The "system ID" is a value assigned by the deployment A13 to each deployed service providing system A22, for identifying each service providing system A22.

[0123] The "sequence ID at the time of deployment" is an identifier given to the sequence of the log output when the service providing system A22 to be authenticated, which is stored in the deployment log A21, is deployed.

[0124] The "determination result" is a string indicating whether the target service providing system A22 was deployed to the legitimate system platform A20 using legitimate code, following a legitimate process, and has been confirmed.

[0125] "Determination date and time" is the date and time when the determination was made.

[0126] "Expiration date" is the date and time until which the determination is valid.

[0127] The "previous system authentication result ID" is the value of the system authentication result ID that was valid up until that point, if authentication of the service providing system A22 is performed again before the expiration date.

[0128] "Is valid" is a flag that indicates whether the judgment result is valid or not. Note that instead of having this column, "is valid" can be managed and published in the form of a CRL or an OCSP server.

[0129] When this content is referenced by others, it is provided in a format similar to the data validation certificate defined in RFC 3029. For example, the certs field may store the validation results of the log sequence at the time of deployment, the validation results of the codes and data used in the service provision system A22, the validation results of the IDs and attributes of the people involved in deploying the service provision system A22, and information for users of the service provision system A22 to identify the service provision system A22.

[0130] Examples of information for identifying the service providing system A22 include an FQDN, an IP address, and a location where the system is installed.

[0131] Fig. 9 is an activity diagram showing the process related to attribute authentication performed by the ID attribute authentication unit A31. Fig. 9 shows the process when the ID attribute authentication unit A31 performs authentication related to the attributes of the processing subject.

[0132] In step I01, the ID attribute authentication unit A31 determines the account of the processing subject to attribute verification and collects information corresponding to the account. The ID attribute authentication unit A31 collects information from the process log A14, the process authentication result A43, etc. In addition, the ID attribute authentication unit A31 uses declarations and evidence from the account owner, approval from a superior, etc., for qualifications and experience that cannot be measured only by the actions taken by the processing subject on the building and deployment device A01.

[0133] In step I02, the ID attribute authentication unit A31 checks the collected information against the attribute rules A32. The contents of the rules include whether the processing subject has experience in deployment, development, and review within a certain period of time in the past, and whether the processing subject has performed processes that deviate from the normal range. In addition, there is evidence that the processing subject has valid qualifications that have been approved by a superior and certified by an external organization.

[0134] In step I03, the ID attribute authentication unit A31 determines whether or not to assign or update attributes based on the result of the comparison in step I02, and stores the result of the determination in the ID attribute authentication result A33.

[0135] The ID attribute authentication unit A31 executes the attribute authentication process when a person who wishes to issue an attribute certificate transmits a certificate signing request to the authentication device A03. The ID attribute authentication unit A31 also periodically executes the attribute authentication process.

[0136] Fig. 10 is an activity diagram showing the process authentication process performed by the process authentication unit A41. Fig. 10 shows the process performed by the process authentication unit A41 when authenticating a process.

[0137] In step J01, the process authentication unit A41 reads the process log A14 from the process log A14. The process authentication unit A41 obtains a sequence of the log records, compares it with the model, and calculates the accuracy rate. The method of obtaining the sequence may be a date and time range, a log type, a log creator, a context value, or a list of process IDs. The process authentication unit A41 also obtains the process model from the process model A42.

[0138] In step J02, the process authentication unit A41 determines which model the sequence of process logs corresponds to based on the result of step J01. The determination method is a procedure for matching the model with the maximum value among those whose calculated conformance rate is equal to or greater than a threshold value.

[0139] The process authentication unit A41 executes the process authentication process when a person who approved the data merging into the data repository A10 or the container repository A12 or the deployment of the service providing system A22 transmits a certificate signing request to the authentication device A03. The process authentication unit A41 may also execute the process authentication process when a software module that manages the data repository A10 or the container repository A12 or a software module that has deployed the service providing system A22 transmits a certificate signing request to the authentication device A03.

[0140] Fig. 11 is an activity diagram showing the process related to data authentication performed by the data authentication unit A51. Fig. 11 shows the process when the data authentication unit A51 performs authentication related to data.

[0141] In step K01, the data authentication unit A51 acquires information on the original data, the account and process that performed the commit, review, and test, and performs verification on the data to be verified. At this time, the data authentication unit A51 identifies the data to be verified by using a repository name, path, branch name, hash value, etc.

[0142] The data authentication unit A51 also determines the original data based on whether the data was created by a trusted organization and whether a verification result exists in the data authentication result A53. For commit, review, and test, the sequence of process logs is obtained from the process log A14, and verification is performed via the process authentication unit A41. For account information, it is determined whether a valid account exists in the ID attribute authentication result A33 and has the required attributes.

[0143] In step K02, the data authentication unit A51 checks the result of step K01 against the data quality rules A52 to determine whether there is a problem, and reflects the result in the data authentication A53. An example of the rules is that there is no problem if the data is reliable, the data is modified by a person with valid qualifications, and the software module has made changes through a prescribed process such as commit, review, and test.

[0144] The data authentication unit A51 executes data authentication processing when a person who has committed or merged data to the data repository A10 or the container repository A12 creates a certificate signing request and sends it to the data authentication unit A51. The data authentication unit A51 may also execute data authentication processing when management software (software module) of the data repository A10 or the container repository A12 sends a certificate signing request.

[0145] Fig. 12 is an activity diagram showing the process related to system authentication performed by the system authentication unit A61. Fig. 12 shows the process when the system authentication unit A61 performs authentication related to the service providing system A22.

[0146] In step L01, the system authentication unit A61 verifies the process related to the deployment of the service providing system A22. At this time, the system authentication unit A61 refers to the deployment log A21 and the process model A42, and verifies the compatibility of the process log at the time of deployment with the model.

[0147] In step L02, the system authentication unit A61 verifies the data used in the service providing system A22. At this time, the system authentication unit A61 verifies the data by referring to the data authentication result A53 and the verification results of the source code, setting values, reference data, configuration definition files, etc.

[0148] In step L03, the system authentication unit A61 refers to the data quality rules A52, data authentication results A53, attribute rules A32, and ID attribute authentication results A33, and verifies the system platform A20 where the data is to be deployed, the validity of the account of the processing entity that instructed the deployment, the validity of the attributes, etc.

[0149] If there is no problem in steps L01 to L03, the system authentication unit A61 determines in step L04 that there is no problem with the current service providing system A22.

[0150] The system authentication unit A61 executes the system authentication process when a person who approved the deployment execution of the service providing system A22 creates a certificate signing request and sends it to the system authentication unit A61. The system authentication unit A61 may also execute the system authentication process when a deployed software module sends a certificate signing request.

[0151] Furthermore, if it is confirmed that the identification information of the service providing system A22 is used in another CSR and that the current service providing system A22 has been replaced, the system authentication unit A61 performs processing to revoke the certificate.

[0152] FIG. 13 shows an example of a certificate chain involved when the system authentication unit A61 verifies the certificate of the service providing system A22.

[0153] M01 is a self-signed certificate of the root authentication unit A30.

[0154] M02 to M05 are certificates of the ID attribute authenticator A31, the process authenticator A41, the data authenticator A51, and the system authenticator A61, respectively, and each includes a signature by the root authenticator A30.

[0155] M06 is a certificate related to the ID of a processing entity such as a person or software module related to the service providing system A22, and includes the signature of the ID attribute authentication unit A31. Here, the processing entity includes a person in charge of development, operation, and deployment of the service providing system A22, and a software module that operates the construction and deployment device A01 and the system-related device A02.

[0156] M07 is a certificate regarding the attributes of processing subjects such as people and software modules involved in the service providing system A22, and includes the signature of the ID attribute authentication M02.

[0157] M08 is a certificate regarding the process verified by the process authenticator A41, and includes the signature of the process authenticator A41.

[0158] M09 is a certificate for data verified by data authenticator A51 and contains the certification of data authenticator A51.

[0159] M10 is a system certification unit A61 that certifies the service provision system A22. This is a certificate for a software module related to construction and deployment, and includes the signature of the system authentication unit A61. Here, the software module includes software modules that cause the construction and deployment device A01 and the system-related device A02 to function.

[0160] M11 is a certificate for the second service providing system A22 with which the first service providing system A22 cooperates, verified by the system authentication unit A61, and includes the signature of the system authentication unit A61. Here, the second service providing system A22 is a computer dependent on the first service providing system A22 whose verification result is indicated by M12.

[0161] For example, the second service providing system A22 may obtain data from the first service providing system A22 and transmit the processing results to the first service providing system A22, or may provide data to the first service providing system A22 for processing by the first service providing system A22.

[0162] In addition, if the service providing system A22 is not relied upon by other service providing systems, this certificate may not exist.

[0163] M12 is a certificate for the service providing system A22 verified by the system authentication unit A61. This certificate includes the signature of the system authentication unit A61, the verification result by the system authentication unit A61, the system identification means of the user, a group of identifiers of related data, a group of identifiers of related processes, and a group of identifiers of related processing subjects. It also includes other extension areas as necessary.

[0164] By referring to this certificate, users of the service providing system A22 can check the results of system verification by the system authentication unit A61. If necessary, they can check the results of verification of the people, modules, and other processing subjects, processes, and data involved in the development, construction, and deployment of the service providing system A22. If necessary, they can check the results of verification by the certification authority that performed those verifications.

[0165] Therefore, by trusting only the root certification and verifying the hierarchical certificate chain in the order of the solid arrows shown in Figure 13, the user can determine whether the target service providing system A22 has been verified and is problem-free.

[0166] Note that FIG. 13 shows a certificate chain, and in reality each certificate contains information such as an expiration date.

[0167] Next, as an example of the service providing system A22 described in the above embodiment, a case will be described in which content such as information about a railway line or advertisements is displayed on a monitor inside a vehicle such as a train or bus. In this case, the service providing system A22 updates the content once a day so that the content can be displayed even when the vehicle is moving and not connected to a communication network.

[0168] The content is stored in the data repository A10 and then included in the container by the build A11. In addition, a container image is created every time the content is updated.

[0169] When updating content, a person with the role of updating the content issues a commit request to reflect the updates in the content, and a person with the role of approving the content update checks and approves the content, and the updated content is reflected in data repository A10.

[0170] Container deployment is performed at fixed times every day, and also when some unexpected event occurs, at the request of a person with the role to deploy containers and with the approval of a person with the role to approve container deployment.

[0171] For the service providing system A22 that provides such information processing services, the authentication device A03 verifies the IDs, roles, etc. of the processing subjects involved in these processes, updates, and deployments, and issues certificates.

[0172] The authentication device A03 also stores a Uniform Resource Locator (URL) that indicates the location where the issued certificate is stored. The information processing service uses the encoded QR Code (registered trademark) to generate a QR Code and transmits it to a display monitor of a terminal (not shown) operated by a user of the information processing service.

[0173] By configuring in this way, the user can check the soundness of the service providing system A22.

[0174] Next, as another example of the service providing system A22 described in the above embodiment, a case where remote monitoring and monitoring of usage status of devices such as equipment and vehicles will be described.

[0175] In this case, the service providing system A22 issues a device certificate to the device to be monitored, and also issues a user certificate to each customer to whom the device is sold.

[0176] The service providing system A22 then collects data from the monitored devices in a state where the data is signed with the private keys of these two accounts.

[0177] The authentication device A03 can verify the signature of the data collected by the service providing system A22 to confirm that the data was collected from a legitimate device used by a legitimate customer.

[0178] In addition, by having the authentication device A03 verify the procedures used by the service providing system A22 to analyze data and create reports, customers can also verify that the data obtained from their own devices has been correctly processed and reflected in the report.

[0179] By configuring in this way, the user can check the soundness of the service providing system A22.

[0180] Next, an example of the overall configuration of an information processing system A00 according to this embodiment is shown in FIG.

[0181] FIG. 14 corresponds to the overall configuration example shown in FIG. 1, and shows that the construction and deployment device A01, system-related device A02, and authentication device A03 are connected and configured to be able to communicate with each other via a network 500 such as the Internet, a LAN (Local Area Network), or a telephone network.

[0182] Next, the hardware configuration of the construction and deployment device A01, the system-related device A02, and the authentication device A03 when they are implemented by physical computers will be described. Note that the construction and deployment device A01, the system-related device A02, and the authentication device A03 are not necessarily configured the same, but they have a common basic configuration, so they are shown together in FIG. 15 to avoid duplication.

[0183] Examples of computers that realize the construction and deployment device A01, the system-related device A02, and the authentication device A03 include personal computers, office computers, server devices, smartphones, tablets, and general-purpose computers (mainframes).

[0184] In addition, all or part of this computer may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, etc., such as a virtual server provided by a cloud system. In addition, all or part of the functions provided by this computer may be realized by a service provided by the cloud system via an API or the like, or may be realized by a service provided by a cloud system via a software as a service (SaaS), It may be realized by using PaaS (Platform as a Service), IaaS (Infrastructure as a Service), etc.

[0185] In addition, when the construction and deployment device A01, the system-related device A02, and the authentication device A03 are realized by a hypervisor-type virtual computer, a physical computer (not shown) executes virtualization software (not shown) for realizing the configuration shown in Fig. 15 by software. In this case, the configuration of this physical computer is the same as the configuration shown in Fig. 15.

[0186] <Authentication device> The authentication device A03 includes a CPU (Central Processing Unit) 310, a memory 320, and a communication It is configured with a device 330, a storage device 340, an input device 350, an output device 360 ​​and a recording medium reading device 370.

[0187] The CPU 310 is responsible for the overall control of the authentication device A03, and is a processor that realizes various functions of the authentication device A03 by reading out an authentication device control program 630, which is composed of codes for performing various operations related to this embodiment stored in the storage device 340, and various data into the memory 320 and executing or processing them.

[0188] For example, the CPU 310 executes or processes the authentication device control program 630 and various data, and by working in cooperation with hardware devices such as the memory 320, the communication device 330, and the storage device 340, various functions such as the root authentication unit A30, the ID attribute authentication unit A31, the process authentication unit A41, the data authentication unit A51, and the system authentication unit A61 are realized.

[0189] The CPU 310 may be configured using, for example, a Micro Processing Unit (MPU), a Graphics Processing Unit (GPU), a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Artificial Intelligence (AI) chip, etc.

[0190] The authentication device control program 630 is a general term for programs for implementing the functions of the authentication device A03, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, and the like that run on the authentication device A03.

[0191] The memory 320 can be configured by, for example, a semiconductor storage device. The memory 320 is a device that stores programs and data, and is, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), a Non-Volatile RAM (NVRAM), or the like.

[0192] The storage device 340 is a device that provides a physical storage area for storing various programs, data, tables, etc. The storage device 340 is, for example, a solid state drive (SSD). The storage device 340 includes a hard disk drive, an optical storage device (e.g., CD (Compact Disc), DVD (Digital Versatile Disc)), a storage system, an IC card, a read / write device for a non-transitory storage medium such as an SD card or an optical storage medium, a non-transitory storage area of ​​a cloud server, etc. The program and data can be read from another information processing device equipped with a recording medium or a non-transitory storage device. The program and data stored (memorized) in the storage device 340 are read into the memory 320 as needed.

[0193] In this embodiment, as shown in FIG. 18, the storage device 340 stores various data such as an authentication device control program 630, attribute rules A32, ID attribute authentication results A33, a process model A42, process authentication results A43, data quality rules A52, data authentication results A53, system rules A62, and system authentication results A63.

[0194] The storage device 340 may be built into the authentication device A03, or may be externally attached.

[0195] The recording medium reader 370 reads the programs and data recorded on a recording medium 800 such as a CD-ROM or a DVD, and stores them in the storage device 340 .

[0196] The communication device 330 is a device that realizes communication with other devices. The communication device 330 is a wired or wireless communication interface that realizes communication with other devices that comply with a predetermined communication protocol via the network 500, and is, for example, a NIC (Network Interface Card), a wireless communication module, or the like.

[0197] For example, the communication device 330 transmits and receives data and programs to and from other computers such as the construction and deployment device A01 and the system-related device A02 via a network 500 such as the Internet or a LAN (Local Area Network). For example, the above-mentioned authentication device control program 630 can be stored in another computer (not shown), and the authentication device A03 can download and execute the authentication device control program 630 from this computer.

[0198] In addition, the authentication device A03 may not have a memory device 340, and may instead realize its functions by using various data such as the above programs and tables stored in another computer (not shown) communicatively connected via the network 500.

[0199] The input device 350 is a device used for inputting data to the authentication device A03 by an operator or the like, and functions as a user interface. As the input device 350, for example, a keyboard, a mouse, a touch panel, a card reader, a pen input tablet, a microphone, etc. can be used.

[0200] The output device 360 ​​is a device for outputting information to the outside and functions as a user interface. The output device 360 ​​is, for example, a display device (liquid crystal display, LCD (Liquid Crystal Display), graphic card, etc.) that visualizes the above-mentioned various information, a device (audio output device (speaker, etc.)) that converts the above-mentioned various information into voice, and a device (printer, etc.) that converts the above-mentioned various information into text. For example, the authentication device A03 may be configured to input and output information to and from other devices via the communication device 330.

[0201] The input device 350 and the output device 360 ​​constitute a user interface that realizes interactive processing with the user (receiving information, providing information, etc.). The authentication device A03 may be implemented with, for example, an operating system, a file system, a DBMS (DataBase Management System) (relational database, NoSQL, etc.), a KVS (Key-Value Store), etc.

[0202] <Construction and deployment device> The construction and deployment device A01 includes a CPU 110, a memory 120, a communication device 130, a storage device 14, and a 0, an input device 150, an output device 160 and a recording medium reading device 170.

[0203] The CPU 110 is responsible for the overall control of the construction and deployment device A01, and is a processor that realizes the various functions of the construction and deployment device A01 described in this embodiment by reading out the construction and deployment device control program 610, which is composed of code for performing various operations related to this embodiment stored in the storage device 140, and various data into the memory 120 and executing or processing them.

[0204] For example, the CPU 110 executes or processes the construction and deployment device control program 610 and various data, and by working in cooperation with hardware devices such as the memory 120, communication device 130, and storage device 140, various functions such as the data repository A10, build A11, container repository A12, deployment A13, and process log A14 are realized.

[0205] The construction and deployment device control program 610 is a general term for programs for implementing the functions of the construction and deployment device A01, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, and the like that run on the construction and deployment device A01.

[0206] In this embodiment, as shown in FIG. 16, the storage device 140 stores various data such as a construction and deployment device control program 610, a data repository A10, a container repository A12, and a process log A14.

[0207] As described above, the construction and deployment device A01 has a common configuration with the authentication device A03, so a duplicated explanation will be omitted.

[0208] <System-related equipment> The system-related device A02 is configured to include a CPU 210, a memory 220, a communication device 230, a storage device 240, an input device 250, an output device 260, and a recording medium reading device 270.

[0209] The CPU 210 is responsible for the overall control of the system-related device A02, and is a processor that realizes the various functions of the system-related device A02 described in this embodiment by reading out a system-related device control program 620, which is composed of codes for performing various operations related to this embodiment stored in the storage device 240, and various data into the memory 220 and executing or processing them.

[0210] For example, the CPU 210 executes or processes the system-related device control program 620 and various data, and by working in cooperation with hardware devices such as the memory 220, the communication device 230, and the storage device 240, various functions such as the system platform A20, the deployment log A21, and the service providing system A22 are realized.

[0211] The system-related device control program 620 is a general term for programs for realizing the functions of the system-related device A02, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, etc. that run on the system-related device A02.

[0212] In this embodiment, as shown in FIG. 17, the storage device 240 stores various data such as a system-related device control program 620, a system platform A20, a deployment log A21, and a service providing system A22.

[0213] As described above, the system-related device A02 has a common configuration with the authentication device A03, so a duplicated description will be omitted.

[0214] The authentication device A03 according to the present embodiment, and the control method and program for the authentication device A03 have been described in detail above, but according to the present embodiment, it is possible to authenticate the service providing system A22 constructed to provide an information processing service. For example, it is possible to authenticate that the construction of the service providing system A22 is performed by a legitimate processing entity processing legitimate data in a legitimate procedure.

[0215] In addition, by enabling a third party to verify, through a chain of trust, the appropriateness of the process used to build and modify the service provision system A22 and whether or not elements have been tested, it becomes possible to determine whether the service provision system A22 is likely to return the expected results.

[0216] Furthermore, by issuing an electronic certificate to prove that the service providing system A22 is legitimately constructed, the user of the service providing system A22 can understand the status of the service providing system A22 by checking the electronic certificate issued by the authentication device A03. In this case, the user does not need to perform the verification himself, and only needs to trust the authentication device A03. Particularly in this embodiment, only the root authentication unit A30 needs to be trusted.

[0217] The above-described embodiment is for the purpose of facilitating understanding of the present invention, and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit of the present invention, and equivalents thereof are also included in the present invention.

[0218] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the programs, tables, and files that realize each function may be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or Alternatively, it may be placed on a recording medium such as an IC card, an SD card, or a DVD.

[0219] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0220] A00 Information Processing Systems A01 Construction and deployment device 110 CPU 120 Memory 130 Communication Equipment 140 Storage device 150 Input Device 160 Output Device 170 Recording medium reader A10 Data Repository A11 Build A12 Container Repository A13 deployment A14 Process Log A02 System related equipment 210 CPU 220 Memory 230 Communication Equipment 240 Storage device 250 Input Device 260 Output Device 270 Recording medium reader A20 System Platform A21 Deployment Log A22 Service provision system A03 Authentication device 310 CPU 320 Memory 330 Communication Equipment 340 Storage device 350 Input Device 360 Output Device 370 Recording medium reader A30 Root Authentication Unit A31 ID Attribute Authentication Part A32 Attribute Terms A33 ID attribute authentication result A41 Process Certification Department A42 Process Model A43 Process Authentication Results A51 Data authentication section A52 Data Quality Standards A53 Data authentication result A61 System Authentication Section A62 System Terms A63 System Authentication Result B00 Process log information C00 Deployment log information D00 ID authentication result information E00 Attribute authentication result information F00 Process authentication result information G00 Data authentication result information H00 System authentication result information M00 Certificate Chain 500 Network 610 Construction and deployment device control program 620 System-related device control program 630 Authentication device control program 800 Recording media

Claims

1. An authentication device that performs authentication of a service providing system that is configured to provide a predetermined information processing service by executing a service providing program, A processor and a memory, a data authentication unit that authenticates the validity of data used when constructing the service providing system, the data including the service providing program; an ID attribute authentication unit that authenticates the legitimacy of a processing entity that constructs the service providing system using the data; a process authentication unit that authenticates the validity of a procedure for constructing the service providing system; a system authentication unit that authenticates that the service providing system has been properly constructed when the authenticity of the data, the authenticity of the processing entity, and the authenticity of the procedure have been authenticated, and outputs a certificate for proving that the service providing system has been properly constructed; An authentication device comprising:

2. 2. The authentication device according to claim 1, a route authentication unit that authenticates the authenticity of the data authentication unit, the ID attribute authentication unit, the process authentication unit, and the system authentication unit; The authentication device further comprises:

3. 2. The authentication device according to claim 1, An authentication device, wherein the processing entity includes a software module that performs processing to construct the service provision system using the data, and a person in charge of performing work to construct the service provision system using the software module.

4. 2. The authentication device according to claim 1, The data includes, in addition to the service providing program, reference data used by the service providing program when providing the information processing service, and a configuration definition file that represents the configuration of the service providing system, an authentication device.

5. A method for controlling an authentication device that performs authentication on a service providing system that is configured to provide a predetermined information processing service by executing a service providing program, comprising the steps of: The authentication device, Authenticating the authenticity of data used in constructing the service providing system, including the service providing program; authenticating the legitimacy of a processing entity that uses the data to construct the service providing system; Authenticating the validity of a procedure for constructing the service providing system; certifying that the service providing system has been legitimately constructed when the legitimacy of the data, the legitimacy of the processing entity, and the legitimacy of the procedure have been authenticated; outputting a certificate for proving that the service providing system is legitimately constructed; A method for controlling an authentication device.

6. A control method for the authentication device according to claim 5, comprising: A control method for an authentication device, wherein the processing entity includes a software module that performs processing to construct the service provision system using the data, and a person in charge of performing work to construct the service provision system using the software module.

7. A control method for the authentication device according to claim 5, comprising: A control method for an authentication device, wherein the data includes, in addition to the service providing program, reference data used by the service providing program when providing the information processing service, and a configuration definition file that represents the configuration of the service providing system.

8. A program for causing a computer having a processor and a memory to execute authentication of a service providing system configured to provide a predetermined information processing service by executing a service providing program, The computer includes: a step of authenticating the validity of data used in constructing the service providing system, the data including the service providing program; a step of authenticating the legitimacy of a processing entity that constructs the service providing system using the data; a step of authenticating the validity of a procedure for constructing the service providing system; a step of authenticating that the service providing system is legitimately constructed when the authenticity of the data, the authenticity of the processing entity, and the authenticity of the procedure are authenticated; a step of outputting a certificate for proving that the service providing system is legitimately constructed; A program for executing.

9. The program according to claim 8, A program, wherein the processing entity includes a software module that performs processing to construct the service provision system using the data, and a person in charge of performing the work of constructing the service provision system using the software module.

10. The program according to claim 8, The data includes, in addition to the service providing program, reference data used by the service providing program when providing the information processing service, and a configuration definition file that represents the configuration of the service providing system.

Citation Information

Patent Citations

  • JP0000000011A

  • Method and device for accessing object and storage medium storing program controlling access to object

    JP1999282753A

  • Business information protection device, business information protection method, and program

    JP2016173851A

  • Virtual network system, virtual network control method, control device, and program thereof

    JP2020074604A