Cloud-computing-based access management method and apparatus, and device
By establishing data boundaries on the cloud platform and access management is carried out based on the constraints of identity subject information, access resources, network and trusted execution environment, the problem of data security threats in cloud data centers is solved and effective data on cloud data is achieved Protection and flexible management.
Patent Information
- Application Number
- PCT/CN2024/093888
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-25
- Filing Date
- 2024-05-17
- Publication Date
- 2024-11-21
AI Technical Summary
The data of tenants in cloud data centers faces security threats from external attackers, other tenants and insiders, and existing technologies are difficult to effectively ensure data security.
By establishing data boundaries on the cloud platform, access management is carried out based on the constraints of identity subject information, access resources, network and trusted execution environment, allowing or denying access requests, thereby ensuring data security.
Effectively prevent unauthorized data access, improves the security of cloud data, meets the flexible needs of tenants, and simplifies operational processes.
Smart Images

Figure CN2024093888_21112024_PF_FP_ABST
Abstract
Description
Method, device and equipment for access management based on cloud computing technology
[0001] This disclosure claims priority to Chinese patent application No. 202310564727.1 filed on May 18, 2023, entitled “Method, device and equipment for realizing data security boundary on the cloud based on IAM” and Chinese patent application No. 202311247399.9 filed on September 25, 2023, entitled “Method, device, equipment and storage medium for data access”, the entire contents of which are incorporated by reference into this disclosure. Technical Field
[0002] The present disclosure relates to the field of cloud technology, and in particular to a method, apparatus, and device for access management based on cloud computing technology. Background Art
[0003] With the development of cloud computing technology, data centers are evolving from local data centers to cloud data centers. Cloud data centers provide cloud services to multiple tenants and store their data. Furthermore, they also offer some services and resources to the public internet. This exposes tenant data in cloud data centers to numerous security threats. Therefore, a method to ensure tenant data security in cloud data centers is urgently needed.
[0004] Summary of the Invention
[0005] The present disclosure provides a method, apparatus, and device for access management based on cloud computing technology, which can effectively ensure data security in cloud data centers. The corresponding technical solutions are as follows:
[0006] In a first aspect, a method for access management based on cloud computing technology is provided. The method is applied to a cloud platform, where the cloud platform is used to manage infrastructure that provides cloud services. The infrastructure includes at least one cloud data center, each of the at least one cloud data center includes multiple servers, and the cloud service is provided in one or more servers of the at least one cloud data center. The method includes: the cloud platform receives a data boundary establishment request for the cloud service input by a first tenant, wherein the data boundary establishment request is used to instruct the cloud platform to establish a data boundary for the cloud service, wherein the data boundary includes at least one constraint condition selected from the following: identity subject information using the cloud service, access resource information related to the cloud service, network information involved in using the cloud service, device information initiating access requests to the cloud service, and trusted execution environment information related to the cloud service. The cloud platform establishes a data boundary for the cloud service based on the data boundary establishment request. When the cloud service receives a first access request for the cloud service generated by the second tenant or the first tenant, the cloud platform compares the information carried in the first access request with the constraints in the data boundary. If the information carried in the first access request matches the constraints in the data boundary, the cloud service is allowed to respond to the first access request. If the information carried in the first access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the first access request, wherein the information carried in the first access request includes one or more of the first identity subject information, the first access resource information, the first network information, the first device information that initiates the first access request, and the first trusted execution environment information.
[0007] In the technical solution provided by the present disclosure, tenants can establish data boundaries for purchased cloud services through the cloud platform according to their actual needs, and use the data boundaries to constrain one or more of the identity subject using the cloud service, the access resources related to the cloud service, the network involved in using the cloud service, the device that initiates access requests to the cloud service, and the trusted execution environment related to the cloud service. Furthermore, when there is an access request for the cloud service, the information carried in the access request is compared with the data boundary established by the tenant for the cloud service. If the information carried in the access request matches the constraints in the data boundary, the cloud service is allowed to respond to the access request. If the information carried in the access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the access request. In this way, the data security of tenants on the cloud can be effectively guaranteed through the constraints of the data boundary.
[0008] In a possible implementation, a first tenant and a second tenant are registered on a cloud platform, the first tenant plays the role of an administrator of a data boundary, and the second tenant plays the role of a visitor of a data boundary.
[0009] In one possible implementation, the method further includes: the cloud platform receiving a request from the first tenant to add a constraint condition to the data boundary. The cloud platform adding a first constraint condition indicated by the constraint condition addition request to the data boundary, where the first constraint condition is one or more of the following: second identity subject information, second access resource information, second network information, information about a second device initiating the access request, and information about a second trusted execution environment.
[0010] In the technical solution provided by the present disclosure, tenants can freely add constraints to the established data boundaries according to actual needs, which is more flexible and simple to operate.
[0011] In one possible implementation, the method further includes: the cloud platform receiving a constraint removal request for a data boundary input by the first tenant. The cloud platform removing, from the data boundary, a second constraint indicated by the constraint removal request, where the second constraint is one or more of: third identity subject information, third access resource information, third network information, information about a third device initiating the access request, and third trusted execution environment information.
[0012] In the technical solution provided by the present disclosure, tenants can freely remove constraints in the established data boundaries according to actual needs, which is more flexible and simple to operate.
[0013] In a possible implementation, the method further includes: the cloud platform receiving a data boundary deletion request for the cloud service input by the first tenant, and the cloud platform deleting the data boundary indicated by the data boundary deletion request.
[0014] In the technical solution provided by the present disclosure, tenants can delete the established data boundaries according to actual needs, which is more flexible and simple to operate.
[0015] In a possible implementation, the method further includes: the cloud platform receiving a request from the first tenant to deactivate a data boundary function for the cloud service, and the cloud platform deactivating the data boundary function for the cloud service.
[0016] In the technical solution provided by the present disclosure, tenants can disable the data boundary function for cloud services according to actual needs, which has higher operational flexibility and is simpler to operate.
[0017] In a possible implementation, the method further includes: the cloud platform receiving a request from the first tenant to enable a data boundary function for the cloud service, and the cloud platform enabling the data boundary function for the cloud service.
[0018] In the technical solution provided by the present disclosure, tenants can enable the data boundary function for cloud services according to actual needs, which has higher operational flexibility and is simpler to operate.
[0019] In a second aspect, a cloud computing-based access management device is provided. The device is applied to a cloud platform. The cloud platform is used to manage infrastructure that provides cloud services. The infrastructure includes at least one cloud data center. Each of the at least one cloud data center includes multiple servers. The cloud service is provided in one or more servers in the at least one cloud data center. The method includes:
[0020] a management module configured to receive a data boundary establishment request for the cloud service input by a first tenant, wherein the data boundary establishment request is used to instruct the cloud platform to establish a data boundary for the cloud service, wherein the data boundary includes at least one constraint condition selected from the group consisting of identity subject information for using the cloud service, access resource information related to the cloud service, network information involved in using the cloud service, device information for initiating access requests to the cloud service, and trusted execution environment information related to the cloud service; and establish a data boundary for the cloud service according to the data boundary establishment request;
[0021] An authentication module is configured to compare, when the cloud service receives a first access request generated by a second tenant or the first tenant for the cloud service, information carried in the first access request with the constraints in the data boundary; if the information carried in the first access request matches the constraints in the data boundary, the cloud service is allowed to respond to the first access request; and if the information carried in the first access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the first access request, wherein the information carried in the first access request includes one or any combination of first identity subject information, first access resource information, first network information, information of the first device that initiates the first access request, and first trusted execution environment information.
[0022] In a possible implementation, the first tenant and the second tenant are registered on the cloud platform, the first tenant has a role as an administrator of the data boundary, and the second tenant has a role as a visitor of the data boundary.
[0023] In a possible implementation, the management module is further configured to:
[0024] receiving a request for adding a constraint condition for the data boundary input by the first tenant;
[0025] Add the first constraint indicated by the constraint addition request in the data boundary, wherein the first constraint is one or more of the second identity subject information, the second access resource information, the second network information, the second device information for initiating the access request, and the second trusted execution environment information.
[0026] In a possible implementation, the management module is further configured to:
[0027] receiving a request for removing a constraint condition on the data boundary input by the first tenant;
[0028] Remove the second constraint indicated by the constraint removal request in the data boundary of the server, wherein the first constraint is one or more of third identity subject information, third access resource information, third network information, third device information for initiating the access request, and third trusted execution environment information.
[0029] In a possible implementation, the management module is further configured to:
[0030] receiving a data boundary deletion request for the cloud service input by the first tenant;
[0031] The data boundary indicated by the data boundary deletion request is deleted.
[0032] In a possible implementation, the management module is further configured to:
[0033] receiving a request input by the first tenant to deactivate a data boundary function of the cloud service;
[0034] Disable the data perimeter functionality for the cloud service in question.
[0035] In a possible implementation, the management module is further configured to:
[0036] receiving a data boundary function activation request for the cloud service input by the first tenant;
[0037] Enable data perimeter functionality for the cloud service.
[0038] In a third aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory, the processor of the at least one computing device being used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the cloud computing-based access management method provided in the first aspect above.
[0039] In a fourth aspect, a computer program product comprising instructions is provided. When the instructions are executed by a computing device cluster, the computing device cluster executes the cloud computing-based access management method provided in the first aspect above.
[0040] In a fifth aspect, a computer-readable storage medium is provided, comprising computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the cloud computing-based access management method provided in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] FIG1 is a schematic diagram of an implementation scenario provided by an embodiment of the present disclosure;
[0042] FIG2 is a flow chart of an access management method based on cloud computing provided by an embodiment of the present disclosure;
[0043] FIG3 is a schematic diagram of a data boundary provided by an embodiment of the present disclosure;
[0044] FIG4 is a schematic diagram of a data boundary provided by an embodiment of the present disclosure;
[0045] FIG5 is a schematic diagram of a data boundary provided by an embodiment of the present disclosure;
[0046] FIG6 is a schematic diagram of a data boundary provided by an embodiment of the present disclosure;
[0047] FIG7 is a flow chart of an access management method based on cloud computing provided by an embodiment of the present disclosure;
[0048] FIG8 is a schematic structural diagram of an access management device based on cloud computing provided by an embodiment of the present disclosure;
[0049] FIG9 is a schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure;
[0050] FIG10 is a schematic diagram of a computer device cluster structure provided by an embodiment of the present disclosure;
[0051] FIG11 is a schematic diagram of a computer device cluster structure provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0052] In order to make the objectives, technical solutions and advantages of the present disclosure more clear, the embodiments of the present disclosure will be further described in detail below with reference to the accompanying drawings.
[0053] The following first explains some of the terms involved in the implementation of the present disclosure to facilitate understanding of the present disclosure by those skilled in the art.
[0054] Cloud platform and infrastructure: The cloud platform is used to manage the cloud vendor's infrastructure. The infrastructure consists of multiple cloud data centers located in different regions, where each region has at least one cloud data center. The cloud platform can provide interfaces related to cloud computing services, such as configuration pages or application program interfaces (APIs) for tenants to access cloud services. Tenants can log in to the cloud platform using a pre-registered account and password, and after successful login, they can select and purchase cloud services provided by the cloud data center in the predetermined region, such as object storage services, database services, message queue services, or other well-known cloud services.
[0055] Tenant: A top-level object used to manage cloud services and / or cloud resources. Tenants register a tenant account and set a tenant password on the cloud platform through a local client (such as a browser). The local client remotely logs in to the cloud platform using the tenant account and set tenant password. The cloud platform provides a configuration interface or API for tenants to configure and use cloud services. Cloud services can be provided by the infrastructure managed by the above-mentioned cloud platform.
[0056] A Virtual Private Cloud (VPC) is a dynamically configured pool of public cloud computing resources that uses encryption, tunneling, and other security protocols to transmit data between an enterprise and a cloud service provider. A VPC creates an isolated, user-configured, and managed virtual network environment for elastic cloud servers, improving the security of cloud resources and simplifying network deployment. Within a VPC, you can define network characteristics such as security groups, virtual private networks (VPNs), IP address ranges, and bandwidth. Tenants can use VPC to conveniently manage and configure their internal networks, making network changes securely and quickly.
[0057] The present disclosure provides an access management method based on cloud computing technology. This method can be applied to a cloud platform, which manages the infrastructure that provides cloud services. The infrastructure includes at least one cloud data center, each of which includes multiple servers, and the cloud services are provided in one or more servers in the at least one cloud data center. The following describes an exemplary implementation scenario of the access management method based on cloud computing technology provided by the present disclosure in conjunction with the accompanying drawings.
[0058] FIG1 is a schematic diagram of an implementation scenario provided by an embodiment of the present disclosure. As shown in FIG1 , this implementation scenario includes a cloud platform 10, cloud data centers 1, ..., and cloud data centers m. Each cloud data center is equipped with multiple servers. For example, cloud data center 1 is equipped with servers 1, 2, ..., and n, and cloud services, such as cloud service 1, cloud service 2, ..., and cloud service a, are deployed on the servers. Tenant 40 can log in to cloud platform 10 via client 30 via the internet 20 using a tenant account and password pre-registered on cloud platform 10, purchase cloud services through cloud platform 10, and establish a data boundary for the purchased cloud services. Tenant 50 can log in to cloud platform 10 via client 60 via the internet 20 using a tenant account and password pre-registered on cloud platform 10, purchase cloud services through cloud platform 10, and establish a data boundary for the purchased cloud services. Tenant 50 or tenant 40 can use the purchased cloud services to store data. However, because cloud data centers may provide services to multiple tenants and may also provide services to the public network, tenants' data may be subject to numerous security threats. The following describes security threats to tenants' data in the cloud.
[0059] Taking the cloud service as an object storage service as an example, tenant 40 can purchase at least one storage bucket (such as storage bucket 1 and storage bucket 2) based on actual needs and store data in the bucket. For tenant 50, their data in the cloud may face the following security threats.
[0060] Security Threat 1: Attacks from external attackers. An external attacker possesses the legitimate credentials of tenant 40 and directly accesses the storage buckets of tenant 50 (such as storage bucket 1 and storage bucket 2), obtaining tenant 40's data and causing tenant 50's data to be leaked.
[0061] Security threat 2: Attacks from other tenants in the cloud (such as tenant 50). Due to incorrect or malicious authorization configuration of resources, unintended tenants (such as tenant 50) can access tenant 40's storage buckets (such as storage bucket 1 and storage bucket 2) and obtain tenant 40's data, resulting in tenant 40's data leakage.
[0062] Security Threat 3: Attacks from insiders or malicious code. An insider from tenant 40, or through malicious code, writes tenant 40's data, which should have been stored in storage bucket 1 or storage bucket 2, to another tenant's storage bucket, resulting in a data leak for tenant 40.
[0063] The embodiment of the present disclosure provides an access management method based on cloud computing technology. In this method, tenants can establish data boundaries for purchased cloud services through the cloud platform according to their actual needs. The data boundaries can be used to constrain one or more of the following: the identity subject using the cloud service, the access resources related to the cloud service, the network involved in using the cloud service, the device that initiates access requests to the cloud service, and the trusted execution environment related to the cloud service. Furthermore, when there is an access request for the cloud service, the information carried in the access request is compared with the data boundary established by the tenant for the cloud service. If the information carried in the access request matches the constraints in the data boundary, the cloud service is allowed to respond to the access request. If the information carried in the access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the access request. In this way, the data security of the tenant on the cloud can be effectively guaranteed by the constraints of the data boundary. The access management method based on cloud computing technology provided by the embodiment of the present disclosure is described below in conjunction with the accompanying drawings.
[0064] 2 , the processing flow of the access management method based on cloud computing technology provided by the embodiment of the present disclosure may include the following steps:
[0065] Step 201: The first tenant sends a data boundary establishment request for a target cloud service to the cloud platform through a terminal.
[0066] The first tenant is any tenant who has purchased the target cloud service, such as tenant 40 and tenant 50 in FIG1 .
[0067] In practice, after purchasing the target cloud service, the first tenant can send a data boundary establishment request for the target cloud service to the cloud platform through the terminal to ensure the security of the data on the cloud, so as to instruct the cloud platform to establish a data boundary for the target cloud service. Among them, the data boundary establishment request carries different constraints included in the data boundary in different fields. The constraints may include one or more of the identity subject information of the target cloud service, the access resource information related to the target cloud service, the network information involved in the use of the target cloud service, the device information that initiates the access request to the target cloud service, and the trusted execution environment information related to the target cloud service. The above constraints are explained below:
[0068] Identity subject information for using the target cloud service: This identity subject information can be the identifier of an Identity and Access Management (IAM) identity established by the tenant for members within an organization. The first tenant can be an enterprise. Using the organization service provided by the cloud platform, the first tenant can establish an organization corresponding to the first tenant. Employees within the enterprise are mapped to members of this organization. The first tenant can then establish a corresponding IAM identity for each member of the organization. Members can then use this IAM identity to access the target cloud service purchased by the tenant. This constraint can be used to control which IAM identities are allowed to access the target cloud service.
[0069] Access resource information related to the target cloud service: This information can be the resource information of the target cloud service purchased by the first tenant. For example, if the target cloud service is an object storage service, the access resource information can be the bucket ID; if the target cloud service is a database service, the access resource information can be the database ID. This constraint can be used to control which resources of the target cloud service are allowed to be accessed.
[0070] Network information related to the target cloud service: This network information can be the identifier of a virtual private cloud (VPC) or a public network. This network information can be used to limit which networks are allowed to access the target cloud service.
[0071] Device information for initiating access requests to the target cloud service: This device information can be used to identify the device used to initiate access requests to the target cloud service. This information indicates the device's operating system, whether it has a security scanning application installed, and other information. This constraint can be used to restrict which devices are allowed to access the target cloud service.
[0072] Trusted execution environment information related to the target cloud service: The trusted execution environment information may be the execution environment information corresponding to the trusted execution environment of the target application accessing the target cloud service. The execution environment information is used to indicate whether the device executing the application supports the Trusted Platform Module (TPM) and whether it supports memory protection.
[0073] The step 201 is described below with an example.
[0074] Example 1: Tenant 1 wants to establish a data boundary for the object storage service it has purchased. This constraint ensures that only IAM identity 1 and IAM identity 2, in trusted execution environment 1, using device 1 and through VPC 1, can access buckets 1 and 2. Accordingly, the data boundary establishment request sent by the terminal carries IAM identity 1's identifier P1, IAM identity 2's identifier P2, trusted execution environment information E1 for trusted execution environment 1, device information D1, VPC 1's identifier N1, bucket 1's identifier R1, and bucket 2's identifier R2.
[0075] Example 2: Tenant 1 wants to establish a data boundary for the object storage service it has purchased. This constraint restricts access to bucket 3 to IAM identities 3, 4, and 5 through VPC 2. Accordingly, the data boundary establishment request sent by the terminal includes IAM identity 3's identifier P3, IAM identity 4's identifier P4, IAM identity 5's identifier P5, VPC 2's identifier N2, and bucket 3's identifier R3.
[0076] Step 202: The cloud platform establishes a data boundary for the target cloud service based on the data boundary establishment request.
[0077] In implementation, after receiving the data boundary establishment request sent by the terminal, the cloud platform obtains the constraint conditions carried in the data boundary establishment request and establishes a data boundary including the constraint conditions.
[0078] Combined with the above example 1: P1, P2, E1, D1, N1, R1, and R2 are carried in the data boundary establishment request, and the cloud platform establishes a data boundary for the target cloud service, which includes P1, P2, E1, D1, N1, R1, and R2.
[0079] Combined with the above example 2: P3, P4, P5, N2, and R3 are carried in the data boundary establishment request, and the cloud platform establishes a data boundary for the target cloud service, which includes P3, P4, P5, N2, and R3.
[0080] Step 203: The target cloud service receives an access request for the target cloud service.
[0081] In implementation, when a tenant needs to use a target cloud service, they can send an access request to the target cloud service through their device. In response, the target cloud service receives the access request sent by the tenant. The tenant can be the first tenant mentioned above, or another tenant registered on the cloud platform other than the first tenant. The access request carries target information, which includes one or more of the following: first identity subject information, first access resource information, first network information, information about the first device initiating the access request, and information about the first trusted execution environment.
[0082] Step 204: The target cloud service sends the target information carried in the access request to the cloud platform.
[0083] In implementation, after receiving the access request, the target cloud service obtains the target information carried in the access request and sends the target information to the cloud platform.
[0084] Step 205: The cloud platform compares the target information with the constraints in the data boundary for the target cloud service to determine whether the target information matches the constraints in the data boundary for the target cloud service.
[0085] During implementation, the cloud platform can obtain the data boundary for the target cloud service, compare the target information with the constraints in each data boundary for the target cloud service in turn, and determine whether the target information matches the constraints in any data boundary for the target cloud service. The following uses the example of the target information including five types of information (first identity subject information, first access resource information, first network information, first device information for initiating an access request, and first trusted execution environment information) and the data boundary including five constraints (identity subject information for using the target cloud service, access resource information related to the target cloud service, network information involved in using the target cloud service, device information for initiating an access request to the target cloud service, and trusted execution environment information related to the target cloud service) to illustrate the process of comparing the target information with the constraints in any data boundary.
[0086] Comparison of identity subject information: Compare the first identity subject information in the target information with the identity subject information using the target cloud service in the data boundary. If the identity subject information using the target cloud service includes the first identity subject information, it is determined that the first identity subject information matches; otherwise, it is determined that the first identity subject information does not match.
[0087] Comparison of access resource information: compare the first access resource information in the target information with the access resource information related to the target cloud service in the data boundary. If the access resource information related to the target cloud service includes the first access resource information, it is determined that the first access resource information matches; otherwise, it is determined that the first access resource information does not match.
[0088] Comparison of network information: Compare the first network information in the target information with the network information involved in using the target cloud service in the data boundary. If the first network information is the VPC identifier, determine whether the network information involved in using the target cloud service includes the first network information. If so, determine that the first network information matches; otherwise, determine that the first network information does not match. If the first network information is related information about the public network (such as the destination IP address, etc.), determine whether the network information involved in the target cloud service includes the public network identifier. If so, determine that the first network information matches; otherwise, determine that the first network information does not match.
[0089] Comparison of device information: Compare the first device information in the target information with the device information in the data boundary that initiates the access request to the target cloud service. If the device information that initiates the access request to the target cloud service includes the first device information, it is determined that the first device information matches; otherwise, it is determined that the first device information does not match.
[0090] Comparison of trusted execution environment information: compare the first trusted execution environment information in the target information with the trusted execution environment information related to the target cloud service in the data boundary. If the first trusted execution environment information is included in the trusted execution environment information related to the target cloud service, it is determined that the first trusted execution environment information matches; otherwise, it is determined that the first trusted execution environment information does not match.
[0091] If the five types of information included in the target information and the five constraints included in the data boundary all match, it is determined that the target information and the constraints in the data boundary match; if any one of the five types of information does not match the corresponding constraints in the data boundary, it is determined that the target information and the constraints in the data boundary do not match.
[0092] The following describes step 205 using an example.
[0093] Example 1: As shown in Figure 3, the target information includes first identity subject information P3, first trusted execution environment information E1, first device information D1, first network information N2, and first access resource information R1. The data boundaries for the target cloud service are data boundary 1 and data boundary 2. Data boundary 1 includes P1, P2, E1, D1, N1, R1, and R2, while data boundary 2 includes P3, P4, E1, D1, N2, R1, and R2. First, the target information is compared with the constraints in data boundary 1. If it is determined that P1 and N2 are not included in data boundary 1, then the target information is determined to not match the constraints in data boundary 1. Then, the target information is compared with the constraints in data boundary 2. If it is determined that all five pieces of information in the target information are included in data boundary 1, then the target information is determined to match the constraints in data boundary 1. Furthermore, the target information is determined to match the constraints in the data boundary for the target cloud service.
[0094] Example 2: As shown in Figure 4, the target information includes first identity subject information P3, first network information N2, and first access resource information R1. The data boundaries for the target cloud service are data boundary 3 and data boundary 4. Data boundary 3 includes P3, P4, P5, N2, and R3, and data boundary 4 includes P1, P2, N1, and R1. First, the target information is compared with the constraints in data boundary 3. If it is determined that R1 is not included in data boundary 3, then the target information is determined to have a mismatch with the constraints in data boundary 3. Then, the target information is compared with the constraints in data boundary 4. If it is determined that P3 and N2 are not included in data boundary 4, then the target information is determined to have a mismatch with the constraints in data boundary 4. Furthermore, it is determined that the target information does not match the constraints in the data boundary for the target cloud service.
[0095] Step 206: The cloud platform sends the authentication result of the access request to the target cloud service.
[0096] During implementation, if the cloud platform determines that the target information matches the constraints in the data boundary for the target cloud service, it sends an authentication success message to the target cloud service. If it determines that the target information does not match the constraints in the data boundary for the target cloud service, it sends an authentication failure message to the target cloud service.
[0097] Step 207: The target cloud service processes the access request based on the authentication result.
[0098] In implementation, if the target cloud service receives an authentication success message returned by the cloud platform, it executes the access request; if it receives an authentication failure message returned by the cloud platform, it refuses to execute the access request.
[0099] Step 208: The target cloud service sends an access result or an access rejection message to the terminal of the tenant that sent the access request.
[0100] In implementation, if the target cloud service executes the access request, it sends the access result after execution to the tenant's terminal; if it denies the access request, it sends an access denial message to the tenant's terminal.
[0101] In one possible implementation, for an established data boundary, the first tenant can use the cloud platform to add or remove constraints within the data boundary, delete the data boundary, disable or enable the data boundary function for the target cloud service. These functions are described below.
[0102] Adding constraints: If the first tenant wants to add constraints to the first data boundary, he can send a constraint adding request to the cloud platform through the terminal, and the constraint adding request carries the first constraint to be added and the identifier of the first data boundary. Correspondingly, after receiving the constraint adding request, the cloud platform adds the first constraint to the first data boundary. The identifier of the first data boundary can be generated by the terminal and carried in the data boundary establishment request when sending the data boundary establishment request to the cloud platform, or it can be generated by the cloud platform when establishing the first data boundary, and the generated identifier of the first data boundary is returned to the terminal. The following is an example to illustrate adding constraints.
[0103] As shown in Figure 5, data boundary 1 includes P1, P2, E1, D1, N1, R1, and R2. To add identity subject information P5 for use with the target cloud service within data boundary 1, the first tenant sends a constraint addition request to the cloud platform via a terminal. The constraint addition request carries P5 and the identifier of data boundary 1. After receiving the constraint addition request, the cloud platform adds identity subject information P5 for use with the target cloud service within data boundary 1.
[0104] Removing Constraints: If the first tenant wishes to remove one or more constraints from the second data boundary, they can send a constraint removal request to the cloud platform via their terminal. This request includes the second constraints to be removed and the identifier of the second data boundary. Upon receiving the constraint removal request, the cloud platform removes the second constraints from the second data boundary. The following example illustrates adding constraints.
[0105] As shown in Figure 6, data boundary 2 includes P3, P4, E1, D1, N2, R1, and R2. To remove access resource information R1 related to the target cloud service from data boundary 2, the first tenant sends a constraint removal request to the cloud platform via a terminal. The constraint removal request carries R1 and the identifier of data boundary 2. After receiving the constraint removal request, the cloud platform removes the access resource information R1 related to the target cloud service from data boundary 2.
[0106] Deleting a data boundary: If the first tenant wishes to delete the third data boundary, they can send a data boundary deletion request for the target cloud service to the cloud platform through their terminal. The request includes the identifier of the third data boundary. Upon receiving the request, the cloud platform deletes the third data boundary for the target cloud service.
[0107] Deactivating the data boundary function: If the first tenant wishes to deactivate the data boundary function for the target cloud service, they can send a data boundary deactivation request for the target cloud service to the cloud platform through their terminal. Upon receiving the deactivation request, the cloud platform will deactivate all data boundaries established by the first tenant for the target cloud service.
[0108] Enabling the data boundary function: If the first tenant enables the data boundary function for the target cloud service, they can send a data boundary activation request for the target cloud service to the cloud platform through their terminal. Upon receiving the data boundary activation request, the cloud platform activates all data boundaries established by the first tenant for the target cloud service.
[0109] In one possible implementation, the cloud platform may provide an application programming interface (API) for establishing data boundaries, adding constraints, removing constraints, deleting data boundaries, disabling data boundary functions, and enabling data boundary functions.
[0110] Accordingly, the terminal can call the API for establishing a data boundary and send a data boundary establishment request to the cloud platform. It can also call the API for adding constraints and send a constraint addition request to the cloud platform. It can also call the API for removing constraints and send a constraint removal request to the cloud platform. It can also call the API for deleting a data boundary and send a data boundary deletion request to the cloud platform. It can also call the API for deactivating a data boundary and send a data boundary deactivation request to the cloud platform. It can also call the API for enabling a data boundary and send a data boundary activation request to the cloud platform.
[0111] In one possible implementation, to improve the efficiency of tenants establishing data boundaries, in the disclosed embodiment, constraints can be added to the data boundaries at the organizational unit level. An organizational unit can correspond to a department, subsidiary, or project team within an enterprise. Accordingly, the processing of step 201 can be as follows:
[0112] When the first tenant establishes a data boundary, if the data boundary needs to include all IAM identities under the first organizational unit, the field used to carry identity subject information for using the target cloud service in the data boundary establishment request sent by the terminal carries the identifier of the first organizational unit. If the data boundary does not need to include identities within the organization, the field used to carry identity subject information for using the target cloud service in the data boundary establishment request carries indication information of identities outside the organization. If the data boundary needs to include all resources of the target cloud service under the first organizational unit, the field used to carry access resource information related to the target cloud service in the data boundary establishment request sent by the terminal carries the identifier of the first organizational unit. If the data boundary needs to include all networks under the first organizational unit, the field used to carry network information related to using the target cloud service in the data boundary establishment request sent by the terminal carries the identifier of the first organizational unit. If the data boundary needs to include networks outside the organization, the field used to carry network information related to using the target cloud service in the data boundary establishment request carries indication information of networks outside the organization. The above processing is illustrated below with an example.
[0113] Example 1: Tenant 1 wants to establish a data boundary for the object storage service it has purchased. This constraint ensures that only all IAM identities in Organization Unit 1, through the network within Organization Unit 1, can access the object storage service's resources. Accordingly, in the data boundary establishment request sent by the terminal, the field used to carry information about the identity subject using the target cloud service carries the identifier of Organization Unit 1, the field used to carry information about accessed resources related to the target cloud service carries the identifier of Organization Unit 1, and the field used to carry information about the network involved in using the target cloud service carries the identifier of Organization Unit 1.
[0114] Example 2: The first tenant wants to establish a data boundary for the object storage service they have purchased, to implement the following constraint: only identities outside the organization, through networks outside the organization, can access the resources of the object storage service under organizational unit 2. Accordingly, in the data boundary establishment request sent by the terminal, the field used to carry the identity subject information for using the target cloud service carries an indication of the outside-organization identity, the field used to carry access resource information related to the target cloud service carries the identifier of organizational unit 2, and the field used to carry network information related to using the target cloud service carries an indication of the outside-organization network.
[0115] In this possible implementation, the processing of step 202 may be as follows:
[0116] After receiving the data boundary establishment request sent by the terminal, if the cloud platform determines that the field used to carry the identity subject information for using the target cloud service in the data boundary establishment request carries the identifier of the first organizational unit, the identifiers of all IAM identities under the first organizational unit are added to the data boundary as the identity subject information for using the target cloud service. If the field used to carry the identity subject information for using the target cloud service is determined to carry indication information of identities outside the organization, the indication information of identities outside the organization is added to the data boundary as the identity subject information for using the target cloud service. If the field used to carry the access resource information related to the target cloud service in the data boundary establishment request is determined to carry the identifier of the first organizational unit, the information of all resources of the target cloud service under the first organizational unit is added to the data boundary as the access resource information related to the target cloud service. If the field used to carry network information related to the target cloud service in the data boundary establishment request contains the identifier of the first organizational unit, all network information under the first organizational unit is added to the data boundary as network information related to the target cloud service. If the field used to carry network information related to the target cloud service contains information indicating a network outside the organization, the information indicating the network outside the organization is added to the data boundary as network information related to the target cloud service. The corresponding relationship between the data boundary and the organization corresponding to the first tenant is then recorded. The following example illustrates establishing a data boundary.
[0117] In conjunction with Example 1 above: In the data boundary establishment request, the field used to carry the identity principal information for using the target cloud service carries the identifier of Organization Unit 1, the field used to carry access resource information related to the target cloud service carries the identifier of Organization Unit 1, and the field used to carry network information related to using the target cloud service carries the identifier of Organization Unit 1. Accordingly, the cloud platform establishes a data boundary that includes the identifiers of all IAM identities under Organization Unit 1, all VPCs under Organization Unit 1, and all storage buckets under Organization Unit 1.
[0118] In conjunction with Example 2 above: In the data boundary establishment request, the field used to carry the identity subject information for using the target cloud service carries the indication of the external identity, the field used to carry the access resource information related to the target cloud service carries the identifier of Organization Unit 2, and the field used to carry the network information involved in using the target cloud service carries the indication of the external network. Accordingly, the cloud platform establishes a data boundary that includes the indication of the external identity, the indication of the external network, and the identifiers of all storage buckets under Organization Unit 2.
[0119] In this possible implementation, the processing of step 205 may be as follows:
[0120] For example, the target identity information includes first identity subject information, first access resource information, and first network information. The first organization to which the first identity subject belongs, the second organization to which the first access resource information belongs, and the third organization to which the first network information belongs are determined. The first, second, and third organizations may be the same or different organizations. The data boundaries established by the first organization for the target cloud service, the second organization for the target cloud service, and the third organization for the target cloud service are obtained. The target information is compared with each data boundary in turn. The comparisons between different types of information in the target information and different types of constraints in the data boundaries are described below.
[0121] Comparison of identity information: Compare the first identity subject information in the target information with the identity subject information of the target cloud service in the data boundary. If the identity subject information of the target cloud service in the data boundary indicates an identity outside the organization, determine whether the first identity subject information belongs to the organization corresponding to the data boundary. If the first identity subject information belongs to the organization corresponding to the data boundary, determine that the first identity subject information does not match; otherwise, determine that the first identity subject information matches. If the identity subject information of the target cloud service in the data boundary does not indicate an identity outside the organization, determine whether the identity subject information of the target cloud service in the data boundary includes the first identity subject information. If the identity subject information of the target cloud service includes the first identity subject information, determine that the first identity subject information matches; otherwise, determine that the first identity subject information does not match.
[0122] Comparison of network information: Compare the first network information in the target information with the network information related to the use of the target cloud service in the data boundary. If the network information related to the use of the target cloud service in the data boundary indicates an external network, determine whether the first network information belongs to the organization corresponding to the data boundary. If the first network information belongs to the organization corresponding to the data boundary, determine that the first network information does not match; otherwise, determine that the first network information matches. If the network information related to the use of the target cloud service in the data boundary does not indicate an external network, determine whether the network information related to the use of the target cloud service includes the first network information. If the network information related to the use of the target cloud service includes the first network information, determine that the first network information matches; otherwise, determine that the first network information does not match.
[0123] Comparison of access resource information: compare the first access resource information in the target information with the access resource information related to the target cloud service in the data boundary. If the access resource information related to the target cloud service includes the first access resource information, it is determined that the first access resource information matches; otherwise, it is determined that the first access resource information does not match.
[0124] The above processing is described below with an example.
[0125] The target information includes first identity subject information P3, first network information I, and first access resource information R1. The cloud platform determines that the first identity subject information P3 belongs to organization 1, the first network information I is related information of the public network and does not belong to any organization, and the first access resource information R1 belongs to organization 1. Then, the data boundary established by organization 1 for the target cloud service is obtained, including data boundary 5 and data boundary 6. Among them, data boundary 5 includes all IAM identities under organization unit 1 (such as P1, P2, P3...), all network information under organization unit 1 (such as VPC1 identifier N1, VPC2 identifier N2, VPC3 identifier N3...), and the identifiers of all storage buckets of the object storage service under organization unit 1 (such as R1, R2, R3...). Among them, organization unit 1 belongs to organization 1. Data boundary 6 includes indication information of identities outside the organization, indication information of networks outside the organization, and identifiers of all storage buckets of the object storage service under organization unit 2 (such as R10, R20, R30...), and organization unit 2 belongs to organization 1.
[0126] Compare the target information with the constraints in data boundary 5. Regarding identity information comparison: Determine that the identity subject information for using the target cloud service in data boundary 5 is not information indicating an identity outside the organization, and that the first identity subject information P3 is included in the identity subject information for using the target cloud service in data boundary 5 (all IAM identities under organizational unit 1). Therefore, determine that the first identity subject information matches. Regarding network information comparison: Determine that the network information related to using the target cloud service in data boundary 5 is not information indicating an external network, and that the first network information is not included in the network information related to using the target cloud service in data boundary 5 (all network information under organizational unit 1). Therefore, determine that the first network information does not match. Regarding access resource information comparison: Determine that the first access resource information R1 is included in the access resource information related to the target cloud service in data boundary 5 (identifiers of all buckets of the object storage service under organizational unit 1). Therefore, determine that the first access resource information R1 matches. Because the first network information does not match, determine that the target information does not match the constraints in data boundary 6.
[0127] Compare the target information with the constraints in the data boundary 6. Comparison of identity information: Determine that the identity subject information for using the target cloud service in the data boundary 6 is indicative information of an identity outside the organization, then determine that the first identity subject information P3 belongs to organization 1. Since the data boundary 6 also belongs to organization 1, it is determined that the first identity subject information P3 does not match. Comparison of network information: Determine that the network information involved in using the target cloud service in the data boundary 5 is indicative information of an external network, and determine that the first network information does not belong to organization 1, then determine that the first network information matches. Comparison of access resource information: Determine that the first access resource information R1 is not included in the access resource information related to the target cloud service in the data boundary 6 (the identifiers of all storage buckets of the object storage service under organizational unit 2), and then determine that the first access resource information R1 matches. Because the first identity subject information does not match, it is determined that the target information and the constraints in the data boundary 6 do not match.
[0128] The present disclosure also provides an access management method based on cloud computing technology. In this method, the cloud platform includes a management plane and an authentication data plane. In the steps shown in FIG2 , the cloud platform's processing is implemented by the management plane and the authentication data plane. Accordingly, as shown in FIG7 , the processing flow of this method can be as follows:
[0129] Step 701: The first tenant sends a data boundary establishment request for a target cloud service to the management plane of the cloud platform through a terminal.
[0130] The only difference between step 701 and the above step 201 is that the recipient of the data boundary establishment request is changed from the cloud platform to the management plane of the cloud platform, and the specific processing is not repeated here.
[0131] Step 702: The management plane establishes a data boundary for the target cloud service based on the data boundary establishment request.
[0132] The only difference between step 702 and the above step 202 is that the establishment of the data boundary is changed from the cloud platform to the management plane of the cloud platform, and the specific processing is not repeated here.
[0133] Step 703: The target cloud service receives an access request for the target cloud service.
[0134] The specific processing of step 703 is the same as that of the above step 203 and will not be described in detail here.
[0135] Step 704: The target cloud service sends the target information carried in the access request to the authentication data plane of the cloud platform.
[0136] The only difference between step 704 and the above step 204 is that the recipient of the target information carried in the access request is changed from the cloud platform to the authentication data plane of the cloud platform, and the specific processing is not repeated here.
[0137] Step 705: The authentication data plane sends a data boundary acquisition request to the management plane.
[0138] In implementation, after receiving the target information from the target cloud service, the authentication data plane sends a data boundary acquisition request to the management plane, wherein the data boundary acquisition request carries the identifier of the target cloud service.
[0139] In one possible implementation, when the organizational unit of the constraint condition in the data boundary is added at a granular level, after receiving the target information from the target cloud service, the authentication data plane can first obtain the first organization to which the first identity subject information belongs, the second organization to which the first network information belongs, and the third organization to which the first access resource information belongs, carried in the target information, and then send a data boundary acquisition request to the management plane. The data boundary acquisition request carries the identifier of the target cloud service, the organization identifier of the first organization, the organization identifier of the second organization, and the organization identifier of the third organization.
[0140] Step 706: The management plane obtains the data boundary for the target cloud service and sends the data boundary for the target cloud service to the authentication data plane.
[0141] In implementation, after receiving the data boundary acquisition request, the management plane obtains the data boundary established by each tenant for the target cloud service, and sends the obtained data boundary to the authentication data plane.
[0142] In one possible implementation, when the constraint organization unit in the data boundary is added at a granularity, the management plane obtains the data boundary for the target cloud service established by the first organization, the data boundary for the target cloud service established by the second organization, and the data boundary for the target cloud service established by the third organization, and sends the obtained data boundaries to the authentication data plane.
[0143] Step 707: The authentication data plane compares the target information with the constraints in the data boundary for the target cloud service to determine whether the target information matches the constraints in the data boundary for the target cloud service.
[0144] The specific processing in step 707 is the same as the comparison processing of the cloud platform in step 205 above, and will not be repeated here.
[0145] Step 708: The authentication data sends the authentication result of the access request to the target cloud service.
[0146] The only difference between step 708 and the above step 206 is that the sender of the authentication result is changed from the cloud platform to the authentication data plane of the cloud platform, and the specific processing is not repeated here.
[0147] Step 709: The target cloud service processes the access request based on the authentication result.
[0148] The specific processing of step 709 is the same as that of the above step 207 and will not be described in detail here.
[0149] Step 710: The target cloud service sends an access result or an access rejection message to the terminal of the tenant that sent the access request.
[0150] The specific processing of step 710 is the same as that of step 208 above, and will not be described in detail here.
[0151] The present disclosure also provides a data access device, which is applied to a cloud platform. The cloud platform is used to manage infrastructure that provides cloud services. The infrastructure includes at least one cloud data center. Each of the at least one cloud data center includes multiple servers. The cloud service is provided in one or more servers of the at least one cloud data center. As shown in FIG8 , the device includes a management module 810 and an authentication module 820, wherein:
[0152] A management module 810 is configured to receive a data boundary establishment request for the cloud service input by a first tenant, wherein the data boundary establishment request is used to instruct the cloud platform to establish a data boundary for the cloud service, wherein the data boundary includes at least one constraint condition selected from the group consisting of identity subject information for using the cloud service, access resource information related to the cloud service, network information involved in using the cloud service, device information for initiating access requests to the cloud service, and trusted execution environment information related to the cloud service; and establish a data boundary for the cloud service according to the data boundary establishment request;
[0153] The authentication module 820 is used to compare the information carried in the first access request with the constraints in the data boundary when the cloud service receives a first access request generated by the second tenant or the first tenant for the cloud service. If the information carried in the first access request matches the constraints in the data boundary, the cloud service is allowed to respond to the first access request; if the information carried in the first access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the first access request, wherein the information carried in the first access request includes one or any combination of first identity subject information, first access resource information, first network information, first device information for initiating the first access request, and first trusted execution environment information.
[0154] In a possible implementation, the first tenant and the second tenant are registered on the cloud platform, the first tenant has a role as an administrator of the data boundary, and the second tenant has a role as a visitor of the data boundary.
[0155] In a possible implementation, the management module 810 is further configured to:
[0156] receiving a request for adding a constraint condition for the data boundary input by the first tenant;
[0157] Add the first constraint indicated by the constraint addition request in the data boundary, wherein the first constraint is one or more of the second identity subject information, the second access resource information, the second network information, the second device information for initiating the access request, and the second trusted execution environment information.
[0158] In a possible implementation, the management module 810 is further configured to:
[0159] receiving a request for removing a constraint condition on the data boundary input by the first tenant;
[0160] Remove the second constraint indicated by the constraint removal request in the data boundary of the server, wherein the first constraint is one or more of third identity subject information, third access resource information, third network information, third device information for initiating the access request, and third trusted execution environment information.
[0161] In a possible implementation, the management module 810 is further configured to:
[0162] receiving a data boundary deletion request for the cloud service input by the first tenant;
[0163] The data boundary indicated by the data boundary deletion request is deleted.
[0164] In a possible implementation, the management module 810 is further configured to:
[0165] receiving a request input by the first tenant to deactivate a data boundary function of the cloud service;
[0166] Disable the data perimeter functionality for the cloud service in question.
[0167] In a possible implementation, the management module 810 is further configured to:
[0168] receiving a data boundary function activation request for the cloud service input by the first tenant;
[0169] Enable data perimeter functionality for the cloud service.
[0170] The management module 810 and the authentication module 820 can be implemented by software or hardware. For example, the implementation of the management module 810 is described below. Similarly, the implementation of the authentication module 820 can refer to the implementation of the management module 810.
[0171] As an example of a software functional unit, the management module 810 may include code running on a computing instance. The computing instance may be at least one of a physical host (computing device), a virtual machine, a container, and other computing devices. Furthermore, the above-mentioned computing device may be one or more. For example, the management module 810 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the application may be distributed in the same region or in different regions. The multiple hosts / virtual machines / containers used to run the code may be distributed in the same AZ or in different AZs, and each AZ includes one data center or multiple geographically close data centers. Generally, a region may include multiple AZs.
[0172] Similarly, the multiple hosts / virtual machines / containers running the code can be distributed within the same VPC or across multiple VPCs. Typically, a VPC is located within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.
[0173] As an example of a hardware functional unit, management module 810 may include at least one computing device, such as a server. Alternatively, management module 810 may be implemented using an ASIC or a PLD. The PLD may be implemented using a CPLD, FPGA, GAL, or any combination thereof.
[0174] The multiple computing devices included in the management module 810 can be distributed in the same region or in different regions. The multiple computing devices included in the management module 8100 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the management module 410 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.
[0175] The present disclosure also provides a computing device 100. As shown in FIG9 , computing device 100 includes a bus 102, a processor 104, a memory 106, and a communication interface 108. Processor 104, memory 106, and communication interface 108 communicate with each other via bus 102. Computing device 100 may be a server or a terminal device. It should be understood that the present disclosure does not limit the number of processors and memories in computing device 100.
[0176] Bus 102 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG5 shows a single line, but this does not imply a single bus or type of bus. Bus 102 may include a path for transmitting information between various components of computing device 100 (e.g., memory 106, processor 104, and communication interface 108).
[0177] The processor 104 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).
[0178] The memory 106 may include volatile memory, such as random access memory (RAM). The memory 106 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).
[0179] Memory 106 stores executable code, which processor 104 executes to implement the functions of management module 810 and authentication module 820, respectively, thereby implementing the data access method. In other words, memory 106 stores instructions for executing the access management method based on cloud computing technology.
[0180] The communication interface 108 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 100 and other devices or a communication network.
[0181] Embodiments of the present disclosure also provide 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 smartphone.
[0182] As shown in Figure 10, the computing device cluster includes at least one computing device 100. The memory 106 in one or more computing devices 100 in the computing device cluster may store the same instructions for executing the access management method based on cloud computing technology.
[0183] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the access management method based on cloud computing technology. In other words, the combination of one or more computing devices 100 can jointly execute instructions for executing the access management method based on cloud computing technology.
[0184] It should be noted that the memories 106 in different computing devices 100 in the computing device cluster may store different instructions, each for executing a portion of the functions of the access management method based on cloud computing technology.
[0185] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the automated testing method. In other words, the combination of one or more computing devices 100 can jointly execute instructions for executing the access management method based on cloud computing technology.
[0186] It should be noted that the memory 106 in different computing devices 100 in the computing device cluster can store different instructions for executing portions of the automated testing system's functions. In other words, the instructions stored in the memory 106 in different computing devices 100 can implement the functions of one or more nodes in the management module 810 and the authentication module 820.
[0187] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network or a local area network, etc. FIG11 shows a possible implementation. As shown in FIG11 , two computing devices 100A and 100B 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 106 in the computing device 100A stores instructions for executing the functions of the management module 810. At the same time, the memory 106 in the computing device 100B stores instructions for executing the functions of the authentication module 820. It should be understood that the functions of the computing device 100A shown in FIG11 may also be performed by multiple computing devices 100. Similarly, the functions of the computing device 100B may also be performed by multiple computing devices 100.
[0188] The present disclosure also provides another computing device cluster. The connection relationship between the computing devices in this computing device cluster can be similar to the connection relationship between the computing device clusters described in Figures 10 and 11. However, the memory 106 of one or more computing devices 100 in this computing device cluster can store the same instructions for executing the access management method based on cloud computing technology.
[0189] In some possible implementations, the memory 106 of one or more computing devices 100 in the computing device cluster may also store partial instructions for executing the automated testing method. In other words, the combination of one or more computing devices 100 can jointly execute instructions for executing the access management method based on cloud computing technology.
[0190] It should be noted that the memory 106 in different computing devices 100 in the computing device cluster can store different instructions for executing partial functions of the access management apparatus based on cloud computing technology. In other words, the instructions stored in the memory 106 in different computing devices 100 can implement the functions of one or more nodes in the management module 810 and the authentication module 820.
[0191] The present disclosure also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be executed on a computing device or stored on any available medium. When executed on at least one computing device, the computer program product causes the at least one computing device to execute a cloud computing-based access management method.
[0192] The present disclosure 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 magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the access management method based on cloud computing technology.
[0193] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure 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 deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various embodiments of the present disclosure.
Claims
1. An access management method based on cloud computing technology, characterized in that: The method is applied to a cloud platform, the cloud platform is used to manage an infrastructure for providing cloud services, the infrastructure includes at least one cloud data center, each of the at least one cloud data center includes a plurality of servers, the cloud service is provided in one or more servers of the at least one cloud data center, the method includes: The cloud platform receives a data boundary establishment request for the cloud service input by the first tenant, wherein the data boundary establishment request is used to instruct the cloud platform to establish a data boundary for the cloud service, wherein the data boundary includes at least one constraint condition among identity subject information using the cloud service, access resource information related to the cloud service, network information involved in using the cloud service, device information initiating an access request to the cloud service, and trusted execution environment information related to the cloud service; The cloud platform establishes a data boundary for the cloud service according to the data boundary establishment request; When the cloud service receives a first access request for the cloud service generated by a second tenant or the first tenant, the cloud platform compares the information carried in the first access request with the constraints in the data boundary. If the information carried in the first access request matches the constraints in the data boundary, the cloud service is allowed to respond to the first access request. If the information carried in the first access request does not match the constraints in the data boundary, the cloud service is not allowed to respond to the first access request, wherein the information carried in the first access request includes one or more of first identity subject information, first access resource information, first network information, first device information for initiating the first access request, and first trusted execution environment information.
2. The method according to claim 1, characterized in that The first tenant and the second tenant are registered on the cloud platform, the role of the first tenant is an administrator of the data boundary, and the role of the second tenant is a visitor of the data boundary.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: The cloud platform receives a request for adding a constraint condition for the data boundary input by the first tenant; The cloud platform adds the first constraint indicated by the constraint adding request in the data boundary, wherein the first constraint is one or more of second identity subject information, second access resource information, second network information, second device information for initiating the access request, and second trusted execution environment information.
4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The cloud platform receives a request for removing a constraint condition on the data boundary input by the first tenant; The cloud platform removes the second constraint indicated by the constraint removal request in the data boundary, wherein the second constraint is one or more of third identity subject information, third access resource information, third network information, third device information for initiating the access request, and third trusted execution environment information.
5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The cloud platform receives a data boundary deletion request for the cloud service input by the first tenant; The cloud platform deletes the data boundary indicated by the data boundary deletion request.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The cloud platform receives a data boundary function deactivation request for the cloud service input by the first tenant; The cloud platform disables a data boundary function for the cloud service.
7. The method according to claim 6, characterized in that The method further comprises: The cloud platform receives a data boundary function activation request for the cloud service input by the first tenant; The cloud platform enables data boundary functionality for the cloud service.
8. An access management device based on cloud computing technology, characterized in that: The device is applied to a cloud platform, the cloud platform is used to manage an infrastructure for providing cloud services, the infrastructure includes at least one cloud data center, each of the at least one cloud data center includes a plurality of servers, the cloud service is provided in one or more servers of the at least one cloud data center, and the method includes: A management module, configured to receive a data boundary establishment request for the cloud service input by a first tenant, wherein the data boundary establishment request is used to instruct the cloud platform to establish a data boundary for the cloud service, wherein the data boundary includes at least one constraint condition among identity subject information using the cloud service, access resource information related to the cloud service, network information involved in using the cloud service, device information initiating an access request to the cloud service, and trusted execution environment information related to the cloud service; establish a data boundary for the cloud service according to the data boundary establishment request; An authentication module is used to compare the information carried in the first access request with the constraints in the data boundary when the cloud service receives a first access request generated by the second tenant or the first tenant for the cloud service, and to allow the cloud service to respond to the first access request if the information carried in the first access request matches the constraints in the data boundary; and to not allow the cloud service to respond to the first access request if the information carried in the first access request does not match the constraints in the data boundary, wherein the information carried in the first access request includes one or any combination of first identity subject information, first access resource information, first network information, first device information for initiating the first access request, and first trusted execution environment information.
9. The device according to claim 8, characterized in that The first tenant and the second tenant are registered on the cloud platform, the role of the first tenant is an administrator of the data boundary, and the role of the second tenant is a visitor of the data boundary.
10. The device according to claim 8 or 9, characterized in that The management module is further used for: receiving a request for adding a constraint condition for the data boundary input by the first tenant; Add the first constraint indicated by the constraint adding request in the data boundary, wherein the first constraint is one or more of the second identity subject information, the second access resource information, the second network information, the second device information for initiating the access request, and the second trusted execution environment information.
11. The device according to any one of claims 8 to 10, characterized in that The management module is further used for: receiving a request for removing a constraint condition on the data boundary input by the first tenant; The second constraint indicated by the constraint removal request is removed in the data boundary of the server, wherein the first constraint is one or more of third identity subject information, third access resource information, third network information, third device information for initiating the access request, and third trusted execution environment information.
12. The device according to any one of claims 8 to 11, characterized in that The management module is further used for: receiving a data boundary deletion request for the cloud service input by the first tenant; The data boundary indicated by the data boundary deletion request is deleted.
13. The device according to any one of claims 8 to 12, characterized in that: The management module is further used for: receiving a data boundary function deactivation request for the cloud service input by the first tenant; Disable the data perimeter functionality for the cloud service in question.
14. The device according to claim 13, characterized in that The management module is further used for: receiving a data boundary function activation request for the cloud service input by the first tenant; Enable data boundary functionality for the cloud service.
15. A computer equipment cluster, characterized in that: The computer device cluster includes at least one computing device, each computing device including a processor and a memory; The processor of the at least one computing device is used to execute instructions stored in the memory of the device, so that the computing device cluster executes the access management method based on cloud computing technology as described in any one of claims 1 to 7.
16. A computer program product comprising instructions, characterized in that When the instructions are executed by a computing device, the computing device executes the access management method based on cloud computing technology as described in any one of claims 1 to 7.
17. A computer-readable storage medium, characterized in that: It includes computer program instructions. When the computer program instructions are executed by a computing device, the computing device executes the access management method based on cloud computing technology as described in any one of claims 1 to 7.
Citation Information
Patent Citations
Data access method and device, equipment and storage medium
CN119011174A
Communication method, communication system and device, server and storage medium
CN112235400A
Resource access authentication method and device, storage medium and electronic equipment
CN112995166A
Cloud calculation safety management method and system
CN113010897A
Method and system of providing secure access to a cloud service in a cloud computing environment
EP3794794A1
