Resource access control method and related equipment

By introducing a credential consumption, i.e. invalidation mechanism in the resource access control system of the cloud computing platform, the security problems caused by failure to rotate or wait for failure after long-term or temporary identity credentials are leaked, and high security of resource access is achieved and reduced Attackers' risk of exploitation.

CN119071008APending Publication Date: 2024-12-03HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311075208.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2023-08-24
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In cloud computing platforms, when long-term or temporary identity credentials are not rotated in time or waited for failure after being leaked, the risk of attackers using leaked credentials is high, making it difficult to guarantee the security of resource access.

Method used

By introducing a voucher consumption, i.e. invalidation mechanism in the resource access control system, the resource access credentials are invalid after consumption. Even if the credential information is leaked, the authentication mechanism can find that it is invalid. The attacker cannot use the credentials to access resources to ensure resource security.

Benefits of technology

It effectively reduces the risk of attackers after credential leakage, ensures the security of resource access, is compatible with high-risk resources and scenarios, and meets the security needs of different businesses.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071008A_ABST
    Figure CN119071008A_ABST
Patent Text Reader

Abstract

The invention provides a resource access control method, which comprises the following steps that: an identity management node receives a credential acquisition request sent by a resource access party, sends a resource access credential to the resource access party according to the credential acquisition request, and records the state of the resource access credential, and the identity management node also receives a credential verification request sent by the resource access control node. The identity management node responds to the voucher verification request, checks the state of the resource access voucher, updates the state of the resource access voucher to be invalid when the state of the resource access voucher is valid, and sends a verification result indicating that verification is passed to the resource access control node, therefore, the resource access control node is allowed to access the resources of the resource owner. The resource access credential is invalid after consumption. Even if the information of the resource access credential is leaked, the authentication mechanism before resource access can discover that the resource access credential is invalid, and an attacker cannot access the resource by using the resource access credential, so that the security of the resource is ensured.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office of China on May 31, 2023, with application number 202310636249.0 and invention name “A resource access control method and related system”, all contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of cloud computing technology, and in particular to a resource access control method, an identity management node, a resource access control system, a computing device cluster, a computer-readable storage medium, and a computer program product. Background Art

[0003] With the continuous development of cloud computing, more and more developers choose to develop and deploy applications based on cloud platforms. Applications implemented based on cloud platforms involve a variety of resource access scenarios, including but not limited to cross-service resource access between microservices within an application and access to resources within the application by other applications. In order to ensure the security of resource access, fine-grained access control can usually be performed on resources.

[0004] The identity and access management (IAM) services of major cloud platforms currently provide identity credential management functions, which support the management of user and program identity credentials and resource access control policies based on identity credentials. Specifically, IAM services support the granting of long-term and temporary identity credentials for identity authentication and authorization when accessing resources.

[0005] Once a leak occurs during the validity period of the identity credential, it is necessary to promptly rotate the long-term identity credential or wait for the temporary identity credential to expire. However, if the valid identity credential is leaked and the long-term identity credential is not rotated or the temporary credential is not expired, the risk of the leaked identity credential being exploited by an attacker is high. Summary of the invention

[0006] The present application provides a resource access control method, where a resource access party granted with a resource access credential can consume the authorized resource access credential when using the resource access credential to access resources, and the resource access credential becomes invalid after consumption. At this point, even if the resource access credential information is leaked, the authentication mechanism before resource access can find that the resource access credential has expired, and the credential verification fails, so the attacker cannot use the resource access credential to access the resource, thereby ensuring the security of the resource. The present application also provides an identity management node, a resource access control system, a computing device cluster, a computer-readable storage medium, and a computer program product corresponding to the above method.

[0007] In a first aspect, the present application provides a resource access control method. The method can be applied to a resource access control system. The resource access control system is used to implement resource access control for a cloud platform. The resource access control system can be a software system, which can be deployed in a computing device cluster, and the computing device cluster executes the program code of the software system to execute the resource access control method provided by the present application. The resource access control system can also be a hardware system, for example, the resource access control system can be a computing device cluster with a resource access control function, and the computing device cluster executes the resource access control method of the present application when it is running.

[0008] The resource access control system includes an identity management node and a resource access control node. The identity management node receives a credential acquisition request sent by a resource access party, sends a resource access credential to the resource access party according to the credential acquisition request, and records the status of the resource access credential. Then the identity management node receives a credential verification request sent by the resource access control node. The credential verification request is generated by the resource access control node according to the resource access request sent by the resource access party. The credential verification request carries the resource access credential or the index information of the resource access credential. The identity management node can respond to the credential verification request, check the status of the resource access credential, and when the status of the resource access credential is valid, update the status of the resource access credential to invalid, and send a verification result indicating that the verification is passed to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

[0009] This method uses a mechanism whereby resource access credentials become invalid upon consumption. Even if the resource access credential information is leaked, the authentication mechanism before resource access can detect that the resource access credential has expired and the credential verification fails. Attackers will not be able to use the resource access credential to access resources, thus ensuring the security of resources.

[0010] In some possible implementations, the identity management node may also receive an access policy for a resource or access scenario configured by the resource owner, the access policy being used to indicate whether to enable the credential consumption invalidation mechanism. Accordingly, when the identity management node determines that the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates that the credential consumption invalidation mechanism is enabled, the status of the resource access credential is updated to invalid.

[0011] In this way, compatibility with existing mechanisms can be achieved, supporting users to enable the access control mechanism on demand for high-risk resources (defined by resource owners based on the impact of resource leakage, without limiting the resource risk level definition standard) or high-risk resource access scenarios, thereby meeting the needs of resource owners or resource access parties who have high security demands for resource access control security.

[0012] In some possible implementations, the access policy includes the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled. The identity management node may also receive a mapping relationship between a resource identifier and a risk level configured by the resource owner, or a mapping relationship between a scenario feature of a resource access scenario and a risk level. Accordingly, the identity management node may obtain the resource identifier of the target resource accessed by the resource access request, or obtain the scenario feature of the target access scenario corresponding to the resource access request, and determine the target risk level corresponding to the resource identifier of the target resource or the scenario feature of the target access scenario based on the resource identifier of the target resource or the scenario feature of the target access scenario. When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, the identity management node may determine that the access policy indicates that the credential consumption invalidation mechanism is enabled. In this way, resource access control based on the risk level of characters or access scenarios can be implemented to meet the needs of different businesses.

[0013] In some possible implementations, the scenario features include at least one of the following: public network access, cross-virtual private cloud (VPC) access, read access, or write access. For example, a public network read access scenario or a cross-VPC write access scenario usually has high security requirements. The method can extract scenario features, determine the risk level of the current access scenario based on the mapping relationship between scenario features and risk levels, and automatically determine whether to enable the credential consumption invalidation mechanism based on the risk level of the access scenario for enabling the credential consumption invalidation mechanism defined in the access policy and the risk level of the current access scenario, so as to meet the security requirements of different scenarios.

[0014] In some possible implementations, the identity management node may also receive a credential revocation request sent by the resource owner, wherein the credential revocation request is used to revoke the resource access credential. The identity management node may update the status of the resource access credential to invalid according to the credential revocation request.

[0015] This method also supports revoking resource access credentials to ensure the security of resources or resource access scenarios.

[0016] In some possible implementations, the identity management node may also receive the scenario characteristics of the credential revocation scenario sent by the resource owner. Accordingly, the identity management node may detect whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, the identity management node may update the status of the resource access credential to invalid. In this way, when the resource scenario meets the credential revocation scenario, the resource access credential can be automatically revoked to ensure the security of the resource or resource access scenario.

[0017] In some possible implementations, the identity management node may update the status of the resource access credential to invalid in a variety of ways. For example, the identity management node may delete the recorded information of the resource access credential, or update the status tag of the recorded resource access credential to invalid.

[0018] The identity management node can delete the recorded information of the resource access credential to invalidate the resource access credential, thereby reducing storage space usage and improving storage resource utilization. The identity management node can identify the status of the resource access credential through a status tag to facilitate query and improve query efficiency.

[0019] In a second aspect, the present application provides an identity management node. The node includes:

[0020] The identity and credential management module is used to receive a credential acquisition request sent by a resource access party, send a resource access credential to the resource access party according to the credential acquisition request, and record the status of the resource access credential;

[0021] A policy management module, configured to receive a credential verification request sent by a resource access control node, wherein the credential verification request is generated by the resource access control node according to a resource access request sent by the resource access party, and the credential verification request carries the resource access credential or index information of the resource access credential;

[0022] The policy management module is also used to check the status of the resource access credential in response to the credential verification request. When the status of the resource access credential is valid, the status of the resource access credential is updated to invalid through the identity and credential management module, and a verification result indicating that the verification is passed is sent to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

[0023] In some possible implementations, the policy management module is further configured to:

[0024] Receive an access policy for a resource or access scenario configured by a resource owner, wherein the access policy is used to indicate whether to enable a credential consumption invalidation mechanism;

[0025] The policy management module is specifically used for:

[0026] When it is determined that the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates enabling the credential consumption invalidation mechanism, the status of the resource access credential is updated to invalid through the identity and credential management module.

[0027] In some possible implementations, the access policy includes a risk level of a resource or access scenario for which a credential consumption invalidation mechanism is enabled;

[0028] The policy management module is also used for:

[0029] Receive a mapping relationship between a resource identifier and a risk level configured by the resource owner, or a mapping relationship between a scenario feature of a resource access scenario and a risk level;

[0030] The policy management module is specifically used for:

[0031] Obtaining a resource identifier of a target resource accessed by the resource access request, or obtaining a scenario feature of a target access scenario corresponding to the resource access request;

[0032] Determining a target risk level corresponding to the resource identifier of the target resource or the scenario feature of the target access scenario according to the resource identifier of the target resource or the scenario feature of the target access scenario;

[0033] When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, it is determined that the access policy indicates enabling the credential consumption invalidation mechanism.

[0034] In some possible implementations, the scene feature includes at least one of the following:

[0035] Public network access, cross-virtual private cloud (VPC) access, read access or write access.

[0036] In some possible implementations, the identity and credential management module is further used to:

[0037] Receiving a credential revocation request sent by a resource owner, wherein the credential revocation request is used to revoke the resource access credential;

[0038] According to the credential revocation request, the status of the resource access credential is updated to invalid.

[0039] In some possible implementations, the policy management module is further configured to:

[0040] Receive scenario characteristics of the credential revocation scenario sent by the resource owner;

[0041] Detect whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, update the status of the resource access credential to invalid through the identity and credential management module.

[0042] In some possible implementations, the identity and credential management module is specifically used to:

[0043] The recorded information of the resource access credential is deleted, or the status tag of the recorded resource access credential is updated to invalid.

[0044] In a third aspect, the present application provides a resource access control system. The resource access control system is used to implement resource access control for a cloud platform, and the resource access control system includes an identity management node and a resource access control node, and the identity management node is used to execute the method described in any implementation of the first aspect after the first aspect, so that the resource access control node allows access to resources of the resource owner.

[0045] In a fourth aspect, the present application provides a computing device cluster. The computing device cluster includes at least one computing device, and the at least one computing device includes at least one processor and at least one memory. The at least one processor and the at least one memory communicate with each other. The at least one processor is used to execute instructions stored in the at least one memory, so that the computing device or the computing device cluster executes the resource access control method as described in the first aspect or any implementation of the first aspect.

[0046] In a fifth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and the instructions instruct a computing device or a computing device cluster to execute the resource access control method described in the first aspect or any implementation of the first aspect.

[0047] In a sixth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computing device or a computing device cluster, enables the computing device or a computing device cluster to execute the resource access control method described in the first aspect or any one of the implementations of the first aspect.

[0048] Based on the implementations provided in the above aspects, this application can also be further combined to provide more implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical method of the embodiments of the present application, the drawings required for use in the embodiments are briefly introduced below.

[0050] Figure 1 A schematic diagram of the architecture of a resource access control system provided in an embodiment of the present application;

[0051] Figure 2 An interactive flow chart of a resource access control method provided in an embodiment of the present application;

[0052] Figure 3 A schematic diagram of a scenario of accessing high-risk resources across applications / services provided in an embodiment of the present application;

[0053] Figure 4 A schematic diagram of a high-risk scenario of accessing resources across applications / services provided in an embodiment of the present application;

[0054] Figure 5 A schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0055] Figure 6 A schematic diagram of the structure of a computing device cluster provided in an embodiment of the present application;

[0056] Figure 7 A schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application;

[0057] Figure 8 A schematic diagram of the structure of another computing device cluster provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The terms "first" and "second" in the embodiments of the present application are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features.

[0059] First, some technical terms involved in the embodiments of the present application are introduced.

[0060] Identity and Access Management (IAM) is a service that provides identity authentication, permission management, and access control. By using IAM to create and manage users and user groups, you can allow or deny users or user groups access to resources through authorization. Among them, the IAM service supports granting long-term identity credentials and temporary identity credentials (collectively referred to as identity credentials) for identity authentication and authorization when accessing resources.

[0061] The identity credential is the basis for identifying the user. The identity credential can include a password or an access key. Among them, the access key can include an access key identifier and a secret access key (Access Key ID / Secret Access Key, AK / SK). AK is used to identify the user's identity, and SK is used to sign and verify the request data to ensure the confidentiality, integrity and correctness of the requester's identity.

[0062] Credentials are usually set with an expiration date. If a credential is leaked during the validity period, it is usually necessary to process the credential to ensure the security of resource access. For example, long-term credentials can usually be rotated in a timely manner to prevent them from being exploited by attackers, and temporary credentials can usually be waited for to expire.

[0063] However, after the valid identity credentials are leaked, if the long-term identity credentials are not rotated or the temporary credentials are not expired, there is a high risk that the leaked identity credentials will be exploited by attackers. In view of this, the present application provides a resource access control method. The method can be executed by a resource access control system. Among them, the resource access control system is used to implement resource access control for the cloud platform. The resource access control system can be a software system, which can be deployed in a computing device cluster, and the computing device cluster executes the program code of the software system to execute the resource access control method provided by the present application. The resource access control system can also be a hardware system. For example, the resource access control system can be a computing device cluster with a resource access control function, and the computing device cluster executes the resource access control method of the present application when it is running.

[0064] Specifically, the resource access control system includes an identity management node and a resource access control node. The identity management node receives a credential acquisition request sent by a resource access party, sends a resource access credential to the resource access party according to the credential acquisition request, and records the status of the resource access credential. Then, the identity management node receives a credential verification request sent by the resource access control node. The credential verification request is generated by the resource access control node according to the resource access request sent by the resource access party. The credential verification request carries the resource access credential or index information of the resource access credential. The identity management node responds to the credential verification request, checks the status of the resource access credential, and when the status of the resource access credential is valid, updates the status of the resource access credential to invalid, and sends a verification result indicating that the verification is passed to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

[0065] In this way, when a resource access party that is granted a resource access credential uses the resource access credential to access resources, it will consume the authorized resource access credential, and the resource access credential will become invalid after consumption. At this point, even if the resource access credential information is leaked, the authentication mechanism before resource access can find that the resource access credential has expired, and the credential verification fails. The attacker will not be able to use the resource access credential to access resources, thus ensuring the security of resources.

[0066] The resource access control method of the present application can be applied to a variety of scenarios, including but not limited to cross-service resource access between microservices within an application, and resource access between applications (for example, access by other applications to resources within the application, also known as cross-application resource access). Among them, the application can be an application implemented based on a cloud platform (also known as a cloud application), or a local application. The method can achieve fine-grained access control of application resources.

[0067] In order to make the technical solution of the present application clearer and easier to understand, the architecture of the resource access control system of the present application is introduced below with reference to the accompanying drawings.

[0068] See also Figure 1 The schematic diagram of the architecture of the resource access control system shown in the figure, the resource access control system 10 includes an identity management node 100 and a resource access control node 200. Among them, the identity management node 100 and the resource access control node 200 can be physical nodes, for example, the identity management node 100 can be a server in a computing device cluster, and the resource control node 200 can be a gateway for interconnection in the computing device cluster. The gateway can be, for example, an application gateway, or an application programming interface (API) gateway. The identity management node 100 and the resource access control node 200 can also be logical nodes, for example, virtual machines or containers deployed with corresponding services or microservices.

[0069] In specific implementation, the identity management node 100 is used to receive a credential acquisition request sent by a resource access party (for example, an application or a microservice within an application), and then send a resource access credential to the resource access party based on the credential acquisition request, and record the status of the resource access credential.

[0070] The resource access control node 200 is used to receive a resource access request sent by a resource access party, generate a credential verification request according to the resource access request, and send the credential verification request to the identity management node 100. The credential verification request carries a resource access credential or index information of the resource access credential. The index information of the resource access credential is used to index to the resource access credential so as to obtain the resource access credential. For example, the index information can be the storage path of the resource access credential.

[0071] The identity management node 100 is also used to respond to a credential verification request, check the status of the resource access credential, and when the status of the resource access credential is valid, update the status of the resource access credential to invalid, and send a verification result indicating that the verification is passed to the resource access control node 200, so that the resource access control node 200 allows access to the resources of the cloud platform.

[0072] In some possible implementations, the identity management node 100 is also used to receive a credential revocation request sent by the resource owner. The credential revocation request is used to revoke the resource access credential. Specifically, the credential revocation request may carry the ID of the resource access credential, thereby requesting the revocation of the specified resource access credential. Alternatively, the credential revocation request may also carry the ID of the resource access party, thereby requesting the revocation of all resource access credentials granted to the resource access party. The identity management node 100 is also used to update the status of the resource access credential to invalid according to the credential revocation request.

[0073] Taking resource access security into consideration, the resource owner can also customize the credential revocation scenario, wherein the credential revocation scenario refers to a scenario in which the resource access credential needs to be revoked (i.e., authorization needs to be revoked), so that when the scenario characteristics of the resource access scenario match the characteristics of the above-mentioned credential revocation scenario, the resource access credential is automatically revoked. Specifically, the identity management node 100 is also used to receive the scenario characteristics of the credential revocation scenario sent by the resource owner. For example, the scenario characteristics may be that the number of resource access requests carrying the same resource access credential received per unit time reaches a preset value, or the source address of the resource access request carrying the resource access credential does not belong to the target network segment. The identity management node 100 detects whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, the status of the resource access credential is updated to invalid.

[0074] The identity management node 100 may include an identity and credential management module 102 and a policy management module 104. The identity and credential management module 102 has at least one of identity management, identity authentication, authorization record, and credential management functions, and the policy management module 104 has at least one of policy management and policy authentication functions. Policy management refers to maintaining resource access control policies, such as resource access control policies configured by resource owners, and the resource access control policies include but are not limited to resource access control that enables a credential consumption invalidation mechanism.

[0075] The functions of the identity and credential management module 102 and the policy management module 104 are described in detail below.

[0076] The identity and credential management module 102 includes identity management, identity authentication, authorization record and credential management functions.

[0077] The identity management function of the identity and credential management module 102 includes identity registration and identity deregistration. Specifically, the identity and credential management module 102 is used to receive a registration request from a user (e.g., an application or a service or microservice within an application), and in response to the registration request, store the user's identity information, which is usually unique. The identity and credential management module 102 is also used to receive a deregistration request from the user, and in response to the deregistration request, delete the user's identity information.

[0078] The identity authentication function of the identity and credential management module 102 includes identity information consistency verification. Specifically, when the identity and credential management module 102 receives a resource access request sent by a resource access party, it verifies the consistency between the identity information in the resource access request and the stored identity information, so as to decide whether to issue a resource access credential.

[0079] The credential management function of the identity and credential management module 102 includes the issuance, expiration or revocation of resource access credentials. Specifically, the identity and credential management module 102 is used to grant resource access credentials when identity authentication is passed, for example, when identity information consistency verification is passed. Furthermore, the identity and credential management module 102 is also used to update the status of the resource access credential to invalid after consuming the resource access credential, or when receiving a credential revocation request for revoking the resource access credential, update the status of the resource access credential to invalid according to the credential revocation request.

[0080] The authorization recording function of the identity and credential management module 102 includes recording the status of the resource access credentials granted. Specifically, the identity and credential management module 102 is used to record the status of the resource access credentials when granting the resource access credentials. In some examples, such as Figure 1 As shown, the identity and credential management module 102 can record the identity (e.g., ID) of the resource access party (application or microservice within the application) and the corresponding resource access credential information, thereby recording the status of the resource access credential. Further, the identity and credential management module 102 can check whether the status of the resource access credential is valid. If valid, the resource access credential can be consumed and the status of the resource access credential can be updated to invalid. Similarly, when a credential revocation request is received, the identity and credential management module 102 can update the status of the resource access credential to invalid.

[0081] The policy management function of the policy management module 104 includes maintaining the resource access control policy defined by the resource owner (resource owner). Specifically, the policy management module 104 is used to receive the resource access control policy defined by the resource owner (resource owner), and then store the resource access control policy. The policy management module 104 is also used to update or delete the resource access control policy when receiving a policy update request or a policy deletion request. Further, the policy management module 104 is also used to receive the scenario characteristics of the credential revocation scenario defined by the resource owner. If the scenario characteristics of the resource access scenario match the scenario characteristics of the credential revocation scenario, the identity and credential management module 102 can be instructed to revoke the resource access credential.

[0082] The policy authentication function of the policy management module 104 includes authentication according to the defined resource access control policy. For example, the policy management module 104 is used to receive a credential verification request sent by a resource access control node, and in response to the credential verification request, check the status of the resource access credential. When the status of the resource access credential is valid, the status of the resource access credential is updated to invalid through the identity and credential management module 102, and a verification result indicating that the verification is passed is sent to the resource access control node 200, so that the resource access control node allows access to the resources of the resource owner. In some possible implementations, the policy management module 104 is also used to update the status of the resource access credential to invalid when the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates that the credential consumption invalidation mechanism is enabled.

[0083] based on Figure 1 The resource access control system 10 shown in the figure, the present application also provides a resource access control method. The resource access control method of the present application is introduced below in conjunction with an embodiment.

[0084] See also Figure 2 The flowchart of a resource access control method shown is applied to a resource access control system 10. The resource access control system 10 is used to implement resource access control on a cloud platform. The resource access control system 10 includes an identity management node 100 and a resource access control node 200. The method includes the following steps:

[0085] S202: The identity management node 100 receives a credential acquisition request sent by a resource access party.

[0086] The resource access party can be the application that initiates resource access or the microservice within the application. For example, when application A is the initiator and requests to access the resources of application B, application A is the resource access party and application B is the resource owner. For another example, when microservice 1 in application A is the initiator and requests to access the resources of microservice 2, microservice 1 is the resource access party and microservice 2 is the resource owner. The resources of the application or microservice can be data or interface resources.

[0087] The credential acquisition request is used to request the identity management node 100 to grant a resource access credential. The credential acquisition request may carry the identity information of the resource access party (also referred to as the resource requester). The identity information may include an identity identifier, such as an application or microservice ID. The identity information may be used to authenticate the identity of the resource access party.

[0088] It should be noted that a credential acquisition request can be used to request one or more resource access credentials. Multiple resource access credentials can be used for one resource access request or for multiple resource access requests (for example, each resource access request uses one of the multiple resource access credentials).

[0089] S204: The identity management node 100 sends the resource access credential to the resource access party according to the credential acquisition request.

[0090] Specifically, the identity management node 100 can parse the credential acquisition request to obtain the identity information of the resource access party, and then the identity management node 100 can verify the identity information of the resource access party. For example, the identity management node 100 can verify the consistency of the identity information in the credential acquisition request with the identity information stored by the identity management node 100. When the identity authentication is passed, the identity management node 100 can generate a resource access credential and send the resource access credential to the resource access party.

[0091] Resource access credentials are specifically credentials used to access resources, such as identity credentials. Resource access credentials can be in the form of tokens. Resource access credentials can also be set with a validity period, which can be set according to business needs. For resources or resource access scenarios that enable the credential consumption expiration mechanism, the validity period of the resource access credential can be set to a shorter time. For resources or resource access scenarios that do not enable the credential consumption expiration mechanism, the validity period of the resource access credential can be set to a longer time.

[0092] S206. The identity management node 100 records the status of the resource access credential.

[0093] The status of the resource access credential includes valid or invalid. When the resource access credential is in invalid status, it means that the resource access credential can no longer be used to access the resource. When the identity management node 100 grants the resource access credential, the status of the resource access credential can be recorded as valid.

[0094] The identity management node 100 can record the status of the resource access credential by the existence of the resource access credential. For example, the identity management node 100 can record the ID of the resource access party and the ID of the resource access credential granted to the resource access party. When the ID of the specified resource access credential is found, it means that the status of the specified resource access credential is valid. When the ID of the specified resource access credential is not found, it means that the status of the specified resource access credential is invalid.

[0095] The identity management node 100 may also record the status of the resource access credential through an additional status tag. For example, the identity management node 100 may record the ID of the resource access party and the ID of the resource access credential granted to the resource access party, and the status tag of the resource access credential granted to the resource access party. When the status tag of one or more resource access credentials corresponding to the ID of the resource access party is valid, it means that the status of the corresponding resource access credential is valid.

[0096] S208: The resource access control node 200 receives a resource access request sent by a resource access party.

[0097] S210: The resource access control node 200 generates a credential verification request according to the resource access request.

[0098] S212 : The resource access control node 200 sends a credential verification request to the identity management node 100 .

[0099] The resource access party may initiate a resource access request to the resource owner based on the obtained resource access credential. The resource access request may carry the resource access credential or the index information of the resource access credential. The index information of the resource access credential is used to index the resource access credential, for example, the index information may be a storage path.

[0100] The resource access control node 200 can obtain the resource access request sent by the resource access party so as to verify the resource access credential presented by the resource access party, thereby making a decision to allow or reject the resource access request. The resource access control node 200 can execute S210 to S212 to request the identity management node 100 to assist in completing the verification of the resource access credential.

[0101] In some possible implementations, the resource access control node 200 may also first verify the legitimacy of the resource access credential based on the resource access request. For example, the resource access control node 200 verifies the signature carried in the resource access request through a public key, and when the verification is successful, it indicates that the resource access credential is legal. The resource access control node 200 may execute the above S210 to S212 when the legitimacy verification is successful.

[0102] Furthermore, the resource access control node 200 can also verify the authority of the resource access party (also known as authentication). For example, the resource access control node 200 can authenticate itself, or request the identity management node 100 to assist in authentication. In some examples, the credential verification request can not only request resource access credential verification (which can be consumed if verified), but also request authentication. In other examples, the resource access control node 200 can also generate an authentication request and send the authentication request to the identity management node 100.

[0103] S214: The identity management node 100 checks the status of the resource access credential. When the status of the resource access credential is valid, S216 is executed.

[0104] Specifically, the identity management node 100 can search for the resource access credential information corresponding to the resource accessor ID in the resource access request to obtain the resource access credential status. Depending on the status recording method, the resource access credential information searched by the identity management node 100 can be different.

[0105] In some possible implementations, when the identity management node 100 uses the existence of resource access credential information (e.g., the ID of the resource access credential) to characterize the status of the resource access credential, the identity management node 100 can search for the ID of the resource access credential corresponding to the ID of the resource accessor. If the search is successful, it indicates that the status of the resource access credential is valid. If the search fails, it indicates that the status of the resource access credential is invalid.

[0106] In some other possible implementations, when the identity management node 100 uses the status tag of the resource access credential to represent the status of the resource access credential, the identity management node 100 can search for the status tag of the resource access credential corresponding to the ID of the resource accessor. When the status tag is valid, it means that the status of the resource access credential is valid; when the status tag is invalid, it means that the status of the resource access credential is invalid.

[0107] S216: The identity management node 100 updates the status of the resource access credential to invalid.

[0108] When the resource access credential is valid, the identity management node 100 can consume the resource access credential and update the resource access credential to invalid. According to different ways of recording the resource access credential status, the identity management node 100 supports updating the resource access credential to invalid in different ways.

[0109] In some possible implementations, when the identity management node 100 uses the existence of resource access credential information (such as the ID of the resource access credential) to characterize the status of the resource access credential, the identity management node 100 may delete the recorded resource access credential information (such as the ID of the resource access credential), thereby updating the status of the resource access credential to invalid.

[0110] In some other possible implementations, when the identity management node 100 uses the status tag of the resource access credential to represent the status of the resource access credential, the identity management node 100 may update the status tag of the recorded resource access credential to invalid.

[0111] Furthermore, when the identity management node 100 receives an authentication request sent by the resource access control node 200, or the credential verification request received by the identity management node 100 is also used for authentication, the identity management node 100 can also authenticate the resource access party. For example, the identity management node 100 can obtain the access permission set of the resource requested by the resource access party, and then the identity management node 100 determines whether the identity information of the resource access party is matched in the access permission set, thereby determining the access permission of the resource access party.

[0112] Considering that not all scenarios or all resources enable the credential consumption invalidation mechanism, the identity management node 100 may also receive the access policy of the resource or access scenario configured by the resource owner, and the access policy is used to indicate whether the credential consumption invalidation mechanism is enabled. Accordingly, the identity management node 100 may update the status of the resource access credential to invalid when it is determined that the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates that the credential consumption invalidation mechanism is enabled.

[0113] Among them, the access policy includes the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled. The identity management node 100 also receives the mapping relationship between the resource identifier and the risk level configured by the resource owner, or the mapping relationship between the scenario characteristics of the resource access scenario and the risk level. Accordingly, the identity management node 100 obtains the resource identifier of the target resource accessed by the resource access request, or obtains the scenario characteristics of the target access scenario corresponding to the resource access request, the scenario characteristics including but not limited to one or more of public network access, cross-virtual private cloud (VPC) access, read access or write access, and then determines the target risk level corresponding to the resource identifier of the target resource or the scenario characteristics of the target access scenario according to the resource identifier of the target resource or the scenario characteristics of the target access scenario. When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, the identity management node 100 determines that the access policy indicates to enable the credential consumption invalidation mechanism.

[0114] S218 . The identity management node 100 sends a verification result indicating that the verification is successful to the resource access control node 200 .

[0115] The verification result is used to indicate that the resource access credential is valid and has been consumed successfully. Further, when the resource access control node 200 also requests the identity management node 100 for authentication, the identity management node 100 may also send the authentication result. The verification result and the authentication result may be sent through the same message or through different messages, which is not limited in this embodiment.

[0116] S220 : The resource access control node 200 allows access to resources of the resource owner.

[0117] The resource access control node 200 determines that the resource access credential is verified (consumption is successful), and the resource access party can be allowed to access the resources of the resource owner. Further, the resource access control node can allow the resource access party to access the resources of the resource owner when it is determined that the resource access credential is verified and the authentication is passed. When the resource access control node 200 determines that the resource access credential is invalid (consumption failure) or the authentication fails, the resource access party can be denied access to the resources of the resource owner, that is, resource access is not allowed.

[0118] Based on the above description, it can be seen that the resource access party who is granted a resource access credential can consume the authorized resource access credential when using the resource access credential to access resources, and the resource access credential will become invalid after consumption. At this time, even if the resource access credential information is leaked, the authentication mechanism before resource access can find that the resource access credential has expired and the credential verification fails. The attacker will not be able to use the resource access credential to access resources, thus ensuring the security of resources.

[0119] Next, the resource access control method of the present application is described in combination with different scenarios.

[0120] First, the resource access control method in the scenario of cross-application / service access to high-risk resources is described in detail.

[0121] See also Figure 3 , the resource owner can complete identity and policy management in advance in the functional module that provides IAM services, such as the identity and credential management module 102. Specifically, the resource owner classifies and manages the resources, defines the risk level of the resources according to the impact of different resource leaks, and defines the risk level of the resources that need to enable the credential consumption invalidation mechanism when accessed. The resource owner can also register an API in the resource access control node 200 (such as an API gateway) to provide resource access capabilities. The resource access party completes identity and permission management in the functional module that provides IAM services, such as the identity and credential management module 102.

[0122] After completing the above preparations, you can execute the following resource access control method, which includes the following steps:

[0123] Step 1: The resource access party sends a credential acquisition request to the identity management node 100.

[0124] Step 2: The identity and credential management module 102 of the identity management node 100 receives the credential acquisition request, verifies the identity information of the resource access party, grants the resource access credential if the verification is successful, and records the status of the granted resource access credential.

[0125] The identity management node 100 represents the status of the resource access credential by recording the information of the resource access credential. Figure 3 As shown, the identity management node 100 can record the ID of the resource access party and the ID of the corresponding resource access credential. For example, the ID of the resource access party is Id1, and the ID of the corresponding resource access credential can be X1, X2; the ID of the resource access party is Id2, and the ID of the corresponding resource access credential can be Y1, Y2, Y3.

[0126] Step 3: The resource access party sends a resource access request.

[0127] The resource access request may be a resource access API call request. The resource access party may call the resource access API with the resource access credentials.

[0128] Step 4: The resource access control node 200 verifies the legitimacy of the resource access credential, and sends a credential verification request to the identity management node 100 when the legitimacy verification passes.

[0129] The verification request is used to request to check the status of the resource access credential, and then consume the resource access credential. In some examples, the verification request is also used to verify the authority of the resource access party.

[0130] Step 5: The identity management node 100 determines whether the resource access credential exists. If the resource access credential exists, the resource access credential is invalidated. If the resource access credential does not exist, the resource access control node 200 is notified that the resource access credential is invalidated.

[0131] The identity management node 100 may delete the information of the resource access credential to invalidate the resource access credential, or the identity management node 100 may update the status tag of the resource access credential to invalid.

[0132] The identity management node 100 can obtain the resource requested by the resource access party and determine whether the risk level of the resource is the risk level of the resource defined by the resource owner that requires the credential consumption invalidation mechanism to be enabled when accessed. If so, the identity management node 100 can invalidate the resource access credential when checking that the status of the resource access credential is valid.

[0133] Step 6: The identity management node 100 completes authentication based on the access control policy.

[0134] Step 7: If the resource access control node 200 determines that the resource access credential has been verified and the authentication has been passed, resource access is allowed; if it is determined that the resource access credential is invalid or the authentication has failed, resource access is denied.

[0135] Next, the resource access control method in the high-risk scenario of cross-application / service access to resources is described in detail.

[0136] See also Figure 4 , the resource owner can complete identity and policy management in advance in the functional module that provides IAM services, such as the identity and credential management module 102. Specifically, the resource owner classifies and manages resource access scenarios, defines the risk level of resource access scenarios according to the impact of different resource access scenarios, and defines the risk level of resource access scenarios that require the activation of consumption invalidation mechanisms. The resource owner can also register an API at the resource access control node 200 (such as an API gateway) to provide resource access capabilities. The resource access party completes identity and authority management in the functional module that provides IAM services, such as the identity and credential management module 102.

[0137] After completing the above preparations, you can execute the following resource access control method, which includes the following steps:

[0138] Step 1: The resource access party sends a credential acquisition request to the identity management node 100.

[0139] Step 2: The identity and credential management module 102 of the identity management node 100 receives the credential acquisition request, verifies the identity information of the resource access party, grants the resource access credential if the verification is successful, and records the status of the granted resource access credential.

[0140] Step 3: The resource access party sends a resource access request.

[0141] Step 4: The resource access control node 200 verifies the legitimacy of the resource access credential, and sends a credential verification request to the identity management node 100 when the legitimacy verification passes.

[0142] The above steps 1 to 4 can refer to Figure 3 The description of the related contents of the illustrated embodiment will not be repeated here.

[0143] Step 5: The identity management node 100 determines whether the resource access credential exists. If the resource access credential exists, the resource access credential is invalidated. If the resource access credential does not exist, the resource access control node 200 is notified that the resource access credential is invalidated.

[0144] In specific implementation, the identity management node 100 can obtain the scenario characteristics of the target access scenario corresponding to the resource access party request, such as write access and cross-VPC access, and then the identity management node 100 determines the target risk level corresponding to the scenario characteristics of the target access scenario based on the scenario characteristics of the target access scenario. When the risk level of the access scenario in which the credential consumption invalidation mechanism is enabled includes the target risk level, the identity management node 100 determines that the access policy indicates that the credential consumption invalidation mechanism is enabled. In this example, the risk level of the cross-VPC write access scenario is a high level, and the risk level of the access scenario in which the credential consumption invalidation mechanism is enabled includes a high level, so the identity management node 100 determines that the access policy indicates that the credential consumption invalidation mechanism is enabled.

[0145] Based on this, when the identity management node 100 detects the existence of the resource access credential, it deletes the resource access credential, thereby invalidating the resource access credential. It should be noted that in other possible implementations of the embodiment of the present application, the identity management node 100 may also update the status tag of the resource access credential to invalid, thereby invalidating the resource access credential.

[0146] Step 6: The identity management node 100 completes authentication based on the access control policy.

[0147] Step 7: If the resource access control node 200 determines that the resource access credential has been verified and the authentication has been passed, resource access is allowed; if it is determined that the resource access credential is invalid or the authentication has failed, resource access is denied.

[0148] Based on the above description, it can be known that the resource access control method of the present application can implement the issuance and granting of resource access credentials according to its own functional mechanism, and record the information of the granted resource access credentials (for example, the status of the resource access credentials). The resource access party that is granted the credentials will consume the authorization credential information when using the resource access credentials to access resources, and the resource access credentials will become invalid after consumption. At this point, even if the resource access credentials are leaked, the attacker cannot use the resource access credentials to access resources, and the authentication mechanism before resource access can find that the credentials have expired and the authentication has failed. This ensures the security of resource access.

[0149] In addition, the resource access method of the present application is compatible with existing mechanisms, supporting users to enable the access control mechanism on demand for high-risk resources (defined by resource owners based on the impact of resource leakage, without limiting the resource risk level definition standard) or high-risk resource access scenarios (such as cross-VPC, access to VPC from the public network, etc., the risk level of the resource access scenario can be defined by the resource owner or policy manager, without limiting the risk level definition standard of the resource access scenario). This can meet the needs of resource owners or resource access parties who have high security demands for resource access control security.

[0150] Based on the aforementioned resource access control method, the present application further provides an identity management node 100. The identity management node 100 will be introduced below from the perspective of functional modularization.

[0151] See also Figure 1 The structure diagram of an identity management node 100 is shown, and the identity management node 100 includes:

[0152] The identity and credential management module 102 is used to receive a credential acquisition request sent by a resource access party, send a resource access credential to the resource access party according to the credential acquisition request, and record the status of the resource access credential;

[0153] The policy management module 104 is used to receive a credential verification request sent by a resource access control node, wherein the credential verification request is generated by the resource access control node according to the resource access request sent by the resource access party, and the credential verification request carries the resource access credential or the index information of the resource access credential;

[0154] The policy management module is also used to check the status of the resource access credential in response to the credential verification request. When the status of the resource access credential is valid, the status of the resource access credential is updated to invalid through the identity and credential management module, and a verification result indicating that the verification is passed is sent to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

[0155] Exemplarily, the identity and credential management module 102 and the policy management module 104 may be implemented by hardware or software.

[0156] Among them, when implemented by software, the identity and credential management module 102 and the policy management module 104 can be applications running on computer devices, such as computing engines, etc. The application can be provided to users in the form of virtualized services. Virtualization services may include virtual machine (VM) services, bare metal server (BMS) services, and container services. Among them, VM services can be services that virtualize virtual machine (VM) resource pools on multiple physical hosts (such as computing devices) through virtualization technology to provide users with VMs on demand for use. BMS services are services that virtualize BMS resource pools on multiple physical hosts to provide users with BMS on demand for use. Container services are services that virtualize container resource pools on multiple physical hosts to provide users with containers on demand for use. VM is a simulated virtual computer, that is, a logical computer. BMS is a high-performance computing service that can be elastically scalable, and its computing performance is no different from that of traditional physical machines, and it has the characteristics of secure physical isolation. Containers are a kernel virtualization technology that can provide lightweight virtualization to achieve the purpose of isolating user space, processes, and resources. It should be understood that the VM service, BMS service and container service in the above-mentioned virtualization services are merely specific examples. In actual applications, the virtualization service may also be other lightweight or heavyweight virtualization services, which are not specifically limited here.

[0157] When implemented by hardware, the identity and credential management module 102 and the policy management module 104 may include at least one computing device, such as a server, etc. Alternatively, the identity and credential management module 102 and the policy management module 104 may also be implemented by using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0158] In some possible implementations, the policy management module 104 is further configured to:

[0159] Receive an access policy for a resource or access scenario configured by a resource owner, wherein the access policy is used to indicate whether to enable a credential consumption invalidation mechanism;

[0160] The policy management module 104 is specifically used for:

[0161] When it is determined that the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates enabling the credential consumption invalidation mechanism, the status of the resource access credential is updated to invalid through the identity and credential management module 102.

[0162] In some possible implementations, the access policy includes a risk level of a resource or access scenario for which a credential consumption invalidation mechanism is enabled;

[0163] The policy management module 104 is also used for:

[0164] Receive a mapping relationship between a resource identifier and a risk level configured by the resource owner, or a mapping relationship between a scenario feature of a resource access scenario and a risk level;

[0165] The policy management module 104 is specifically used for:

[0166] Obtaining a resource identifier of a target resource accessed by the resource access request, or obtaining a scenario feature of a target access scenario corresponding to the resource access request;

[0167] Determining a target risk level corresponding to the resource identifier of the target resource or the scenario feature of the target access scenario according to the resource identifier of the target resource or the scenario feature of the target access scenario;

[0168] When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, it is determined that the access policy indicates enabling the credential consumption invalidation mechanism.

[0169] In some possible implementations, the scene feature includes at least one of the following:

[0170] Public network access, cross-virtual private cloud (VPC) access, read access or write access.

[0171] In some possible implementations, the identity and credential management module 102 is further configured to:

[0172] Receiving a credential revocation request sent by a resource owner, wherein the credential revocation request is used to revoke the resource access credential;

[0173] According to the credential revocation request, the status of the resource access credential is updated to invalid.

[0174] In some possible implementations, the policy management module 104 is further configured to:

[0175] Receive scenario characteristics of the credential revocation scenario sent by the resource owner;

[0176] Detect whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, update the status of the resource access credential to invalid through the identity and credential management module.

[0177] In some possible implementations, the identity and credential management module 102 is specifically used to:

[0178] The recorded information of the resource access credential is deleted, or the status tag of the recorded resource access credential is updated to invalid.

[0179] Based on the above identity management node 100, the present application also provides a resource access control system 10. The resource access control system 10 is used to implement resource access control on the cloud platform. Figure 1 As shown, the resource access control system 10 includes an identity management node 100 and a resource access control node 200. The identity management node 100 is used to execute the resource access control method as described above, so that the resource access control node 200 performs access control on the resources of the resource owner.

[0180] Specifically, the identity management node 100 can receive a credential acquisition request sent by a resource access party, send a resource access credential to the resource access party according to the credential acquisition request, and record the status of the resource access credential. The resource access party can send a resource access request, which can carry the resource access credential or the index information of the resource access credential. The resource access control node 200 receives the above resource access request, generates a credential verification request according to the resource access request, and carries the resource access credential or the index information of the resource access credential. Then the resource access control node 200 sends a credential verification request to the identity management node 100.

[0181] Accordingly, the identity management node 100 can check the status of the resource access credential in response to the credential verification request. When the status of the resource access credential is valid, the identity management node 100 can update the status of the resource access credential to invalid, and send a verification result indicating that the verification is passed to the resource access control node 200, so that the resource access control node 200 allows access to the resources of the resource owner.

[0182] The above-mentioned identity management node 100 or resource access control system 10 can be implemented by a computing device or a computing device cluster. The computing device and computing device cluster of the present application are introduced below from the perspective of hardware entity.

[0183] The present application also provides a computing device 500. Figure 5 As shown, computing device 500 includes: bus 502, processor 504, memory 506 and communication interface 508. Processor 504, memory 506 and communication interface 508 communicate through bus 502. Computing device 500 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in computing device 500.

[0184] The bus 502 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The bus 502 is represented by only one line, but it does not mean that there is only one bus or one type of bus. The bus 502 may include a path for transmitting information between various components of the computing device 500 (eg, the memory 506, the processor 504, and the communication interface 508).

[0185] The processor 504 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0186] The memory 506 may include a volatile memory, such as a random access memory (RAM). The memory 506 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD). The memory 506 stores executable program code, and the processor 504 executes the executable program code to implement the aforementioned resource access control method. Specifically, the memory 506 stores instructions for the resource access control system 10 or the identity management node 100 to execute the resource access control method.

[0187] The communication interface 508 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 500 and other devices or a communication network.

[0188] The embodiment of the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0189] like Figure 6 As shown, the computing device cluster includes at least one computing device 500. The memory 506 in one or more computing devices 500 in the computing device cluster may store the same resource access control system 10 or identity management node 100 for executing instructions of the resource access control method.

[0190] In some possible implementations, one or more computing devices 500 in the computing device cluster may also be used to execute some instructions of the resource access control system 10 or the identity management node 100 for executing the resource access control method. In other words, a combination of one or more computing devices 500 may jointly execute instructions of the resource access control system 10 or the identity management node 100 for executing the resource access control method.

[0191] It should be noted that the memory 506 in different computing devices 500 in the computing device cluster may store different instructions for executing partial functions of the resource access control system 10 or the identity management node 100 .

[0192] Figure 7 A possible implementation is shown. Figure 4As shown, two computing devices 500A and 500B are connected via a communication interface 508. The memory in computing device 500A stores instructions for executing the functions of device A and device B. The memory in computing device 500B stores instructions for executing the functions of device C. In other words, the memories 506 of computing devices 500A and 500B jointly store instructions for resource access control system 10 or identity management node 100 to execute resource access control method.

[0193] Figure 7 The connection mode between the computing device clusters shown may be considered to be based on the fact that the resource access control method provided by the present application requires computing power for policy authentication. Therefore, it is considered to hand over the functions implemented by the policy management module 104 to the computing device 500B for execution.

[0194] It should be understood that Figure 7 The functions of the computing device 500A shown in FIG. 5A may also be completed by multiple computing devices 500. Similarly, the functions of the computing device 500B may also be completed by multiple computing devices 500.

[0195] In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network, which may be a wide area network or a local area network. Figure 8 A possible implementation is shown. Figure 8 As shown, two computing devices 500C and 500D are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 506 in the computing device 500C stores instructions for executing the functions of the identity and credential management module 102. At the same time, the memory 506 in the computing device 500D stores instructions for executing the functions of the policy management module 104.

[0196] Figure 8 The connection method between the computing device clusters shown may be based on the consideration that the resource access control method provided in the present application requires computing power for policy authentication, and therefore the functions implemented by the policy management module 104 may be handed over to the computing device 500D for execution.

[0197] It should be understood that Figure 8 The functions of the computing device 500C shown in FIG. 5 may also be completed by multiple computing devices 500. Similarly, the functions of the computing device 500D may also be completed by multiple computing devices 500.

[0198] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the above-mentioned resource access control system 10 or identity management node 100 for executing the resource access control method.

[0199] The embodiment of the present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the resource access control method described above.

[0200] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. A resource access control method, characterized in that: Applied to a resource access control system, the resource access control system is used to implement resource access control on a cloud platform, the resource access control system includes an identity management node and a resource access control node, and the method includes: The identity management node receives a credential acquisition request sent by a resource access party, sends a resource access credential to the resource access party according to the credential acquisition request, and records the status of the resource access credential; The identity management node receives a credential verification request sent by the resource access control node, where the credential verification request is generated by the resource access control node according to the resource access request sent by the resource access party, and the credential verification request carries the resource access credential or index information of the resource access credential; The identity management node checks the status of the resource access credential in response to the credential verification request, and when the status of the resource access credential is valid, updates the status of the resource access credential to invalid, and sends a verification result indicating that the verification is passed to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

2. The method according to claim 1, characterized in that The method further comprises: The identity management node receives an access policy for a resource or access scenario configured by a resource owner, wherein the access policy is used to indicate whether to enable a credential consumption invalidation mechanism; The identity management node updates the state of the resource access credential to invalid, including: When the identity management node determines that the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates to enable the credential consumption invalidation mechanism, the status of the resource access credential is updated to invalid.

3. The method according to claim 2, characterized in that The access policy includes the risk level of resources or access scenarios for which the credential consumption invalidation mechanism is enabled; The identity management node also receives a mapping relationship between a resource identifier and a risk level configured by the resource owner, or a mapping relationship between a scenario feature of a resource access scenario and a risk level; The identity management node determines that an access policy of a target resource accessed by the resource access request or a target access scenario corresponding to the resource access request indicates that the credential consumption invalidation mechanism is enabled, including: The identity management node obtains a resource identifier of a target resource accessed by the resource access request, or obtains a scenario feature of a target access scenario corresponding to the resource access request; The identity management node determines, according to the resource identifier of the target resource or the scenario feature of the target access scenario, a target risk level corresponding to the resource identifier of the target resource or the scenario feature of the target access scenario; When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, the identity management node determines that the access policy indicates enabling the credential consumption invalidation mechanism.

4. The method according to claim 3, characterized in that The scene features include at least one of the following: Public network access, cross-virtual private cloud (VPC) access, read access or write access.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The identity management node receives a credential revocation request sent by a resource owner, where the credential revocation request is used to revoke the resource access credential; The identity management node updates the status of the resource access credential to invalid according to the credential revocation request.

6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The identity management node receives scenario characteristics of a credential revocation scenario sent by a resource owner; The identity management node detects whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, the status of the resource access credential is updated to invalid.

7. The method according to any one of claims 1 to 6, characterized in that: The identity management node updates the state of the resource access credential to invalid, including: The identity management node deletes the recorded information of the resource access credential, or updates the status tag of the recorded resource access credential to invalid.

8. An identity management node, characterized in that: The nodes include: The identity and credential management module is used to receive a credential acquisition request sent by a resource access party, send a resource access credential to the resource access party according to the credential acquisition request, and record the status of the resource access credential; A policy management module, configured to receive a credential verification request sent by a resource access control node, wherein the credential verification request is generated by the resource access control node according to a resource access request sent by the resource access party, and the credential verification request carries the resource access credential or index information of the resource access credential; The policy management module is also used to check the status of the resource access credential in response to the credential verification request. When the status of the resource access credential is valid, the status of the resource access credential is updated to invalid through the identity and credential management module, and a verification result indicating that the verification is passed is sent to the resource access control node, so that the resource access control node allows access to the resources of the resource owner.

9. The node according to claim 8, characterized in that: The policy management module is also used for: Receive an access policy for a resource or access scenario configured by a resource owner, wherein the access policy is used to indicate whether to enable a credential consumption invalidation mechanism; The policy management module is specifically used for: When it is determined that the access policy of the target resource accessed by the resource access request or the target access scenario corresponding to the resource access request indicates enabling the credential consumption invalidation mechanism, the status of the resource access credential is updated to invalid through the identity and credential management module.

10. The node according to claim 9, characterized in that: The access policy includes the risk level of resources or access scenarios for which the credential consumption invalidation mechanism is enabled; The policy management module is also used for: Receive a mapping relationship between a resource identifier and a risk level configured by the resource owner, or a mapping relationship between a scenario feature of a resource access scenario and a risk level; The policy management module is specifically used for: Obtaining a resource identifier of a target resource accessed by the resource access request, or obtaining a scenario feature of a target access scenario corresponding to the resource access request; Determining a target risk level corresponding to the resource identifier of the target resource or the scenario feature of the target access scenario according to the resource identifier of the target resource or the scenario feature of the target access scenario; When the risk level of the resource or access scenario for which the credential consumption invalidation mechanism is enabled includes the target risk level, it is determined that the access policy indicates enabling the credential consumption invalidation mechanism.

11. The node according to claim 10, characterized in that: The scene features include at least one of the following: Public network access, cross-virtual private cloud (VPC) access, read access or write access.

12. The node according to any one of claims 8 to 11, characterized in that: The identity and credential management module is also used to: Receiving a credential revocation request sent by a resource owner, wherein the credential revocation request is used to revoke the resource access credential; According to the credential revocation request, the status of the resource access credential is updated to invalid.

13. The node according to any one of claims 8 to 11, characterized in that: The policy management module is also used for: Receive scenario characteristics of the credential revocation scenario sent by the resource owner; Detect whether the scenario characteristics of the target access scenario corresponding to the resource access request match the scenario characteristics of the credential revocation scenario. If the match is successful, update the status of the resource access credential to invalid through the identity and credential management module.

14. The node according to any one of claims 8 to 13, characterized in that: The identity and credential management module is specifically used for: The recorded information of the resource access credential is deleted, or the status tag of the recorded resource access credential is updated to invalid.

15. A resource access control system, characterized in that: The resource access control system is used to implement resource access control for the cloud platform. The resource access control system includes an identity management node and a resource access control node. The identity management node is used to execute the method described in any one of claims 1 to 7 so that the resource access control node allows access to the resources of the resource owner.

16. A computing device cluster, characterized in that: The computing device cluster includes at least one computing device, and the at least one computing device includes at least one processor and at least one memory, wherein the at least one memory stores computer-readable instructions; the at least one processor executes the computer-readable instructions so that the computing device cluster executes the method as described in any one of claims 1 to 7.

17. A computer-readable storage medium, characterized in that: The method comprises computer-readable instructions; the computer-readable instructions are used to implement the method according to any one of claims 1 to 7.

18. A computer program product, characterized in that The method comprises computer-readable instructions; the computer-readable instructions are used to implement the method according to any one of claims 1 to 7.