Control access to cloud resources in your data using cloud-enabled data tagging and a dynamic access control policy engine

By adopting an attribute-based access control system in a multi-tenant computing system, using tags and attribute management access rights, the problems of complexity and high error rate of permission management in the prior art are solved, and dynamic and accurate permission management is achieved.

CN114641768BActive Publication Date: 2024-11-22MICROSOFT TECHNOLOGY LICENSING LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080074229.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-10-22
Filing Date
2020-10-15
Publication Date
2024-11-22
Estimated Expiration
2040-10-15

AI Technical Summary

Technical Problem

When existing multi-tenant computing systems manage data and resource access, changes in user roles and project responsibilities lead to complex access management and error-prone access, resulting in cumbersome and difficult to track, resulting in users' access to or loss of undeserved resource access. Permissions.

Method used

Adopt attribute-based access control (ABAC) system to manage access rights to users, environments, devices and data by defining and mapping tags or attributes. Use the policy decision engine to make access decisions based on specific policies and attributes, and achieve dynamic and fine-grained Permission management.

Benefits of technology

Simplifies permission management, reduces the burden on administrators, improves the accuracy and consistency of access permissions, avoids permission errors, and adapts to changes in user roles and project responsibilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114641768B_ABST
    Figure CN114641768B_ABST
Patent Text Reader

Abstract

Access to data and resources in a multi-tenant computing system is managed by tagging data and resources with attributes and by tagging users with attributes. Tenant-specific access policies are configured. When an access request is received from a workload, a policy decision engine processes the attributes tagged to the requesting workload (e.g., user, application, etc.) and the attributes tagged to the requested data or resource, given the relevant tenant-specific policies. An access decision is provided in response to the access request, and the access decision can be executed by a tenant-specific execution system.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] Computing systems are currently widely used. Many computing systems host services accessed by multiple different tenants. Each tenant can be a separate organization, so that data and some resources of different tenants are isolated and maintained from each other.

[0002] In some current systems, organizations store relatively large amounts of structured and unstructured data in remote server environments (e.g., in cloud-based data repositories accessed through hosted data storage services). Tenants typically store data directly to the cloud storage system and may also store data through software applications that support cloud applications.

[0003] At the same time, it is not uncommon for such tenants to have a relatively large number of users who need access to the data. As these users spend time in the organization corresponding to the tenant, their roles and project responsibilities can change, expand, and retract. Similarly, at different points in the project lifecycle, the organization may want to enable collaboration between different groups in the organization. This naturally leads to expansion and contraction of the scope of audiences who need access to the data at different times, as well as the types of access required.

[0004] The above discussion is provided only for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter. Summary of the invention

[0005] Access to data and resources in a multi-tenant computing system is managed by tagging data and resources with attributes and by tagging users with attributes. Tenant-specific access policies are configured. When an access request is received from a workload, a policy decision engine processes the attributes tagged to the requesting workload (e.g., user, application, etc.) and the attributes tagged to the requested data or resource, given the associated tenant-specific policy. An access decision is provided in response to the access request, and the access decision can be executed by a tenant-specific execution system.

[0006] This Summary is provided to introduce a selection of concepts in a simplified form that are further described in the Detailed Description below. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all of the disadvantages mentioned in the Background. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a block diagram of one example of a computing system architecture in which attribute-based access control (ABAC) is provided.

[0008] Figure 2is a block diagram illustrating one example of an attribute-based access control management system in more detail.

[0009] Figure 3 is a flow chart illustrating one example of the operation of an ABAC management system in more detail.

[0010] Figure 4 is a block diagram illustrating one example of a tenant repository storing identity-attribute mappings.

[0011] Figure 5 is a flow chart illustrating one example of the operation of an ABAC computing system in greater detail.

[0012] Figure 6 is a block diagram illustrating one example of an access response in more detail.

[0013] Figure 7 It shows the deployment in cloud computing architecture Figure 1 A block diagram of an example of the illustrated architecture.

[0014] Figure 8 is a block diagram illustrating one example of a computing environment that may be used in the architectures shown in the previous figures. DETAILED DESCRIPTION

[0015] As mentioned above, tenants using a multi-tenant computing system often need to add, change, or remove access to data and resources over time. Currently, access is typically managed through a role-based access control (RBAC) system, where users are added to role groups, and role groups are granted permissions to access various data. In addition, it is not uncommon to attach access control lists (ACLs) to the data itself to which the groups have been added.

[0016] However, these types of systems place multiple burdens on content creators and resource owners. For example, content creators and resource owners must understand, manage, and maintain group memberships and nested group permissions. Memberships tend to become stale over time, so it becomes difficult to track the actual permissions that exist for a given content item or given resource. In addition, content and resource creators and owners must understand the permissions granted to each group, as well as the implications of changing permissions. This often means that control over these permissions is delegated to administrative users, or to content owners who understand the security posture and configuration of their own environments. This is tedious and time consuming, and can be error-prone, as incorrect permissions are granted or maintained that should not be granted or maintained. In addition, if a user changes projects or roles, it is the administrator's responsibility to understand all groups that the user has been added to, and take appropriate action to remove the user from groups that the user no longer has access to, which is also difficult to manage and easy to overlook groups, resulting in users having permissions on objects or resources that should have been revoked from the user.

[0017] Thus, this discussion is conducted with respect to an attribute-based access control (ABAC) computing system that allows tags or attributes to be defined and attached to different users, environments, devices, computing system resources, and data. This is done in a multi-tenant manner so that tags and mappings can be done on a tenant-specific basis. In addition, a multi-tenant policy resource / storage system stores tenant-specific policies for granting access given tags or attributes attached to items involved in a particular request for access. A policy decision system is deployed in a trusted execution environment. It obtains the relevant policies and attributes (or tags) associated with any given access request, and, given the relevant policies, obtains the process decision engine's reasoning on the tags or attributes to present an access request decision. The decision can grant or deny access, and can also identify permitted actions when access is granted.

[0018] Figure 1 1 is a block diagram illustrating one example of a computing system environment 100 in which a multi-tenant computing system 102 may be accessed by a variety of different tenant computing systems 104-106, each of which may correspond to a different tenant, and each of which may have a plurality of different users 108-110 and 112-114, respectively. The multi-tenant computing system 102 may host services (e.g., data storage services, application services, or other services) for tenants using the computing systems 104 and 106. Thus, the tenant computing systems 104 and 106 may access the multi-tenant computing system 102 via a network (e.g., a wide area network, a local area network, a cellular network, or various other networks or combinations of networks).

[0019] Figure 1The multi-tenant computing system 102 is also shown in communication with an attribute-based access control (ABAC) computing system 116. Figure 1 , ABAC computing system 116 is shown separately from computing system 102, but this is just an example. It can also be hosted within system 102. Other architectures are also contemplated herein. As described in more detail below, when a user 108-114 or an application or another workload requests access to data or resources of a particular tenant, multi-tenant computing system 102 issues an access request 118 indicating the user or application or other workload requesting access to a particular set of data or resources. ABAC computing system 116 illustratively generates a response 120 to request 118, indicating whether the requested access is granted or denied. If the request is granted, it can also identify the specific action permitted.

[0020] Figure 1 It is also shown that administrative users can access the ABAC computing system 116 either through the multi-tenant computing system 102 or directly. This is indicated by administrative interactions 122. Administrative interactions 122 can be processed by the ABAC computing system 116 to configure various tags or attributes used by a particular tenant, to map these tags or attributes to users, environments, devices, data, computing system resources, etc., and to configure access control policies to be used for the particular tenant.

[0021] Figure 1 It is shown that the multi-tenant computing system 102 and the ABAC computing system 116 may also interact in other ways. This is indicated by block 124.

[0022] Before describing the overall operation of the architecture 100 in more detail, a brief description of some of the items in the architecture 100 and their operation will first be provided. The multi-tenant computing system 102 illustratively has one or more processors or servers 137 that implement a front-end system 126, a back-end system 128, an access management system 130, and multiple tenant-specific data repositories 132-134. Each data repository 132-134 can include content 136-138, respectively. The content can have corresponding tags or attributes 140-142, respectively. The tags or attributes 140-142 can be stored with the corresponding content 136-138, or they can be stored separately. For exemplary purposes only, they are stored with the content. Each tenant-specific data store 132-134 can also store a variety of other information 144-146, respectively.

[0023] The front-end system 126 illustratively exposes interfaces that can be accessed by the different tenant computing systems 104-106. Users 108-110 and 112-114 can interact with these interfaces using the tenant computing systems 104-106, thereby providing input through the front-end computing system 126 to request access to the corresponding tenant's content 136-138 (which can be data, other computing system resources, such as a piece of cloud infrastructure, etc.), and to perform operations on the corresponding tenant's content 136-138. These requests are passed to the back-end system 128, which can perform the desired actions on the content requested for access. However, before performing the operation, the access management system 130 illustratively performs access management tasks to determine whether the requested access and operation can be granted and performed, respectively.

[0024] The multi-tenant computing system 102 also illustratively includes an encryption key computing system 135. The encryption key computing system 135 can be used when encryption keys are needed to access various content items. It can issue encryption keys or retain encryption keys. It can provide access requests to the ABAC computing system 116, asking whether the encryption key should be issued to the requester. Thus, the ABAC computing system 116 can receive access requests 118 generated not only from end users 108-114 or administrative users or applications on the multi-tenant computing system 102, but also from other workloads such as the encryption key computing system 135.

[0025] exist Figure 1 In the example shown, the access management system 130 illustratively includes an ABAC component 148, a role-based access control (RBAC) component 150, a tenant-specific policy enforcement system 152, and it may include a variety of other items 154. The ABAC component 148 itself may include a content tagging component 156, an access request interaction component 158, and it may include other items 160.

[0026] Content creators and administrative users can use the content tagging component 156 to generate and apply tags to various content items. Administrators can also declaratively create and apply tags to other items, such as environments, devices, etc.

[0027] When an access request is made, the access request interaction component 158 ​​illustratively handles the interaction with the ABAC computing system 116 by providing the access request 118, and receives the response 120. It can provide the response to the tenant-specific policy enforcement system 152. Different tenants can choose to handle different responses 120 in different ways. For example, one tenant may want the response to deny access to a content item to generate an explanatory message indicating the reason why access was denied. Another tenant may want the response to return only an error message, or simply not perform the requested access. These are just examples, and the tenant-specific policy enforcement system 152 can be configured on a tenant-specific basis, on an application-specific basis, or in other ways.

[0028] The RBAC component 150 can perform traditional role-based access control or other types of access control. Thus, for example, when an access request is received, the access management system 130 can perform a variety of different types of access control.

[0029] exist Figure 1 In the example shown, the ABAC computing system 116 includes one or more processors or servers 160, an ABAC management system 162, a policy / label information system 164, a multi-tenant attribute (label) storage system 166 (which itself illustratively includes tenant repositories 168-170 that store attribute mappings 172-174, respectively, mapping attributes or labels to different users, computer system resources, devices, environments, data, etc., hereinafter collectively referred to as resources), a multi-tenant policy resource / storage system 176, and a trusted execution environment 178, which includes a policy decision system 180. The ABAC computing system 116 may also include a variety of other items 182.

[0030] like Figure 1 As shown, the multi-tenant policy resource / storage system 176 illustratively includes a set of tenant-specific policy repositories 184-186. In one example, the policies stored in the tenant-specific policy repositories 184-186 can be expressed and modified by users in a standard language. Illustratively, the individual policies are secure and can only be accessed by members of a specific management role. Therefore, the policies are (or can be) tenant-specific and can only be accessed by tenant administrators. Therefore, there is no mixing of policies of different tenants. In addition, policies can be illustratively imported and exported using a standards-based format. These are just examples. Given the various attributes or tags involved in the mapping associated with any particular decision, the policy illustratively defines how access is granted.

[0031] Trusted execution environment 178 illustratively sends and receives information in encrypted form. It prevents unauthorized users (even administrative users) from accessing information in environment 178.

[0032] The policy decision system 180 illustratively includes a workload request processor 188, a policy loading system 190, an attribute (tag) loading system 192, a process decision engine 194, and it may include an environment cleanup system 196 and other items 198. The policy decision system 180 illustratively receives relevant policies (which are relevant to the access request 118) along with relevant tags or attributes. In one example, all or part of the system 180 is a cloud-based service that is described on a per-tenant basis in a trusted execution environment. The workload request processor 188 determines which policies are relevant, which tags or attributes are included in the access request, and which need to be obtained from the multi-tenant attribute storage system 166. The policy loading system 190 accesses the multi-tenant policy resource / storage system 176 to obtain relevant policies from the relevant tenant-based policy repositories 184-186. The policy loading system 190 loads the relevant policies into the process decision engine 194. The attribute (tag) loading system 192 accesses the multi-tenant attribute storage system 166 to obtain any additional attributes or tags that the engine 194 needs and that are not provided by the access request 118. Given the loaded tags or attributes, the process decision engine 194 then executes the loaded relevant policies and generates a response 120. In one example, the response 120 not only indicates whether the requested access is granted or denied, but it can also indicate which specific operations are permitted if access is granted.

[0033] The environment cleanup system 196 then cleans up the environment by deleting any policies and attributes or labels generated during the decision-making process and any other artifacts or information in a secure manner. This is done to prevent surreptitious access to the information.

[0034] Figure 2 1 is a block diagram illustrating one example of an ABAC management system 162 in more detail. In one example, the ABAC management system 162 can isolate the management of data and resource attributes from user attributes. For example, this can be achieved by separating management roles to prevent data administrators from manipulating user attributes. The system 162 can also allow other management functions besides those described herein. Figure 2 The system 162 is shown to include a tag type (or group) generation component 200, a tag generation component 202, a tag application component 204, a policy creation and management component 206, a management and access auditing system 208, an attribute repository 210, an attribute type repository 212, and it may include other items 214. The management and access auditing system 208 may include a management access logging component 216, an access logging component 218, surface logic 220, and it may include other items 222. The attribute repository 210 may include attributes 224, and the attribute type repository 212 may include attribute types 226.

[0035] The tag type generation component 200 illustratively presents an interface that allows an administrative user (via the administrative interaction 122) to define a particular type or group of tags. The tag generation component 202 presents an interface that allows the administrative user to generate those tags, and the tag application component 204 allows the administrative user to apply those tags to the different entities to which they correspond. For example, component 204 allows the administrative user to apply tags to users, data, resources, environments, devices, etc.

[0036] Policy creation and management component 206 illustratively allows administrative users to generate and manage policies. Users can illustratively create, modify, update, and delete policies using component 206. Generated attributes can be stored in data repository 210 as attributes 225, and generated attribute types can be stored in attribute type repository 212 as attribute types 226.

[0037] The management and audit system 208 illustratively records various information indicating the types of management actions that have been taken and the types of data access requests and processing operations that have been taken in the ABAC computing system 116. The management action recording component 216 determines when management actions are requested and taken, and records information indicating those operations. The access recording component 218 determines when access operations are performed and records data indicating those access operations. The presentation logic 220 allows visualization of the recorded information for auditing or other purposes.

[0038] Figure 3 1 is a flow chart that illustrates one example of the operation of the ABAC management system 162 in more detail. The system 162 first detects a request to configure attributes and / or policies for a particular tenant. Figure 3 The system 162 may use its own authentication system, or a separate authentication system, to authenticate the request. This is indicated by box 242. For example, it may verify that the requesting administrator has authenticated the tenant to which it is requesting access. This is indicated by box 244. It may also authenticate the request in other ways, which is indicated by box 246.

[0039] The specific component being used then displays an interface to perform the configuration. This is indicated by box 248. In one example, it may be that an administrator requires that multiple tags or attributes, or mappings or policies be automatically downloaded to the ABAC computing system 116. Therefore, the displayed interface can be used for automated configuration, as shown in box 250. It may be that the administrator is requesting to perform manual configuration, in which case, the appropriate interface is displayed for manual configuration. This is represented by box 252.

[0040] The exposed interface then detects the configuration input to perform the configuration. This is indicated by box 254. For example, in the case where the configuration input is used to generate tags or attribute types, the component 200 generates these types and stores them in the attribute type repository 212. This is indicated by box 256. In the case where the tags (or attributes) themselves are being generated, then the component 202 generates the tags or attributes and stores them in the attribute repository 210. This is indicated by box 258.

[0041] In the case of creating or managing policies, component 206 generates or modifies these policies and stores these policies (or modifications) in corresponding tenant policy repositories 184-186 in the multi-tenant policy resource / storage system 176 (e.g., Figure 2 This is indicated by Figure 3 260 in the flowchart of FIG.

[0042] In the event that the administrator is generating a mapping of attributes or tags to different entities, then the component 204 generates and stores the tag mappings. This is indicated by box 262. The tag mappings may be user identity to attribute mappings 264, computing system resources to attribute mappings 266, devices to attribute mappings 268, environments to attribute mappings 270, or they may include various other resource to attribute mappings 272.

[0043] The management action recording component 216 then records all management actions just performed. Figure 3 274 in the flowchart of FIG.

[0044] The policy / tag information system 164 illustratively supports a search interface that can be accessed by an administrator (or other authorized person) to identify currently existing tags and policies. For example, the system 164 can receive a request to identify all tags that have been applied to a particular user or user group, computing system resource, environment, device, any other resource, etc. It can identify these tags and return a response to the request. Given certain inputs or criteria, it can also illustratively receive a request to identify relevant policies. It can search the multi-tenant policy resource / storage system 176 to identify those policies and generate a response indicating the relevant policies. The policy / tag information system 164 can also be used to obtain other information about tags and policies, those mentioned are for example purposes only.

[0045] Figure 4is a block diagram illustrating one example of a tenant repository 168 in greater detail. As can be seen, the tenant repository 168 includes a plurality of different entity-attribute mappings 280. The mappings may include, for example, a user identity-attribute mapping 264, a resource-attribute mapping 266, a device-attribute mapping 268, an environment-attribute mapping 270, or any of a variety of other attribute mappings 272. The tenant repository 168 may also include other items 282.

[0046] Figure 5 is a flowchart illustrating an example of the operation of the ABAC computing system 116 in receiving an access request and generating a response to the access request. First, assume that the ABAC computing system 116 detects an access request from a workload, requesting access to a resource (e.g., data, cloud infrastructure, etc.). Figure 5 As previously described, the access request may be a user access request for tagged content or tagged resources (tagged with attributes). This is indicated by box 292. The access request may be an administrator access request for configuring attributes or policies or for other management purposes. This is indicated by box 294. The workload requesting access may be an application on the multi-tenant computing system 102. This is indicated by box 296. It may come from the encryption key computing system 135, such as Figure 5 The workload access request may also be any of a variety of other access requests. This is indicated by box 300.

[0047] ABAC computing system 116 forwards access request 118 to policy decision system 180 in trusted execution environment 178. Figure 5 denoted by block 302 in the flowchart of FIG.

[0048] The workload request processor 188 processes the access request 118 to determine which items are being accessed, who is accessing them, whether attributes or tags are provided, etc. The request is processed by Figure 5 In one example, the workload request processor 188 parses the request to identify which attributes, if any, are included with the request. This is indicated by block 304 in the flowchart of FIG. Figure 5The request may include, for example, an identity of the requestor, and any tags or attributes mapped to the requestor. It may include a content identifier that identifies the content for which access is requested, and tags or attributes mapped to the content item. It may include environment data indicating the environment in which the content is located, and tags or attributes corresponding to the environment, etc. The workload request processor 188 illustratively identifies which attributes are included in the request. It also identifies which attributes are still required (e.g., not included in the request). This is indicated by box 308. The access request 118 may include some, but not all, of the required tags or attributes. Thus, the processor 188 identifies any tags or attributes that still need to be obtained.

[0049] The workload request processor 188 also illustratively identifies any relevant policies to be referenced when generating a response 120 to the access request 118. The relevant policies may be identified in the access request 118, or they may need to be obtained. Identifying the relevant policies is indicated by block 310. The identification of the relevant policies may also be derived from other information in the request (e.g., who is making the request, the data or resources being requested, etc.). The request may also be processed in a variety of other ways, as indicated by Figure 5 , as indicated by block 312 in the flowchart of FIG.

[0050] If any tags or attributes are still needed, the attribute (tag) loading system 192 loads any required tags into the trusted execution environment so that they can be accessed by the process decision engine 194. Loading tags is done by Figure 5 The policy loading system 190 may request tags from the multi-tenant attribute (or tag) storage system 166. This is indicated by block 314 in the flowchart of FIG. Figure 5 In one example, the tags are encrypted in transit to and from the trusted execution environment 178 to maintain their security integrity. This is indicated by box 318. Tags can also be loaded in other ways, which is indicated by box 320.

[0051] The policy loading system 190 then loads the relevant policies into the trusted execution environment 178 so they can be accessed by the process decision engine 194. Figure 5 In one example, system 192 may request the relevant policy from multi-tenant policy resource / storage system 176. This is indicated by block 322 in the flowchart of FIG. Figure 5 The policy may be encrypted in transit to and from the trusted execution environment 178. This is indicated by box 326. The policy may also be loaded in other ways, which is indicated by box 328.

[0052] The process decision engine 194 then processes the relevant policies given the loaded attributes to generate an access decision (or response 120) based on the workload access request 118. Figure 5 denoted by block 330 in the flowchart of FIG. Figure 6 An example of an access decision (or response) 120 is shown in FIG. As can be seen, the response 120 illustratively includes an access decision 332 indicating whether access is granted or denied. This is also indicated by Figure 5 The access response 120 may include an identifier identifying an allowed action (or set of actions) 336. This is also indicated by box 338. The access response 120 may include various other items 340. This is indicated by Figure 5 , as indicated by block 342 in the flowchart of .

[0053] The process decision engine 194 then returns the response 120 to the multi-tenant computing system 102 and to the workload that requested it. In one example, this is accomplished by the access request interaction component 158 ​​in the access management system 130 on the multi-tenant computing system 102. The return access response 120 is Figure 5 This is indicated by block 344 in the flowchart of FIG.

[0054] The tenant-specific policy enforcement system 152 then enforces the access decision (or response) 120 it receives from the ABAC computing system 116. The access decision (or response) 120 is enforced by Figure 5 As indicated by block 346 in the flowchart of . As described above, this can be done in a variety of different ways, depending on the type of workload requesting it, and on the specific tenant in which the workload resides.

[0055] Management and access audit system 208 (such as Figure 2 118 and then records the operations just performed by the ABAC computing system 116 in receiving the access request 118 and generating the response 120. Figure 5 For example, it may record information indicating the workload that generated the request 118, the resource requested for access, the time at which the access request was received, the decision, the policy used to generate the decision, and various other information.

[0056] It should be noted that the above discussion has described a variety of different systems, components and / or logic. It should be appreciated that such systems, components and / or logic may include hardware items (such as processors and associated memory, or other processing components, some of which are described below) that perform functions associated with those systems, components and / or logic. In addition, the systems, components and / or logic may consist of software that is loaded into memory and then executed by a processor or server or other computing component, as described below. The systems, components and / or logic may also include different combinations of hardware, software, firmware, etc., some examples of which are described below. These are just some examples of different structures that can be used to form the above-mentioned systems, components and / or logic. Other structures may also be used.

[0057] This discussion has referred to processors and servers. In one example, processors and servers include computer processors with associated memory and timing circuits, not shown separately. They are functional parts of the systems or devices to which they belong, activated by other components or items in those systems and facilitate their functions.

[0058] In addition, many user interface displays have been discussed. They can take many different forms, and many different user-actuated input mechanisms can be set thereon. For example, the user-actuated input mechanism can be a text box, a check box, an icon, a link, a drop-down menu, a search box, etc. They can also be actuated in various ways. For example, a click device (such as a trackball or a mouse) can be used to actuate them. They can be actuated using hardware buttons, switches, joysticks or keyboards, thumb switches or thumb pads, etc. They can also be actuated using virtual keyboards or other virtual actuators. In addition, in the case where the screen displaying them is a touch-sensitive screen, touch gestures can be used to actuate them. In addition, in the case where the device displaying them has a voice recognition component, voice commands can be used to actuate them.

[0059] A number of data repositories are also discussed. It is worth noting that each of them can be broken down into multiple data repositories. All can be local to the system accessing them, all can be remote, or some can be local and others can be remote. This article covers all of these configurations.

[0060] In addition, the drawings show multiple blocks with functions attributed to each block. It should be noted that fewer blocks can be used, so the functions are performed by fewer components. In addition, more blocks can be used with functions distributed between more components.

[0061] Figure 7 yes Figure 1 , except that its elements are arranged in a cloud computing architecture 500. Figure 1Same. Cloud computing provides computing, software, data access, and storage services that do not require the end user to know the physical location or configuration of the system providing the service. In various examples, cloud computing provides services over a wide area network (such as the Internet) using appropriate protocols. For example, a cloud computing provider provides applications over a wide area network, and they can be accessed through a web browser or any other computing component. The software or components of architecture 100 and the corresponding data can be stored on servers at remote locations. Computing resources in a cloud computing environment can be integrated or dispersed at remote data center locations. Cloud computing infrastructure can provide services through shared data centers, even if they appear to be a single access point for users. Therefore, the components and functions described here can be provided from a service provider at a remote location using a cloud computing architecture. Alternatively, they can be provided from a traditional server, or they can be installed directly on the client device, or in other ways.

[0062] This description is intended to include both public and private cloud computing. Cloud computing (public and private) provides essentially seamless pooling of resources and reduces the need to manage and configure the underlying hardware infrastructure.

[0063] Public clouds are managed by the vendor and typically support multiple consumers using the same infrastructure. In addition, in contrast to private clouds, public clouds free end users from managing hardware. Private clouds can be managed by the organization itself, and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installation and repairs.

[0064] exist Figure 7 In the example shown, some items are similar to Figure 1 Items shown in , and they are similarly numbered. Figure 7 Specifically shown are computing systems 102 and 116 that may be located in a cloud 502 (which may be public, private, or a combination where some are public and other parts are private). Thus, users 108-114 access those systems through the cloud 502 using user devices 504-506.

[0065] Figure 7 Another example of a cloud architecture is also depicted. Figure 7 It is also contemplated that some elements of computing systems 102 and 116 may be arranged in cloud 502, while others are not. For example, data repositories 168, 170, 184, 186, 210, and 212 may be arranged outside of cloud 502 and accessed through cloud 502. Regardless of where they are located, they may be directly accessed by devices 504-506, through a network (wide area network or local area network), they may be hosted at a remote site by a service, or they may be provided as a service through the cloud or accessed through a connection service residing in the cloud. All of these architectures are contemplated herein.

[0066] It will also be noted that the architecture 100 or portions thereof can be deployed on a variety of different devices. Some of these devices include servers, desktop computers, laptop computers, tablet computers or other mobile devices, such as palmtop computers, mobile phones, smart phones, multimedia players, personal digital assistants, etc.

[0067] Figure 8 is an example of a computing environment in which architecture 100 or portions thereof (for example) may be deployed. Referring to the figure, an example system for implementing some of the examples includes a computing device in the form of a computer 810 that is programmed to operate as described above. Components of computer 810 may include, but are not limited to, a processing unit 820 (which may include a processor or server from the previous figures), a system memory 830, and a system bus 821 that couples various system components including the system memory to the processing unit 820. The system bus 821 may be any of a variety of types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example and not limitation, such architectures include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus, also known as a mezzanine bus. With respect to Figure 1 The memory and programs described can be deployed in Figure 8 in the corresponding part of .

[0068] Computer 810 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by computer 810, and includes volatile and non-volatile media, removable and non-removable media. As an example and not limitation, computer-readable media can include computer storage media and communication media. Computer storage media is different from and does not include modulated data signals or carrier waves. It includes hardware storage media, including volatile and non-volatile, removable and non-removable media implemented in any method or technology, for storing information, such as computer-readable instructions, data structures, program modules or other data. Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required information and can be accessed by computer 810. Communication media typically embody computer-readable instructions, data structures, program modules or other data in a transmission mechanism, and include any information delivery media. The term "modulated data signal" refers to a signal whose characteristics are set or changed in a manner that encodes information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

[0069] The system memory 830 includes computer storage media in the form of volatile and / or nonvolatile memory, such as read-only memory (ROM) 831 and random access memory (RAM) 832. A basic input / output system 833 (BIOS), containing the basic routines that help to transfer information between elements within the computer 810, such as during startup, is typically stored in ROM 831. RAM 832 typically contains data and / or program modules that are immediately accessible to and / or currently being operated on by the processing unit 820. By way of example and not limitation, Figure 8 Operating system 834 , application programs 835 , other program modules 836 , and program data 837 are illustrated.

[0070] The computer 810 may also include other removable / non-removable volatile / non-volatile computer storage media. For example only, Figure 8A hard disk drive 841 is shown that reads from or writes to a non-removable, non-volatile magnetic medium, and an optical disk drive 855 that reads from or writes to a removable, non-volatile optical disk 856, such as a CD ROM or other optical media. Other removable / non-removable, volatile / non-volatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic cassettes, flash memory cards, digital versatile disks, digital video tapes, solid-state RAM, solid-state ROM, etc. The hard disk drive 841 is typically connected to the system bus 821 via a non-removable memory interface such as interface 840, and the optical disk drive 855 is typically connected to the system bus 821 via a removable memory interface such as interface 850.

[0071] Alternatively or additionally, the functions described herein may be performed at least in part by one or more hardware logic components. For example, but not limited to, exemplary hardware logic component types that may be used include field programmable gate arrays (FPGAs), program-specific integrated circuits (ASICs), program-specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), etc.

[0072] The above discussion and Figure 8 The drives and their associated computer storage media shown in FIG. 8 provide storage of computer readable instructions, data structures, program modules and other data for the computer 810. Figure 8 844, applications 845, other program modules 846, and program data 847. Note that these components may be the same as or different from operating system 834, applications 835, other program modules 836, and program data 837. Operating system 844, applications 845, other program modules 846, and program data 847 are given different numbers here to illustrate that at least they are different copies.

[0073] A user can enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861 such as a mouse, trackball, or touch pad. Other input devices (not shown) may include a joystick, a game controller, a satellite dish, a scanner, and the like. These and other input devices are typically connected to the processing unit 820 through a user input interface 860 coupled to the system bus, but may be connected through other interfaces and bus structures, such as a parallel port, a game port, or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 through an interface such as a video interface 890. In addition to the monitor, the computer may also include other peripheral output devices such as speakers 897 and a printer 896, which may be connected through an output peripheral interface 895.

[0074] The computer 810 operates in a network environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, handheld device, server, router, network PC, peer device or other public network node, and typically includes many or all of the elements described above with respect to the computer 810. Figure 8 The logical connections described in the figure include a local area network (LAN) 871 and a wide area network (WAN) 873, but may also include other networks. Such a networking environment is common in offices, enterprise-wide computer networks, intranets, and the Internet.

[0075] When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873 (e.g., the Internet). The modem 872, which may be internal or external, may be connected to the system bus 821 through the user input interface 860 or other appropriate mechanism. In a networking environment, program modules or portions thereof depicted relative to the computer 810 may be stored in the remote memory storage device. By way of example and not limitation, Figure 8 Remote application programs 885 are illustrated as residing on remote computer 880. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0076] It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of these are considered herein.

[0077] Example 1 is a computer-implemented method comprising:

[0078] receiving an access request from a workload in a multi-tenant computing system, the access request indicating that a requestor is requesting access to a resource; identifying a requestor attribute set corresponding to the requestor and a resource attribute set corresponding to the resource;

[0079] Identify relevant tenant-specific data access policies; and

[0080] Acquire the relevant tenant-specific data access policy from a multi-tenant policy storage system;

[0081] generating an access decision indicating whether the requested access is granted based on the requestor attribute set, the resource attribute set, and the associated tenant-specific data access policy; and

[0082] The access decision is returned to the workload.

[0083] Example 2 is a computer-implemented method of any or all of the previous examples, wherein obtaining the relevant tenant-specific access policy comprises:

[0084] Obtaining the relevant tenant-specific access policy in encrypted form from the multi-tenant policy storage system; and

[0085] The relevant tenant-specific access policy is decrypted.

[0086] Example 3 is a computer-implemented method of any or all of the preceding examples, and also includes:

[0087] determining whether any of the requester attribute set or the resource attribute set is included in the access request; and

[0088] If not, any one of the requester attribute set and the resource attribute set not included in the access request is obtained.

[0089] Example 4 is the computer-implemented method of any or all of the previous examples, wherein obtaining any one of a requester attribute set and a resource attribute set not included in the access request comprises:

[0090] Any one of the requester attribute sets not included in the access request is obtained from a multi-tenant attribute storage system that partitions attributes corresponding to different tenants.

[0091] Example 5 is the computer-implemented method of any or all of the previous examples, wherein obtaining any one of a requester attribute set and a resource attribute set not included in the access request comprises:

[0092] Any one of the resource attribute sets not included in the access request is obtained from the multi-tenant attribute storage system, the multi-tenant attribute storage system dividing the attributes corresponding to different tenants.

[0093] Example 6 is a computer-implemented method of any or all of the previous examples, wherein generating an access decision comprises:

[0094] Obtaining a set of environment attributes corresponding to the environment in which the workload runs;

[0095] Obtaining a device attribute set corresponding to the device initiating the access request; and

[0096] The access decision is generated based on the environment attributes and the device attributes.

[0097] Example 7 is the computer-implemented method of any or all of the previous examples, and also includes:

[0098] generating a user interface using a user-actuatable tag type to generate an input mechanism;

[0099] detecting user actuation of the tag type generating input mechanism indicative of the tag type; and

[0100] The tag type is stored in a tag type repository.

[0101] Example 8 is the computer-implemented method of any or all of the previous examples, and also includes:

[0102] generating a user interface using a user-actuatable tag to generate an input mechanism;

[0103] detecting user actuation of a tag generation input mechanism indicative of a tag of a given tag type; and

[0104] The tags are stored in a tag repository.

[0105] Example 9 is the computer-implemented method of any or all of the previous examples, and also includes:

[0106] generating a user interface using a user-actuatable label mapping input mechanism;

[0107] detecting user actuation of a tag mapping input mechanism indicating a mapping between tags of tag types and resource identifications; and

[0108] The mapping is stored in the multi-tenant attribute storage system.

[0109] Example 10 is the computer-implemented method of any or all of the previous examples, wherein the resource identification identifies one of a user, a device, an environment, or a computing system resource.

[0110] Example 11 is a computer-implemented method of any or all of the previous examples, wherein generating an access decision comprises:

[0111] The access decision is generated to include a set of permitted actions permitted for the requested access.

[0112] Example 12 is a computer system comprising:

[0113] one or more processors;

[0114] A memory storing instructions, which, when executed by the one or more processors, cause the one or more processors to perform steps comprising:

[0115] receiving an access request from a workload in a multi-tenant computing system, the access request indicating that a requestor is requesting access to a resource;

[0116] Acquire a requester attribute set corresponding to the requester and a resource attribute set corresponding to the resource from a multi-tenant attribute storage system;

[0117] Identify relevant tenant-specific data access policies; and

[0118] Acquire the relevant tenant-specific data access policy from a multi-tenant policy storage system;

[0119] generating an access decision indicating whether to grant the requested access based on the requestor attribute set, the resource attribute set, and the associated tenant-specific data access policy; and

[0120] The access decision is returned to the workload.

[0121] Example 13 is the computer system of any or all of the previous examples, wherein obtaining the relevant tenant-specific access policy comprises:

[0122] Obtaining the relevant tenant-specific access policy in encrypted form from the multi-tenant policy storage system; and

[0123] The relevant tenant-specific access policy is decrypted.

[0124] Example 14 is the computer system of any or all of the previous examples, wherein generating the access decision comprises:

[0125] Obtaining a set of environment attributes corresponding to the environment in which the workload runs;

[0126] Obtaining a device attribute set corresponding to the device initiating the access request; and

[0127] Generate access decisions based on environment attributes and device attributes.

[0128] Example 15 is the computer system of any or all of the previous examples, and also includes:

[0129] generating a user interface using a user-actuatable tag type to generate an input mechanism;

[0130] detecting user actuation of a tag type generating input mechanism indicative of a tag type; and

[0131] Store tag types in a tag type repository.

[0132] Example 16 is the computer system of any or all of the previous examples, and also includes:

[0133] generating a user interface using a user-actuatable tag generation input mechanism;

[0134] detecting user actuation of a tag generation input mechanism indicative of a tag of a given tag type; and

[0135] Store the tags in a tag repository.

[0136] Example 17 is the computer system of any or all of the previous examples, and also includes:

[0137] generating a user interface using a user-actuatable label mapping input mechanism;

[0138] detecting user actuation of a tag mapping input mechanism indicating a mapping between tags of tag types and resource identities; and

[0139] Store the mapping in a multi-tenant property storage system.

[0140] Example 18 is the computer system of any or all of the previous examples, wherein the resource identity identifies one of a user, a device, an environment, or a computing system resource.

[0141] Example 19 is a computing system comprising:

[0142] A multi-tenant policy storage system that stores tenant-specific data access policies in a tenant-specific data repository;

[0143] a workload request processor that receives an access request from a workload in a multi-tenant computing system, the access request indicating that a requestor requests access to a resource, the workload request processor identifying a set of requestor attributes corresponding to the requestor and a set of resource attributes corresponding to the resource, and an associated tenant-specific data access policy; and

[0144] An access decision engine obtains the requester attribute set, the resource attribute set and the relevant tenant-specific data access policy, and generates an access decision indicating whether the requested access is granted based on the requester attribute set, the resource attribute set and the relevant tenant-specific data access policy, and returns the access decision to the workload.

[0145] Example 20 is the computing system of any or all of the previous examples, and also includes:

[0146] a management system configured to generate a user interface using a user-actuatable tag type generation input mechanism, detect user actuation of the tag type generation input mechanism indicating a tag type, generate a user interface using the user-actuatable tag generation input mechanism, detect user actuation of the tag generation input mechanism indicating a tag of a given tag type, generate a user interface using a user-actuatable tag mapping input mechanism, and detect user actuation of the tag mapping input mechanism indicating a mapping between tags of the tag type and a resource identity;

[0147] A data repository is configured to store tag types, tags, and tag mappings.

[0148] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A computer-implemented method comprising: receiving an access request from a workload in a multi-tenant computing system, the access request indicating that a requestor is requesting access to a resource; parsing the access request through a tenant-specific execution environment specific to a specific tenant associated with the requestor to identify requestor attributes corresponding to the requestor and resource attributes corresponding to the resource; Based on the information in the access request, select a tenant-specific data access policy from a data access policy set, wherein the selected tenant-specific data access policy is specific to the specific tenant; Accessing a multi-tenant policy storage system including a plurality of tenant-specific policy repositories, wherein each tenant-specific policy repository in the plurality of tenant-specific policy repositories: corresponds to a respective tenant in a plurality of tenants and stores a tenant-specific data access policy set for the respective tenant, the tenant-specific data access policy set being separate from data access policies of other tenants; Obtaining the selected tenant-specific data access policy from a tenant-specific policy repository corresponding to the specific tenant; loading the selected tenant-specific data access policy into the tenant-specific execution environment; generating an access decision indicating whether the requested access is granted based on the requestor attributes, the resource attributes, and the selected tenant-specific data access policy; and The access decision is returned to the workload.

2. The computer-implemented method of claim 1, wherein: Get the selected tenant specific access policy including: Retrieving the selected tenant-specific access policy in encrypted form from the multi-tenant policy storage system; and Decrypts the selected tenant-specific access policy.

3. The computer-implemented method of claim 1 , further comprising: Based on determining that one or more of the requester attributes or the resource attributes are not included in the access request, obtaining the one or more of the requester attributes or the resource attributes that are not included in the access request.

4. The computer-implemented method of claim 3, wherein: Obtaining one or more of the requester attributes or the resource attributes not included in the access request comprises: The requester attributes are obtained from a multi-tenant attribute storage system, and the multi-tenant attribute storage system divides the attributes corresponding to different tenants.

5. The computer-implemented method of claim 3, wherein: Obtaining one or more of the requester attributes or the resource attributes not included in the access request comprises: The resource attributes are obtained from a multi-tenant attribute storage system, and the multi-tenant attribute storage system divides the attributes corresponding to different tenants.

6. The computer-implemented method of claim 1, wherein: Generating the access decision includes: Obtaining an environment attribute corresponding to the environment in which the workload runs; Obtaining device attributes corresponding to the device initiating the access request; and The access decision is generated based on the environment attributes and the device attributes.

7. The computer-implemented method of claim 1 , further comprising: generating a user interface using a user-actuatable tag type to generate an input mechanism; detecting user actuation of said tag type generating input mechanism indicative of a tag type; as well as The tag type is stored in a tag type repository.

8. The computer-implemented method of claim 1, wherein: Each of the plurality of tenants has a plurality of users, and the multi-tenant computing system hosts services for the plurality of users of the plurality of tenants.

9. The computer-implemented method of claim 5, further comprising: generating a user interface using a user-actuatable label mapping input mechanism; detecting user actuation of the tag mapping input mechanism indicating a mapping between tags of tag types and resource identifiers; as well as The mapping is stored in the multi-tenant attribute storage system.

10. The computer-implemented method of claim 9, wherein: The resource identification identifies one of a user, a device, an environment, or a computing system resource.

11. The computer-implemented method of claim 1 , wherein: Generating the access decision includes: The access decision is generated to include a set of permitted actions permitted for the requested access.

12. A computer system comprising: one or more processors; A memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform steps comprising: receiving an access request from a workload in a multi-tenant computing system, the access request indicating that a requestor is requesting access to a resource; parsing the access request through a tenant-specific execution environment specific to a specific tenant associated with the requestor to identify requestor attributes corresponding to the requestor and resource attributes corresponding to the resource; Based on the information in the access request, select a tenant-specific data access policy from a data access policy set, wherein the selected tenant-specific data access policy is specific to the specific tenant; Accessing a multi-tenant policy storage system including a plurality of tenant-specific policy repositories, wherein each tenant-specific policy repository in the plurality of tenant-specific policy repositories: corresponds to a respective tenant in a plurality of tenants and stores a tenant-specific data access policy set for the respective tenant, the tenant-specific data access policy set being separate from data access policies of other tenants; Obtaining the selected tenant-specific data access policy from a tenant-specific policy repository corresponding to the specific tenant; loading the selected tenant-specific data access policy into the tenant-specific execution environment; generating an access decision indicating whether to grant the requested access based on the requestor attributes, the resource attributes, and the selected tenant-specific data access policy; and The access decision is returned to the workload.

13. The computer system of claim 12, wherein: Get the selected tenant specific access policy including: Retrieving the selected tenant-specific access policy in encrypted form from the multi-tenant policy storage system; and Decrypts the selected tenant-specific access policy.

14. The computer system of claim 12, wherein: Generating the access decision includes: Obtaining an environment attribute set corresponding to the environment in which the workload runs; Obtaining a device attribute set corresponding to the device initiating the access request; and The access decision is generated based on the environment attributes and the device attributes.

15. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors of a computing device, cause the computing device to perform the method of any one of claims 1-11.