REMOTE AUTHORIZATION CONTROL SYSTEM, RESOURCE ACCESS DEVICE, AUTHENTICATION DEVICE, REMOTE AUTHORIZATION CONTROL METHOD, AND PROGRAM

Abstract

The present invention is a remote approval control system comprising a resource access device, a resource management device, and an authentication device, wherein the resource access device: downloads, from the authentication device, an access control list to a secure region of the resource access device; downloads, from the resource management device, a resource in the secure region; and, when a resource use request is received from a user, determines whether the resource can be used by the user on the basis of the access control list, and, if the resource can be used, allows the user to use the resource.

Description

[Technical field]

[0001] The present invention relates to a technique for controlling whether or not digital content can be used in the information and communications field. [Background technology]

[0002] As a technique for controlling whether or not digital content can be used, access control using DRM (Digital Rights Management) and an Access Control List (ACL) is known.

[0003] DRM is a mechanism for managing copyrights of digital content (hereafter referred to as resources). Users obtain encrypted resources through packages or distribution. The obtained resources are decrypted with a decryption key using browsing software on the user's terminal. The decryption key may be built into the browsing software or may be distributed from the network (Non-Patent Document 1).

[0004] In access control using ACLs, when a user attempts to view a resource, an access control list or the like is used to determine whether or not access is permitted. If access is permitted, the resource is downloaded from the server to the user's terminal and used (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] Wikipedia DRM https: / / en.wikipedia.org / wiki / Digital_rights_management (Retrieved 2021 / 1 / 7) [Non-Patent Document 2] Wikipedia Access-control list https: / / en.wikipedia.org / wiki / Access-control_list (Retrieved 2021 / 1 / 7) Summary of the Invention [Problem to be solved by the invention]

[0006] In conventional DRM, the decryption key is handed over to the user's device, which can lead to the problem that the decryption key is leaked through reverse engineering, etc., and the DRM function is no longer functional. In recent years, there has been technology to manage the key more safely by storing it in a secure area such as TEE (Trusted Execution Environment), but this is not a complete solution as there is still a possibility of the key being leaked through a side channel attack.

[0007] On the other hand, conventional access control based on ACLs requires resources to be downloaded when they are used, which can result in long download wait times when the resource data size is large.In addition, the need for processing on the cloud also poses the problem of low availability.

[0008] The present invention has been made in view of the above-mentioned points, and has an object to provide a resource availability control technology that is safer than conventional technologies and can reduce waiting times during use. [Means for solving the problem]

[0009] According to the disclosed technique, there is provided a remote authorization control system including a resource access device, a resource management device, and an authentication device, the resource access device downloads an access control list from the authentication device onto a secure area in the resource access device; The resource access device downloads resources from the resource management device onto the secure area; When the resource access device receives a resource use request from a user, Leave , The authentication device acquires an ID of the secure area by performing a remote attestation to the secure area, and when the authentication device successfully verifies the ID, the resource access device determining whether the user is permitted to use the resource based on the access control list, and allowing the user to use the resource if the user is permitted to use the resource; The resource is a weight parameter of a DNN executed in the resource access device, and when the resource is available, the weight parameter is set to the DNN. A remote authorization control system is provided. Effect of the Invention

[0010] According to the disclosed technology, a resource availability control technology is provided that is safer than conventional technologies and can reduce waiting times during use. [Brief description of the drawings]

[0011] [Figure 1] 1 is a system configuration diagram according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a configuration diagram of a resource access device. [Diagram 3] FIG. 2 is a configuration diagram of a resource management server. [Figure 4] FIG. 2 is a diagram illustrating the configuration of an authentication server. [Diagram 5] FIG. 1 is a system configuration diagram according to a first embodiment. [Figure 6] FIG. 2 is a sequence diagram according to the first embodiment. [Figure 7] FIG. 2 is a sequence diagram according to the first embodiment. [Figure 8] FIG. 2 is a sequence diagram according to the first embodiment. [Figure 9] FIG. 11 is a system configuration diagram according to a second embodiment. [Figure 10] FIG. 11 is a sequence diagram according to the second embodiment. [Figure 11] FIG. 11 is a sequence diagram according to the second embodiment. [Figure 12] FIG. 11 is a sequence diagram according to the second embodiment. [Figure 13] FIG. 2 is a diagram illustrating a hardware configuration of the device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention (the present embodiment) will be described with reference to the drawings. 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.

[0013] (Outline of the embodiment) Recent machines include a Trusted Execution Environment (TEE), which is a function that can safely execute critical processes independently of the OS. Such machines include not only servers but also terminals such as smartphones.

[0014] A machine with TEE functionality has a secure area (which may be called an Enclave) that does not leak data to the outside. In particular, TEEs such as Intel (registered trademark) SGX are provided with a mechanism (remote attestation) that guarantees to outside the secure area (for example, a remote user or server that communicates with the machine) that a correct program is running within the secure area. Note that the "remote attestation" used in this embodiment assumes the mechanism in Intel (registered trademark) SGX, but is not limited to this, and any mechanism with similar functionality may be used.

[0015] In this embodiment, the ACL (a list describing whether a user can access each resource) is managed on the TEE. Before a resource is viewed, the resource is downloaded into the secure area of ​​the TEE. However, at this point, the resource cannot be used.

[0016] After the ACL on the TEE has determined that the resource is available, the resource is sent outside the secure area and becomes available for use.

[0017] (System Configuration) A configuration example of a remote authorization control system according to the present embodiment is shown in Fig. 1. As shown in Fig. 1, the remote authorization control system according to the present embodiment includes a resource access device 100, a resource management device 200, an authentication device 300, and a user terminal 400, each of which is connected to a network. Note that, although the present embodiment shows a case in which the resource access device 100 and the user terminal 400 are separate devices, the user terminal 400 may have a configuration in which the function of the resource access device 100 is included therein.

[0018] Furthermore, the resource access device 100, the resource management device 200, and the authentication device 300 may be called a "Local Authorization & Resource Server", a "Central Resource Server", and a "Central Authorization Server", respectively.

[0019] The resource access device 100, the resource management device 200, and the authentication device 300 may each be a physical machine or a virtual machine on a cloud. It is assumed that the resource access device 100 is installed at the edge of a network or on a local network where a user exists.

[0020] The resource access device 100 is a device having a TEE, downloads an ACL from the authentication device 300, manages the ACL in a secure area of ​​the TEE, and executes resource access control using the ACL. The resource access device 100 can also execute any application such as a DNN (Deep Neural Network) in an environment outside the TEE. The environment outside the TEE may be called an REE (Rich Execution Environment).

[0021] The resource management device 200 manages resources. The authentication device 300 performs authentication processing, manages ACLs, and controls ACL issuance, etc. The user terminal 400 is a general terminal equipped with a browser, such as a PC or a smartphone.

[0022] (Example of device functional configuration) 2 shows an example of a functional configuration of the resource access device 100. As shown in FIG. 2, the resource access device 100 includes a secure area 110, a communication unit 120, a data storage unit 130, and a data processing unit 140.

[0023] The secure area 110 is the Enclave described above, and is a protected area where confidentiality is maintained. The contents of the data and programs in this area cannot be known from the outside. Outside the secure area 110, normal data storage, data processing (program execution), and transmission and reception can be performed.

[0024] In secure area 110, data can be stored and data processed (program execution) while maintaining confidentiality. In Fig. 2, a secure data storage unit 111 and a secure processing unit 112 are shown as functional units that perform these functions in secure area 110. As will be described later, an application 160 is executed in secure area 110. In addition, an application 150 is executed outside secure area 110.

[0025] The secure area 110 itself can be realized by existing technology. Any existing technology may be used to realize the secure area 110. For example, the secure area 110 may be realized as a separate chip that is independent in terms of hardware from the main CPU and memory, or the secure area 110 may be realized in terms of software by utilizing encryption technology and authentication technology. As a technology for realizing the secure area 110 in terms of software, for example, there is the above-mentioned SGX, and in this embodiment, it is assumed that SGX is used as an example.

[0026] The secure area 110 in this embodiment is an isolated execution environment that is dynamically started (generated) in the resource access device 100 by an instruction from a host application (an application that runs outside the secure area).

[0027] Fig. 3 shows a functional configuration diagram of the resource management device 200. As shown in Fig. 3, the resource management device 200 has an authentication processing unit 210, a resource control unit 220, and a resource storage unit 230. The authentication processing unit 210 performs remote attestation with respect to the secure area 110, mutual authentication with the authentication device 300, and the like.

[0028] Resources are stored in the resource storage unit 230. The resource storage unit 230 may be located outside the resource management device 200. The resource control unit 220 downloads resources and the like.

[0029] Fig. 4 shows a functional configuration diagram of the authentication device 300. As shown in Fig. 4, the authentication device 300 has an authentication processing unit 310, a data storage unit 320, an ACL control unit 330, and an ACL storage unit 340. The authentication processing unit 310 performs remote attestation for the secure area 110, mutual authentication with the resource management device 200, fraud detection using a user ID and a TEE ID, etc. The data storage unit 320 stores registration information and the like. Note that the data storage unit 320 may be located outside the authentication device 300.

[0030] The ACL is stored in the ACL storage unit 340. The ACL storage unit 340 may be located outside the authentication device 300. The ACL control unit 330 downloads the ACL.

[0031] Below, a first embodiment and a second embodiment will be described as more specific examples of the operation.

[0032] Example 1 5 is a configuration diagram of the first embodiment. Outside the secure area 110 (on the REE), an application 150 (hereinafter referred to as APP(REE) 150) operates, and the APP(REE) 150 executes request / response processing for the user terminal 400, generation of the secure area 110, communication with the secure area 110, etc. Also, within the secure area 110, an application 160 (hereinafter referred to as APP(TEE) 160) on a TEE operates, and the APP(TEE) 160 executes acquisition of ACLs and resources, access control by ACLs, etc.

[0033] The authentication device 300 downloads the ACL into the secure area 110 in the resource access device 100. In addition, the resource management device 200 downloads the resource into the secure area 110.

[0034] When a user terminal 400 requests a resource, access control using an ACL is performed by APP (TEE) 160 in the secure area 110 only if authentication by the authentication device 300 is successful, and if use of the resource is OK, the resource requested by the user is passed to APP (REE) 150, which then transmits the requested resource to the user terminal 400.

[0035] Hereinafter, detailed operations of the first embodiment will be described with reference to the sequences of Fig. 6 to Fig. 8. In the actual processing, a third-party verification organization that mediates remote attestation and a certification authority that certifies the validity of a public key are also used, but since these are common technologies, they are not described in the sequence.

[0036] <Initial registration operation> FIG. 6 shows the operations required for a user (user terminal 400) to use resources at the time of initial registration.

[0037] In S101, the user terminal 400 transmits a DRM initialization request to the resource access device 100. In S102, upon receiving the DRM initialization request, the APP (REE) 150 of the resource access device 100 generates a secure area 110. In the secure area 110, an APP (TEE) 160 that performs subsequent processing is started. In S103, the APP (TEE) 160 transmits a TEE initial registration request to the authentication device 300.

[0038] In S104, the authentication processing unit 310 of the authentication device 300 that has received the TEE initial registration request executes remote attestation for the secure area 110. Here, it is assumed that the remote attestation is successful. The following processing will also be described assuming that the remote attestation is successful.

[0039] The authentication processing unit 310 obtains the ID (referred to as TEE ID) of the secure area 110 by remote attestation, and stores it in the data storage unit 320 together with a public key (Attestation Public Key) corresponding to the signature key of the secure area 110 .

[0040] In addition to the above example, if the TEE ID and public key are registered in advance in the authentication device 300 (or registered in a specified server), in S103, the resource access device 100 may transmit the TEE ID to be used to the authentication device 300, and confirm that the TEE ID registered in the authentication device 300 is used.

[0041] In S105, the authentication processing unit 310 transmits a notification of completion of initial registration to the resource access device 100. In S106, the APP (TEE) 160 transmits a user initial registration request to the APP (REE) 150. In S107, the APP (REE) 150 transmits the user initial registration request to the user terminal 400.

[0042] In S108, the user terminal 400 transmits the user ID, the password, and information indicating consent (described as “ID / PW / Agreement”) to the resource access device 100. The information indicating consent is information indicating consent to linking and using the APP (REE) 150 and the APP (TEE) 160 of the secure area 110.

[0043] The ID / PW / agreement are passed from the APP (REE) 150 to the APP (TEE) 160, and are then transmitted from the APP (TEE) 160 to the authentication device 300 (S109, S110).

[0044] The authentication processing unit 310 of the authentication device 300 that has received the ID / PW / agreement stores the hash value of the user ID and password in the data storage unit 320. In the data storage unit 320, the TEE ID and the user ID are associated with each other, and a virtual table that combines the user ID and the TEE ID is configured. Note that a table that actually associates and stores the user ID and the TEE ID may be used.

[0045] In S111, the authentication processing unit 310 transmits a notification of the completion of the initial registration via the back channel to the resource access device 100. A notification of the completion of the DRM initialization is transmitted from the APP (TEE) 160 to the user terminal 400 via the APP (REE) 150.

[0046] <Operation when downloading resources before using them> FIG. 7 shows the operation up to the time when a resource is downloaded to the resource access device 100 before the user (user terminal 400) uses the resource.

[0047] In S121, the user terminal 400 transmits a DRM activation request to the resource access device 100. In S122, the APP (REE) 150 generates the secure area 110. Also, the APP (TEE) 160 that executes the subsequent processes in the secure area 110 is read and activated. Note that if the secure area 110 is activated, S122 is not necessary.

[0048] In S123, the APP (TEE) 160 transmits an access control list (ACL) request to the authentication device 300.

[0049] An ACL describing whether a user can access each resource is stored in the ACL storage unit 340 of the authentication device 300. The authentication processing unit 310 executes remote attestation for the secure area 110 in S124, and reads out the ACL from the ACL storage unit 340, attaches a signature to it, and transmits it to the APP (TEE) 160 in S125.

[0050] In S126, the APP (TEE) 160 that has received the signed ACL requests a public key for signature verification from the authentication device 300. In S127, the authentication processing unit 310 of the authentication device 300 transmits information on the public key to the APP (TEE) 160.

[0051] In S128, the APP (TEE) 160 verifies the signature of the ACL using the received public key. Here, it is assumed that the signature verification is successful. The following description will be given assuming that the signature verification is also successful.

[0052] In S129 and S130, the APP (TEE) 160 notifies the APP (REE) 150 and the user terminal 400 of the completion of DRM activation.

[0053] In S131, the user terminal 400 transmits a resource DL request to the resource access device 100. In the resource access device 100, the resource DL request is notified from the APP (REE) 150 to the APP (TEE) 160.

[0054] In S133, the APP (TEE) 160 transmits a resource DL request to the resource management device 200. In S134, the authentication processing unit 210 of the resource management device 200 executes remote attestation for the secure area 110 to obtain attestation information. In addition, the authentication processing unit 310 performs mutual TLS authentication with the authentication device 300 (S135).

[0055] The attestation information is information on the hardware and software used in the secure area 110 in the resource access device 100 to which a signature is attached.

[0056] In S136, the authentication processing unit 210 transmits the attestation information to the authentication device 300. This corresponds to a request for signature verification. The authentication processing unit 310 of the authentication device 300 verifies the attestation information using a public key (Attestation Public Key), and transmits the verification result (authentication result) to the resource management device 200 as the attestation result (S137).

[0057] Resources are stored in the resource storage unit 230 of the resource management device 200. When the authentication processing unit 210 of the resource management device 200 confirms the validity (authenticity) of the secure area 110 based on the attestation result of S137, the resource control unit 220 acquires the resources from the resource storage unit 230, attaches a signature to the resources, and transmits them to the APP (TEE) 160 (S138). In S139, the APP (TEE) 160 verifies the signature of the resources.

[0058] In S140, the APP (REE) 150 transmits a resource DL completion notification to the user terminal 400. In this state, since the resource is held in the secure area 110, the user terminal 400 cannot use the resource.

[0059] <Resource usage behavior> 8 shows the operation when a user (user terminal 400) uses a resource. In S151, the user terminal 400 transmits a resource use request to the resource access device 100.

[0060] In S152, the APP (REE) 150 transmits a resource use request to the APP (TEE) 160. Having received the resource use request, the APP (TEE) 160 transmits an authentication / authorization request to the APP (REE) 150. In S154, the APP (REE) 150 transmits an authentication / authorization request to the user terminal 400.

[0061] In S155, the user terminal 400 transmits the ID / PW / agreement to the resource access device 100. In S156, the APP (REE) 150 transmits the ID / PW / agreement to the APP (TEE) 160, and in S157, the APP (TEE) 160 transmits the ID / PW / agreement to the authentication device 300.

[0062] In S158, the authentication processing unit 310 of the authentication device 300 executes remote attestation for the secure area 110 and acquires the TEE ID of the secure area 110. The authentication processing unit 320 verifies the validity of the resource utilization request from the user (determines the presence or absence of fraud) by checking whether the user ID acquired in S157 and the TEE ID acquired in S158 are associated and stored in the data storage unit 320. This makes it possible to detect fraud when either the user ID (and password) or the TEE is used fraudulently.

[0063] Here, it is assumed that the above verification (authentication) is successful, and the authentication processing unit 310 transmits the authentication result to the APP (TEE) 160 in S159. In S160, the APP (TEE) 160 that has received the authentication result uses the ACL held in the secure area 110 to determine whether the resource requested by the user can be used.

[0064] Here, it is assumed that the resource is determined to be usable, and in S161, the APP (TEE) 160 transmits the resource to the APP (REE) 150. As a result, the resource is outside the secure area 110, and can be used by the user. Specifically, in S162, the APP (REE) 160 transmits the resource to the user terminal 400.

[0065] When the use of the resource in the user terminal 400 is finished, in S163, the user terminal 400 requests the APP (REE) 150 to delete the resource. As a result, the resource access device 100 deletes the resource outside the secure area 110, and in S164, a deletion completion notification is transmitted to the user terminal 400.

[0066] In the first embodiment, when a DNN is used as a resource, the DNN itself cannot be known from the outside because the DNN is held in the secure area 110. In other words, in the first embodiment, only the DNN execution result is known to the user, so that the intellectual property to be protected (here, the DNN) is protected.

[0067] Example 2 Next, a description will be given of Example 2. Fig. 9 is a configuration diagram of Example 2. Outside the secure area 110 (on the REE), an APP (REE) 150 operates, and performs request / response processing for the user terminal 400, generation of the secure area 110, communication with the secure area 110, etc.

[0068] In the second embodiment, the APP (REE) 150 executes inference using a DNN (Deep Neural Network). The weight parameters of the DNN correspond to "resources", which are called "states" in the second embodiment.

[0069] An APP (TEE) 160 on a TEE runs in the secure area 110, and the APP (TEE) 160 obtains ACLs and states, and performs access control based on the ACLs.

[0070] The authentication device 300 downloads the ACL into the secure area 110 in the resource access device 100. In addition, the state is downloaded into the secure area 110 from the resource management device 200. The ACL describes whether or not a user can access each DNN (that is, each state).

[0071] When the user terminal 400 requests to use the DNN, access control using the ACL is executed by the APP (TEE) 160 in the secure area 110 only when the authentication by the authentication device 300 is successful. When the DNN usage is permitted, the state is set to the DNN of the APP (REE) 150, and inference by the DNN using the state is executed, and the execution result is transmitted to the user terminal 400. Note that in the second embodiment, the DNN is used as the inference method, but a machine learning method other than the DNN may be used. The DNN is an example of a machine learning program.

[0072] Hereinafter, the detailed operations of the second embodiment will be described with reference to the sequences of FIGS. 10 to 12. Since the sequence of the second embodiment is basically the same as the sequence of the first embodiment, hereinafter, the differences from the first embodiment will be mainly described.

[0073] <Operation at initial registration> FIG. 10 shows the operations at initial registration required for the user (user terminal 400) to use the DNN. The processes of S201 to S213 are the same as the processes of S101 to S113 in the first embodiment (FIG. 6). Note that although the structure of the DNN is fixed at the time of generation of the secure area 110, the weight parameters (state) can be changed later.

[0074] <Operation when downloading the state before using the DNN> FIG. 11 shows the operations until the state is downloaded to the resource access device 100 before the user (user terminal 400) uses the DNN.

[0075] The processes of S221 to S240 in FIG. 11 are the same as those obtained by replacing "resource" with "state" in the processes of S121 to S140 in the first embodiment (FIG. 7).

[0076] <Operation when using the resource> Fig. 12 shows the operation when a user (user terminal 400) uses a DNN. The processing of S251 to S260 in Fig. 12 is the same as that of S151 to S160 in the first embodiment (Fig. 8) except that "resource" is replaced with "DNN". Note that the DNN usage request is an example of a resource usage request.

[0077] In S260, if it is determined that the user is allowed to use the DNN based on the ACL, in S261, the state is set to DNN and inference using the DNN is executed. In S262, the APP (REE) 150 transmits the result of the DNN execution to the user terminal 400.

[0078] When the use of the DNN in the user terminal 400 is completed, in S263, the user terminal 400 requests the APP (REE) 150 to delete the execution result. As a result, the execution result outside the secure area 110 is deleted in the resource access device 100, and in S264, a deletion completion notification is transmitted to the user terminal 400.

[0079] In the second embodiment, the state is held in the secure area 110 and is set in the DNN when it is used, so the state itself cannot be known from the outside. In other words, in the second embodiment, only the DNN execution result is known to the user, so that the intellectual property to be protected (here, the state) is protected.

[0080] (Hardware configuration example) The resource access device 100, the resource management device 200, and the authentication device 300 can all be realized by, for example, causing a computer to execute a program. This computer may be a physical computer or a virtual machine on the cloud. The resource access device 100, the resource management device 200, and the authentication device 300 are collectively referred to as "devices."

[0081] That is, the device can be realized by executing a program corresponding to the processing performed by the device, using hardware resources such as a CPU and memory built into a computer. The program can be recorded on a computer-readable recording medium (such as a portable memory) and stored or distributed. The program can also be provided via a network such as the Internet or email.

[0082] Fig. 13 is a diagram showing an example of the hardware configuration of the computer. The computer in Fig. 13 has a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, and the like, all of which are connected to one another via a bus BS. Note that some of these devices may not be included. For example, if no display is performed, the display device 1006 may not be included.

[0083] The program for realizing the processing on the computer is provided by a recording medium 1001 such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via a network. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.

[0084] The memory device 1003 reads out and stores the program from the auxiliary storage device 1002 when an instruction to start the program is received. The CPU 1004 realizes the functions related to the device in accordance with the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network, and functions as a transmitting unit and a receiving unit. The display device 1006 displays a GUI (Graphical User Interface) or the like according to a program. The input device 1007 is composed of a keyboard and mouse, buttons, a touch panel, or the like, and is used to input various operation instructions. The output device 1008 outputs the results of calculations.

[0085] (Effects of the embodiment) As described above, according to the technology of this embodiment, the minimum key required to realize the function is only the code signing key of the Trusted Application (an application that runs in the secure area 110), which is held in the resource management device 200 or the authentication device 300, and is not passed to the user terminal 400 (or an area accessible by the user in the resource access device 100). In this embodiment, the decryption key for the resource does not exist on the user terminal 400 (an area accessible by the user) as in conventional DRM, and the problem with conventional DRM that the decryption key may be leaked in the user terminal 400, etc. is resolved.

[0086] In addition, in this embodiment, resources are downloaded in advance onto the TEE of the resource access device 100, so that the download waiting time at the time of permission to use, which was a problem in the conventional access control method, can be significantly reduced, and availability is improved because edge processing can be performed instead of cloud processing. This is particularly effective when the data size of the resource is large.

[0087] (Summary of the embodiment) This specification discloses at least the following remote authorization control system, resource access device, authentication device, remote authorization control method, and program. (Section 1) A remote authorization control system including a resource access device, a resource management device, and an authentication device, the resource access device downloads an access control list from the authentication device onto a secure area in the resource access device; The resource access device downloads resources from the resource management device onto the secure area; When the resource access device receives a resource utilization request from a user, the resource access device determines whether the user is permitted to utilize the resource based on the access control list, and if the user is permitted to utilize the resource, the resource access device allows the user to utilize the resource. Remote authorization control system. (Section 2) the authentication device registers a user ID of the user in association with an ID of the secure area at the time of initial registration; When the user makes a resource utilization request, the presence or absence of fraud is determined by checking whether or not the user ID transmitted from the user and the ID of the secure area obtained from the resource access device are registered as registration information. 2. A remote authorization control system according to claim 1. (Section 3) The resource is a parameter of a machine learning program executed in the resource access device, and when the resource is available, the parameter is set in the machine learning program. 3. A remote authorization control system according to claim 1 or 2. (Section 4) A resource access device in a remote authorization control system including a resource access device, a resource management device, and an authentication device, means for downloading an access control list from the authentication device onto a secure area in the resource access device; means for downloading resources from the resource management device onto the secure area; a means for determining whether or not the user is permitted to use the resource based on the access control list when a resource use request is received from the user, and allowing the user to use the resource if the user is permitted to use the resource; A resource access device comprising: (Section 5) An authentication device in a remote authorization control system including a resource access device, a resource management device, and an authentication device, A means for registering a user ID of a user in association with an ID of a secure area in the resource access device at the time of initial registration; a means for determining whether or not there is any fraud by checking whether or not a user ID transmitted from the user and an ID of the secure area obtained from the resource access device are registered as registration information when the user makes a request to use the resource after the access control list and the resource are downloaded onto the secure area; An authentication device comprising: (Section 6) A remote authorization control method in a remote authorization control system including a resource access device, a resource management device, and an authentication device, comprising: downloading an access control list from the authentication device onto a secure area in the resource access device; The resource access device downloads resources onto the secure area from the resource management device; a step of, when the resource access device receives a resource utilization request from a user, determining whether the user is permitted to utilize the resource based on the access control list, and allowing the user to utilize the resource if the user is permitted to utilize the resource; A remote authorization control method comprising: (Section 7) A program for causing a computer to function as each of the means in the resource access device according to claim 4. (Section 8) A program for causing a computer to function as each of the means in the authentication device described in paragraph 5.

[0088] Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]

[0089] 100 Resource Access Device 110 Secure Area 111 Secure Data Storage 112 Secure Processing Unit 120 Communications Department 130 Data storage unit 140 Data Processing Unit 150 APP(REE) 160 APP(TEE) 200 Resource Management Device 210 Authentication processing unit 220 Resource Control Section 230 Resource Storage 300 Authentication Device 310 Authentication processing unit 320 Data Storage Unit 330 ACL control section 340 ACL storage section 400 User terminals 1000 Drive Device 1001 Recording media 1002 Auxiliary storage device 1003 Memory device 1004 CPU 1005 Interface device 1006 Display device 1007 Input Device 1008 Output device

Claims

1. A remote authorization control system including a resource access device, a resource management device, and an authentication device, the resource access device downloads an access control list from the authentication device onto a secure area in the resource access device; The resource access device downloads resources from the resource management device onto the secure area; When the resource access device receives a resource use request from a user, the authentication device acquires an ID of the secure area by performing remote attestation to the secure area, and when the authentication device successfully verifies the ID, the resource access device determines whether the user can use the resource based on the access control list, and when the user can use the resource, allows the user to use the resource; The resource is a weight parameter of a DNN executed in the resource access device, and if the resource is available, the weight parameter is set to the DNN. Remote authorization control system.

2. The authentication device registers a user ID of the user and an ID of the secure area in association with each other at the time of initial registration; When the user makes a resource utilization request, the presence or absence of fraud is judged by checking whether or not the user ID transmitted from the user and the ID of the secure area obtained from the resource access device are registered as registration information.

2. The remote authorization control system of claim 1.

3. A resource access device in a remote authorization control system including a resource access device, a resource management device, and an authentication device, a first means for downloading an access control list from the authentication device onto a secure area in the resource access device; means for downloading resources from the resource management device onto the secure area; a second means for, when receiving a resource utilization request from a user, determining whether or not the user is permitted to utilize the resource based on the access control list, and allowing the user to utilize the resource if the user is permitted to utilize the resource; When the second means receives the resource use request from the user, the authentication device acquires an ID of the secure area by performing remote attestation to the secure area, and when the authentication device succeeds in verifying the ID, the second means determines whether the user is permitted to use the resource based on the access control list, and when the user is permitted to use the resource, allows the user to use the resource; The resource is a weight parameter of a DNN executed in the resource access device, and if the resource is available, the weight parameter is set to the DNN. Resource access device.

4. An authentication device in a remote authorization control system including a resource access device, a resource management device, and an authentication device, A means for registering a user ID of a user and an ID of a secure area in the resource access device in association with each other at the time of initial registration; a means for determining whether or not there is fraud by checking whether or not a user ID transmitted from the user and an ID of the secure area obtained from the resource access device by performing remote attestation to the secure area are registered as registration information when the user makes a resource use request after an access control list and a resource are downloaded to the secure area, The resource is a weight parameter of a DNN executed in the resource access device, and the weight parameter is set to the DNN when the fraud is not present and the resource is available. Authentication device.

5. A remote authorization control method in a remote authorization control system including a resource access device, a resource management device, and an authentication device, comprising: downloading an access control list from the authentication device onto a secure area in the resource access device; The resource access device downloads resources onto the secure area from the resource management device; a step of, when the resource access device receives a resource use request from a user, the authentication device performs remote attestation to the secure area to obtain an ID of the secure area, and when verification by the authentication device using the ID is successful, the resource access device determines whether or not the user is permitted to use a resource based on the access control list, and when the user is permitted to use the resource, allows the user to use the resource; The resource is a weight parameter of a DNN executed in the resource access device, and if the resource is available, the weight parameter is set to the DNN. A method for remote authorization control.

6. A program for causing a computer to function as each of the means in the resource access device according to claim 3.

7. A program for causing a computer to function as each of the means in the authentication device according to claim 4.

Images