Patent Description:
<CIT> describes techniques include identifying permission polices corresponding to a plurality of identities in a network environment, the permission polices specifying what types of actions the plurality of identities are permitted to take with respect to particular network resources; analyzing information describing activity associated with a first identity from the plurality of identities in the network environment; and automatically developing, based on the analysis of the information, a least-privilege profile for the first identity, the least-privilege profile including permissions corresponding to the particular actions with respect to the particular network resources and excluding permissions that do not correspond to the particular actions with respect to the particular network resources.

<CIT> describes a method for managing a security policy having multiple policy items includes the steps of: (a) mapping permissions to the policy items which apply to usage of the permissions so as to determine which of the permissions are granted to groups of users by each of the policy items; (b) identifying at least one of the policy items mapped in step (a) that is in violation of least privilege based on a comparison of an actual permission usage with the security policy; (c) identifying at least one of the policy items mapped in step (a) that increases operational risk; (d) verifying that policy constructs in the security policy are consistent with policy constructs inferred from the actual permission usage; and (e) identifying optimizations of the security policy based on output from one or more of steps (a)-(d).

For simplicity and illustrative purposes, the principles of the present disclosure are described by referring mainly to embodiments and examples thereof. In the following description, numerous specific details are set forth in order to provide an understanding of the embodiments and examples. It will be apparent, however, to one of ordinary skill in the art, that the embodiments and examples may be practiced without limitation to these specific details. In some instances, well known methods and/or structures have not been described in detail so as not to unnecessarily obscure the description of the embodiments and examples. Furthermore, the embodiments and examples may be used together in various combinations.

As discussed above, cloud providers may provide users access to a variety of resources and may implement an access model that may restrict access by the users to the resources. As organizations become more complex with ever increasing numbers of users and resources, the ability to apply the access model and track access configurations may become more complex. In some instances, this may lead to some of the users being granted greater access privileges to the resources than they may practically use. A result of the users being granted overly permissive access privileges may be that the access to the resources may be less secure than when the users are granted least levels of access privileges.

Disclosed herein are systems, apparatuses, methods, and computer-readable media in which a processor may manage assignment of privilege levels to groups of members for resources. That is, instead of assigning privilege levels to members individually for the resources, the processor may assign privilege levels to groups of members for the resources. In addition, the processor may assign the privilege level to a group of members such that the members may have a least privilege level to a resource. The least privilege level may be defined as a minimal level of access privilege that the members may use to perform their intended functions with respect to the resource.

As discussed herein, the processor may determine a respective least privilege level for a resource for each of a plurality of members in a group and may determine, based on the determined respective least privilege levels, a privilege level to be assigned to the group for the resource. The processor may also assign the determined privilege level to the group for the resource and may apply the assigned privilege level to the members of the group for the resource. In some examples, the processor may further assign and apply different privilege levels to some of the members, may partition the group into sub-groups that are assigned different privilege levels with respect to each other, and/or may modify the assigned privilege level.

A technological issue with conventional management of user access to resources may be that the tracking of individual user privilege levels may be overly complex, which may result in greater processor usage and decreased security over data in the resources. Through implementation of various features of the present disclosure, a processor may assign a privilege level to a group of members instead of to the members individually for a resource. In addition, the processor may assign the privilege level to be a least privilege level that, for instance, the majority of the members in the group may use to access the resource in normally performing their duties. As a result, a technological improvement of the features of the present disclosure may be that the complexity in managing member privileges over the resources may be reduced, which may result in a reduced processor utilization and thus, energy and processing power consumption. Additionally, the features of the present disclosure may result in improved security over the resources as the groups (and thus, the members of the groups) may be assigned least privilege levels to the resources.

Reference is first made to <FIG> and <FIG>. <FIG> shows a block diagram of a network environment <NUM>, in which an apparatus <NUM> may manage privilege levels assigned to a group <NUM> of members 122A-122N, in accordance with an embodiment of the present disclosure. <FIG> depicts a block diagram of the apparatus <NUM> depicted in <FIG>, in accordance with an embodiment of the present disclosure. It should be understood that the network environment <NUM> and the apparatus <NUM> of the network environment <NUM> may include additional features and that some of the features described herein may be removed and/or modified without departing from the scopes of the network environment <NUM> and/or the apparatus <NUM>.

As shown in <FIG>, the network environment <NUM> may include the apparatus <NUM>, a plurality of members 122A-122N, resources 130A, 130B, and a network <NUM>. According to examples, the apparatus <NUM> may be a server or other type of computing device, e.g., a network gateway, an access point, or the like, that may provide administrative services to the members 122A-122N, in which the variable "N" may represent a value greater than <NUM>. In some examples, each of the members 122A-122N may be a separate computing device, such as a personal computer, a laptop computer, a tablet computer, a smartphone, a handheld scanning device, or the like. In other examples, each of the members 122A-122N may be a different user, user account, service, application, or the like. For instance, the first member 122A may represent a first user account that is logged into a first computing device, the second member 122B may represent a first service executing a second computing device, etc. As such, for instance, a user may log into different computing devices using a user account at different times and may thus be a member 122A on different computing devices at different times. Likewise, different services may be executing on different computing devices and may access the resources 130A and 130B during the execution of the services.

As also shown, the members 122A-122N may be part of a group <NUM>. Generally speaking, the group <NUM> may be defined as a collection of principals or members, e.g., users, user accounts, terminals, computing devices, services, applications, or the like, that may share a common feature and/or function. By way of example, a group may include members (e.g., user accounts of employees) of a business organization that work in a common department, for instance, the employees in a finance department, an IT department, a facilities management department, a sales department, a marketing department, or the like. As another example, a group may include members of an educational institution, for instance, the faculty in the math department, the faculty in the English department, or the like. In any regard, an administrator of an organization or other personnel may define the criteria for inclusion in the group <NUM> and may determine which members 122A-122N are to be included in the group <NUM>. As a further example, a group may include services that are to perform similar types of operations for a department in an organization or institution.

Although each of the members 122A-122N has been depicted as being included in the group <NUM>, it should be understood that at least one of the members 122A-122N may be outside of the group <NUM>. Additionally, although a single group <NUM> has been depicted in <FIG>, it should be understood that any number of groups may be included in the network environment <NUM> depicted in <FIG>. Likewise, although two resources 130A and 130B are depicted, it should be understood that the network environment <NUM> may include any number of resources.

As further shown in <FIG>, the apparatus <NUM> may communicate with each of the members 122A-122N via a network <NUM>, which may be any suitable type of network through which the members 122A-122N, e.g., the computing devices on which the members 122A-122N are logged in, are executing, etc., and the apparatus <NUM> may communicate with each other, such as the Internet, a wide area network, a local area network, and/or the like. In addition, the members 122A-122N may communicate with the resources 130A and 130B via the network <NUM>. The resources 130A and 130B may each be a server, a service, a virtual machine, a data store, a data store, and/or the like.

As discussed herein, the group <NUM> may be assigned a privilege level, which may also be referenced as a permission level, a role, or the like, to a first resource 130A and a privilege level to the second resource 130B. The privilege levels assigned to the group <NUM> may be the same or may differ for each of the first resource 130A and the second resource 130B. As also discussed herein, the apparatus <NUM>, and more particularly, the processor <NUM>, may assign and/or modify an assigned privilege level to the group <NUM> for the first resource 130A and the privilege level for the second resource 130B. The privilege level may be assigned based on a type of access that the members 122A-122N of the group <NUM> are to have over the first resource 130A and/or the second resource 130B, e.g., the files, documents, data, and/or the like, stored on the first resource 130A. For instance, a first group, e.g., a finance group, may be assigned a higher privilege level to the first resource 130A than a second group, e.g., a sales group, because the members in the first group may normally manipulate the data provided by the first resource 130A whereas the members in the second group may normally read the data provided by the first resource 130A.

The types of access may include, for instance, a contributor type, a writer type, a reader type, a limited reader type, a limited writer type, and/or the like. A group <NUM> that has been assigned the contributor type of access may enable the members 122A-122N of the group <NUM> to have a highest level of access to the data associated with a resource 130A. Thus, for instance, a group <NUM> that has been assigned with the contributor type of access may enable the members 122A-122N of the group <NUM> to read, write, copy, delete, modify, etc., the data. A group <NUM> that has been assigned with the writer type of access may enable the members 122A-122N of the group <NUM> to read and write the data. A group <NUM> that has been assigned with the reader type of access may enable the members 122A-122N to read the data without being able to write, e.g., modify, the data.

As shown in <FIG>, the apparatus <NUM> may include a data store <NUM> on which assigned privilege levels <NUM> of a plurality of groups, including the group <NUM>, may be stored. The data store <NUM> may be a Random Access memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage device, or the like. The privilege levels may be assigned to the groups such that, for instance, when new members are added to an organization and/or when members change groups, the members may be assigned the same privilege level as other members of the group, which may simplify assignment of privilege levels to the members. The assigned privilege levels may also be enforced such that, for instance, access by the members of the groups to the resources may be restricted to their assigned privilege levels. For instance, the apparatus <NUM> may employ role-based access control over the members 122A-122N.

According to examples, and as discussed herein, the apparatus <NUM> may manage the privilege level assigned to a group <NUM> for a resource 130A such that, for instance, the group <NUM> may be assigned an appropriate privilege level for the resource 130A. That is, for instance, the apparatus <NUM> may manage the privilege level assigned to the group <NUM> for the resource 130A such that the group <NUM> may be assigned a least privilege level, e.g., a minimal privilege level, that may enable the members 122A-122N of the group <NUM> to normally perform their intended duties. The apparatus <NUM> may also apply the assigned least privilege level to the group <NUM> such that the members 122A-122N of the group <NUM> may be prevented from having access (e.g., read access, write access, etc.) to the data associated with the resource 130A that exceeds the assigned least privilege level. By assigning and applying the least privilege level to the group <NUM>, access to the data associated with the resource 130A may be better restricted, which may enhance security of the resources 130A.

As shown in <FIG> and <FIG>, the apparatus <NUM> may include a processor <NUM> that may control operations of the apparatus <NUM>. The apparatus <NUM> may also include a memory <NUM> on which data that the processor <NUM> may access and/or may execute may be stored. The processor <NUM> may be a semiconductor-based microprocessor, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and/or other hardware device. The memory <NUM>, which may also be termed a computer readable medium, may be, for example, a Random Access memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage device, or the like. The memory <NUM> may be a non-transitory computer readable storage medium, where the term "non-transitory" does not encompass transitory propagating signals. In any regard, the memory <NUM> may have stored thereon machine-readable instructions that the processor <NUM> may execute.

Although the apparatus <NUM> is depicted as having a single processor <NUM>, it should be understood that the apparatus <NUM> may include additional processors and/or cores without departing from a scope of the apparatus <NUM>. In this regard, references to a single processor <NUM> as well as to a single memory <NUM> may be understood to additionally or alternatively pertain to multiple processors <NUM> and multiple memories <NUM>. In addition, or alternatively, the processor <NUM> and the memory <NUM> may be integrated into a single component, e.g., an integrated circuit on which both the processor <NUM> and the memory <NUM> may be provided. In addition, or alternatively, the operations described herein as being performed by the processor <NUM> may be distributed across multiple apparatuses <NUM> and/or multiple processors <NUM>.

As shown in <FIG>, the memory <NUM> may have stored thereon machine-readable instructions <NUM>-<NUM> that the processor <NUM> may execute. Although the instructions <NUM>-<NUM> are described herein as being stored on the memory <NUM> and may thus include a set of machine-readable instructions, the apparatus <NUM> may include hardware logic blocks that may perform functions similar to the instructions <NUM>-<NUM>. For instance, the processor <NUM> may include hardware components that may execute the instructions <NUM>-<NUM>. In other examples, the apparatus <NUM> may include a combination of instructions and hardware logic blocks to implement or execute functions corresponding to the instructions <NUM>-<NUM>. In any of these examples, the processor <NUM> may implement the hardware logic blocks and/or execute the instructions <NUM>-<NUM>. As discussed herein, the apparatus <NUM> may also include additional instructions and/or hardware logic blocks such that the processor <NUM> may execute operations in addition to or in place of those discussed above with respect to <FIG>.

The processor <NUM> may execute the instructions <NUM> to determine, for each of the members 122A-122N of the group <NUM>, a respective least privilege level for a resource 130A. That is, for instance, the processor <NUM> may determine, for each of the member 122A-122N, a least or lowest privilege level that the member may need to perform their normal duties or functions. By way of example, the processor <NUM> may determine that a first member 122A may normally read data associated with, e.g., stored by, under the control of, or the like, the resource 130A and that a second member 122B may normally write data associated with the resource 130A. Thus, for instance, the processor <NUM> may determine that the least privilege level that the first member 122A may need for the resource 130A is a read type of privilege level and that the least privilege level that the second member 122B may need for the resource 130B is a write type of privilege level.

The processor <NUM> may determine the respective least privilege levels for the resource 130A through implementation of any suitable algorithm or technique. For instance, the processor <NUM> may determine, for each of the members 122A-122N, historical usage of the resource 130A, e.g., the type of access that the members 122A-122N used on the resource 130A. The processor <NUM> may review logs or other data that may show the historical usage over a certain period of time, e.g., the past month, the past three months, and/or the like, etc. By way of example, the processor <NUM> may determine that the least privilege level for the first member 122A may be a read privilege level based on a determination that the first member 122A did not perform any write operations of the data associated with the resource 130A during the time period at which the historical usage was analyzed. In any regard, the processor <NUM> may determine the respective least privilege levels of the members 122A-122N for the resource 130A based on the historical usages of the resource 130A.

The processor <NUM> may execute the instructions <NUM> to determine, based on the determined respective least privilege levels, a privilege level to be assigned to the group <NUM> for the resource 130A. For instance, the processor <NUM> may determine the least privilege level for which a majority of the members 122A-122N are determined to have. In this example, the processor <NUM> may determine the privilege level to be assigned to the group <NUM> to correspond to the determined least privilege level for which the majority of the members 122A-122N are determined to have.

The processor <NUM> may execute the instructions <NUM> to assign the determined privilege level to the group <NUM> for the resource 130A. That is, for instance, the processor <NUM> may store the assignment of the determined privilege level to the group <NUM> for the resource 130A in the data store <NUM>. In addition, the processor <NUM> may execute the instructions <NUM> to apply the assigned privilege level to the group <NUM> for the resource 130A. That is, for instance, the processor <NUM> may control or otherwise cause the level and/or type of access that the members 122A-122N of the group <NUM> may have over the resource 130A to be restricted to the applied permission level. By way of example, the processor <NUM> may directly control how the members 122A-122N may access and/or manipulate data associated with the resource 130A. As another example, the processor <NUM> may direct or otherwise cause the resource 130A to enforce the level and/or type of access that the members 122A-122N may have over the resource 130A.

According to examples, the processor <NUM> may determine whether any of the members 122A-122N have a least privilege level that is lower than the assigned privilege level of the group <NUM>. In these examples, the processor <NUM> may identify those members 122A and may assign a least privilege level to the identified member 122A or members that is lower than the privilege level assigned to the group <NUM> for the resource 130A. In addition, the processor <NUM> may apply the lower least privilege level to the identified member 122A or members for the resource 130A.

According to examples, the processor <NUM> may determine whether any of the members 122A-122N of the group <NUM> has a determined least privilege level that exceeds the assigned privilege level to the group <NUM> for the resource 130A. In these examples, the processor <NUM> may assign a privilege level that is higher than the privilege level assigned to the group <NUM> for the resource 130A. In addition, the processor <NUM> may assign and apply the higher least privilege level to the members of the group for the resource determined to have a determined least privilege level that exceeds the different privilege level assign to the group.

In some examples, the processor <NUM> may determine a number of the members 122A-122N having determined least privilege levels that are lower than the assigned privilege level of the group <NUM> for the resource 130A. In these examples, the processor <NUM> may determine whether the determined number exceeds a predetermined value. The predetermined value may be user-defined and/or may be based, for instance, on an intended security level of the resource 130A. Based on the determined number of the members 122A-122N having determined least privilege levels that fall below the predetermined value, the processor <NUM> may partition the group <NUM> into a first sub-group and a second sub-group. In addition, the processor <NUM> may assign the determined privilege level to the first sub-group and may assign a different, e.g., lower or higher, privilege level to the second sub-group. The processor <NUM> may also assign members of the group <NUM> having a determined least privilege level that meets or exceeds the assigned privilege level to the first sub-group and may assign members of the group having a determined least privilege level that is below the assigned privilege level to the second sub-group. The processor <NUM> may further store the assignments of the members of the group <NUM> in the data store <NUM>.

In some examples, the processor <NUM> may determine whether the sub-groups of the group <NUM> are to be further partitioned, for instance, based on a determined number of the members 122A-122N in the sub-groups. That is, the processor <NUM> may determine whether a sub-group is to be further partitioned into descendent sub-groups in manners similar to those discussed above with respect to determining whether the group <NUM> is to be partitioned into the sub-groups. The processor <NUM> may also determine that the descendent sub-groups may be further partitioned in similar manners until, for instance, the processor <NUM> determines that no further partitions are to be made.

The partitioning of the group <NUM>, sub-groups, and descendent sub-groups, may add complexity to the assignment of privilege levels to the group <NUM>, sub-groups, and descendent sub-groups, especially as the levels of descendent sub-groups increases. In some examples, the processor <NUM> may determine whether partitioning the group <NUM>, a sub-group, a descendent sub-group, and/or the like, would exceed a complexity threshold, and may partition the group <NUM> into the first sub-group and the second sub-group, may partition a sub-group into descendent sub-groups, etc., based on a determination that the partitioning would not exceed the complexity threshold. The complexity threshold may be user-defined and may be based on any suitable parameters, such as available processing resources, number of members, number of groups, number of descendent sub-groups, and/or the like. Thus, for instance, the processor <NUM> may not partition a group, a sub-group of the group, a descendent sub-group, etc., based on a determination that the number of sub-groups and/or descendant sub-groups exceeds a certain threshold number. In instances in which the processor <NUM> determines that partitioning the group <NUM>, the sub-group, the descendent sub-group, etc., would likely exceed the complexity threshold, the processor <NUM> may not partition the group <NUM>, the sub-group, the descendent sub-group, etc..

According to examples, the processor <NUM> may determine whether the group <NUM> is to be assigned a privilege level for the second resource 130B. That is, the processor <NUM> may determine, for each of the members, a respective least privilege level for the second resource 130b. The processor <NUM> may also determine, based on the determined respective least privilege levels for the second resource 130B, a second privilege level to be assigned to the group <NUM> for the second resource 130B. The processor <NUM> may further assign the determined second privilege level to the group <NUM> for the second resource 130B and may apply the assigned second privilege level to the group <NUM> for the second resource 130B. The processor <NUM> may still further partition the group <NUM> and/or assign lower or higher privilege levels to some of the members 122A-122N for the second resource 130B in manners similar to those discussed herein with respect to the first resource 130A.

According to examples, the processor <NUM> may determine whether the assigned privilege level to the group <NUM> for the resource 130A is to be modified. In these examples, the processor <NUM> may determine a number of the members 122A-122N that have least privilege levels that are lower than the assigned privilege level of the group <NUM> for the resource 130A. That is, for instance, the processor <NUM> may determine whether the assigned privilege level of the group <NUM> is to be modified based on a number of the members 122A-122N having least privilege levels that are lower than the assigned privilege level of the group <NUM>. The number of the members 122A-122N may correspond to any suitable number, e.g., a total number, a percentage value of the total number of members 122A-122N in the group <NUM>, or the like.

The processor <NUM> may also determine whether the determined number of the members 122A-122N that have least privilege levels that are lower than the assigned privilege level of the group exceeds a predefined threshold value. The predefined threshold level may be user-defined and may be set based on, for instance, an intended security level associated with the group <NUM> and/or the resource 130A. Thus, for instance, the predefined threshold level may be set to a lower level in instances in which a higher level of security is intended and to a higher level in instances in which a lower level of security is intended. By way of example in which a higher level of security is intended, by setting the predefined threshold level to a lower number, the privilege level assigned to the group <NUM> may more likely be reduced.

The processor <NUM> may, based on the determined number exceeding the predefined threshold value, determine that the assigned privilege level of the group is to be modified. In an example in which the predefined threshold value is <NUM>%, the processor <NUM> may determine that the determined number exceeds the predefined threshold value based on <NUM>% or greater of the members 122A-122N having least privilege levels that fall below the assigned privilege level of the group <NUM>. In other examples, the processor <NUM> may determine that the assigned privilege value of the group is not to be modified based on a determination that the determined number falls below the predefined threshold value.

The processor <NUM> may, based on a determination that the privilege level of the group <NUM> is to be modified, assign and store a different privilege level to the group <NUM> for the resource 130A. That is, the processor <NUM> may assign a lower privilege level to the group <NUM> for the resource 130A. In some examples, the lower privilege level may correspond to the determined respective least privilege levels of the members 122A-122N. For instance, the lower privilege level may be equivalent to a majority (or some other number) of the determined respective least privilege levels of the members 122A-122N for the resource 130A. Thus, in an example in which the assigned privilege level is a contributor level, the processor <NUM> may modify the assigned privilege level to a reader or a writer level. The processor <NUM> may also store the assigned different privilege level in the data store <NUM> and may apply the assigned different privilege level of the members 122A-122N for the resource 130A.

According to examples, the processor <NUM> may determine whether any of the members 122A of the group <NUM> has a determined least privilege level that exceeds the different privilege level, e.g., lower privilege level, assigned to the group <NUM>. In these examples, the processor <NUM> may implement an exception for those members 122A of the group <NUM> having determined least privilege levels that exceeds the different privilege level. That is, the processor <NUM> may exempt those members 122A from being assigned the different privilege level. Instead, those members 122A may be assigned the determined privilege level, e.g., the initially assigned privilege level of those members 122A may not be modified. In addition, the processor <NUM> may store the assigned privilege level of those members 122A in the data store <NUM> and may apply the assigned privilege level of those members 122A for the resource 130A.

However, based on a determination that the determined number of the members 122A-122N having least privilege levels that are lower than the assigned privilege level of the group <NUM> falls below the predefined threshold value, the processor <NUM> may determine that the assigned privilege level of the group <NUM> for the resource 130A is not to be modified. In addition, the processor <NUM> may not modify the assigned privilege level of the group <NUM> for the resource 130A. In these examples, the processor <NUM> may identify a member 122A (or members) of the group <NUM> having a determined least privilege level that falls below the assigned privilege level of the group <NUM> for the resource 130A. The processor <NUM> may also assign and store the determined least privilege level to the identified member 122A (or members) of the group <NUM> for the resource 130A. As a result, the member(s) 122A that have determined least privilege levels that fall below the assigned privilege level of the group <NUM> for the resource 130A may be assigned lower privilege levels, which may enhance security of the resource 130A.

In some examples, the processor <NUM> may determine a number of the members 122A-122N having determined least privilege levels that are lower than the assigned privilege level of the group. In these examples, the processor <NUM> may determine whether the determined number exceeds a predetermined value. The predetermined value may be user-defined and may be based, for instance, on an intended security level of the resource 130A. Based on the determined number of the members 122A-122N having determined least privilege levels that fall below the predetermined value, the processor <NUM> may partition the group <NUM> into a first sub-group and a second sub-group. In addition, the processor <NUM> may assign the privilege level assigned to the group <NUM>, e.g., the initially assigned privilege level, to the first sub-group and may assign the different privilege level, e.g., the modified privilege level, to the second sub-group. The processor <NUM> may also assign members of the group <NUM> having a determined least privilege level that meets or exceeds the assigned privilege level to the first sub-group and may assign members of the group having a determined least privilege level that is below the assigned privilege level to the second sub-group. The processor <NUM> may further store the assignments of the members of the group <NUM> in the data store <NUM>.

As discussed herein, the processor <NUM> may further partition a sub-group into descendent sub-groups. In addition, the processor <NUM> may determine whether partitioning the group <NUM>, a sub-group, a descendent sub-group, etc., would exceed a complexity threshold, and may partition the group <NUM> into the first sub-group and the second sub-group, partition the sub-group, partition the descendent sub-group, etc., based on a determination that the partitioning would not exceed the complexity threshold. The complexity threshold may be user-defined and may be based on any suitable parameters, such as available processing resources, number of members, number of groups, number of descendent sub-groups, and/or the like. In instances in which the processor <NUM> determines that partitioning the group <NUM>, the sub-group, the descendent sub-group, etc., would likely exceed the complexity threshold, the processor <NUM> may not partition the group <NUM>, the sub-group, the descendent sub-group, etc..

According to examples, the processor <NUM> may determine whether the privilege level of the group <NUM> for the second resource 130B is to be modified. That is, the processor <NUM> may identify a second privilege level assigned to the group <NUM> for a second resource 130B and may determine, for each of the members 122A-122B of the group, a respective least privilege level for the second resource 130B. The processor <NUM> may also determine, based on the determined respective least privilege levels, whether the assigned privilege level of the group <NUM> is to be modified for the second resource 130B and based on a determination that the privilege level of the group <NUM> is to be modified for the second resource 130B, assign and store a different privilege level to the group <NUM> for the second resource 130B. The processor <NUM> may further determine whether any of the members 122A-122N are to have least privilege levels that differ from the privilege level assigned to the group <NUM> in manners similar to those discussed herein with respect to the first resource 130A.

Various manners in which the processor <NUM> of the apparatus <NUM> may operate are discussed in greater detail with respect to the method <NUM> depicted in <FIG>. Particularly, <FIG>, collectively, depict a flow diagram of a method <NUM> for determining whether an assigned permission level of a group <NUM> of members 122A-122N is to be modified and to assigning a different permission level to the group <NUM> based on the determination, in accordance with an embodiment of the present disclosure. It should be understood that the method <NUM> depicted in <FIG> may include additional operations and that some of the operations described therein may be removed and/or modified without departing from the scope of the method <NUM>. The description of the method <NUM> is made with reference to the features depicted in <FIG> and <FIG> for purposes of illustration.

With reference first to <FIG>, at block <NUM>, the processor <NUM> may identify a permission level assigned to a group <NUM> of members 122A-122N over a resource 130A. The permission level may be equivalent to the privilege level discussed elsewhere herein as well as to a role or other equivalent term.

At block <NUM>, the processor <NUM> may determine least permission levels respectively used by the members 122A-122N over the resource 130A over a predefined time period. In addition, at block <NUM>, the processor <NUM> may determine whether the assigned permission level of the group <NUM> over the resource 130A is to be modified based on the determined least permission levels. For instance, the processor <NUM> may determine a number of the members 122A-122N that have used least permission levels over the resource 130A over the predefined time period that are lower than the assigned permission level of the group <NUM> over the resource 130A. The processor <NUM> may also determine whether the determined number exceeds a predefined threshold value and based on the determined number exceeding the predefined threshold value, determine that the assigned permission level of the group <NUM> over the resource 130A is to be modified.

At block <NUM>, the processor <NUM> may assign a different permission level to the group <NUM> over the resource 130A based on a determination that the assigned permission level is to be modified. The processor <NUM> may also store the assigned different permission level in the data store <NUM>. At block <NUM>, the processor further apply the different permission level to the members 122A-122N of the group <NUM> over the resource 130A. That is, for instance, the processor <NUM> may control or otherwise cause the level and/or type of access that the members 122A-122N may have over the resource 130A to be restricted to the different permission level. By way of example, the processor <NUM> may directly control how the members 122A-122N may access and/or manipulate data associated with the resource 130A. As another example, the processor <NUM> may direct or otherwise cause the resource 130A to enforce the level and/or type of access that the members 122A-122N may have over the resource 130A.

In some examples, at block <NUM>, the processor <NUM> may determine whether any of the members 122A-122N of the group <NUM> has a determined least permission level that exceeds the different permission level assigned to the group <NUM> over the resource 130A. In these examples, at block <NUM>, the processor <NUM> may end the method <NUM> based on a determination that none of the members has a determined least permission level over the resource 130A that exceeds the different permission level assigned to the group <NUM> over the resource 130A.

However, based on at least one of the members 122A-122N having a determined least permission level that exceeds the different permission level assigned to the group <NUM> over the resource 130A, at block <NUM> (<FIG>), the processor <NUM> may assign the determined least permission level to the members of the group <NUM> determined to have a determined least permission level that exceeds the different permission level assigned to the group <NUM> over the resource 130A. In addition, at block <NUM>, the processor <NUM> may apply the assigned least permission level to the members of the group <NUM> determined to have a determined least permission level that exceeds the different permission level assigned to the group <NUM> over the resource 130A. The method <NUM> may also end at block <NUM> following block <NUM>.

With reference back to <FIG>, based on the determined number falling below the predefined threshold value at block <NUM>, the processor <NUM> may determine that the assigned permission level of the group <NUM> over the resource 130A is not to be modified as indicated at block <NUM>. In some examples, the processor <NUM> may, at block <NUM> (<FIG>), determine whether any of the members 122A-122N of the group <NUM> has a least permission level that falls below the assigned permission level of the group <NUM> over the resource 130A. Based on a determination that at least one of the members has a least permission level that falls below the assigned permission level of the group <NUM> over the resource 130A, the processor <NUM> may identify those members and at block <NUM>, may assign the determined least permission level to the identified member or members. In addition, at block <NUM>, the processor <NUM> may apply the assigned least permission level to the identified member or members.

However, based on a determination that none of the members 122A-122N of the group <NUM> has a least permission level that falls below the assigned permission level of the group <NUM> over the resource 130A, the processor <NUM> may end the method <NUM> at block <NUM>.

According to examples, based on a determination at block <NUM> that at least one of the members 122A-122N of the group <NUM> has a determined least permission level that exceeds the different permission level assigned to the group <NUM> over the resource 130A, at block <NUM> (<FIG>), the processor <NUM> may determine a number of the members having a least permission level that is lower than the assigned permission level of the group <NUM> over the resource 130A. At block <NUM>, the processor <NUM> may determine whether the determined number of the members at block <NUM> exceeds a predetermined value.

In addition, at block <NUM>, the processor <NUM> may, based on the determined number falling below the predetermined value, partition the group <NUM> into a first sub-group and a second sub-group. The processor <NUM> may also assign (block <NUM>) the permission level assigned to the group <NUM> to the first sub-group and assign (block <NUM>) the different permission level to the second sub-group. The processor <NUM> may also assign members of the group <NUM> having a determined least permission level that meets or exceeds the assigned permission level to the first sub-group and may assign members of the group <NUM> having a determined least permission level that is below the assigned permission level to the second sub-group. The processor <NUM> may further apply and/or enforce the assigned permission levels upon the members in each of the respective sub-groups. The processor <NUM> may still further end (block <NUM>) the method <NUM>.

In some examples, prior to partitioning the group <NUM> at block <NUM> or partitioning a sub-group into descendent sub-groups, etc., the processor <NUM> may determine whether partitioning the group, the sub-group, etc., would exceed a complexity threshold as discussed herein. In addition, the processor <NUM> may partition the group into the first sub-group and the second sub-group, a sub-group into descendent sub-groups, etc., based on a determination that the partitioning would not exceed the complexity threshold. However, the processor <NUM> may not partition the group, the sub-group, the descendent sub-group, etc., based on a determination that the partitioning would exceed the complexity threshold.

With reference back to block <NUM>, based on a determination that the number of the members determined at block <NUM> does not exceed the predetermined value, the processor <NUM> may end the method <NUM>. Following the ending of the method <NUM> at block <NUM>, the processor <NUM> may implement the method <NUM> again for the group <NUM> over another resource 130B and/or for another group <NUM> over the resource 130A. The processor <NUM> may repeat the method <NUM> in this manner for any additional combinations of groups <NUM> and resources.

Some or all of the operations set forth in the method <NUM> may be included as utilities, programs, or subprograms, in any desired computer accessible medium. In addition, the method <NUM> may be embodied by computer programs, which may exist in a variety of forms both active and inactive. For example, they may exist as machine-readable instructions, including source code, object code, executable code or other formats. Any of the above may be embodied on a non-transitory computer readable storage medium.

Examples of non-transitory computer readable storage media include computer system RAM, ROM, EPROM, EEPROM, and magnetic or optical disks or tapes. It is therefore to be understood that any electronic device capable of executing the above-described functions may perform those functions enumerated above.

Turning now to <FIG>, there is shown a block diagram of a computer-readable medium <NUM> that may have stored thereon computer-readable instructions for assigning a privilege level to a group <NUM> of members 122A-122N for a resource 130A, in accordance with an embodiment of the present disclosure. It should be understood that the computer-readable medium <NUM> depicted in <FIG> may include additional instructions and that some of the instructions described herein may be removed and/or modified without departing from the scope of the computer-readable medium <NUM> disclosed herein. The computer-readable medium <NUM> may be a non-transitory computer-readable medium, in which the term "non-transitory" does not encompass transitory propagating signals.

The computer-readable medium <NUM> may have stored thereon computer-readable instructions <NUM>-<NUM> that a processor, such as the processor <NUM> depicted in <FIG> and <FIG>, may execute. The computer-readable medium <NUM> may be an electronic, magnetic, optical, or other physical storage device that contains or stores executable instructions. The computer-readable medium <NUM> may be, for example, Random Access memory (RAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a storage device, an optical disc, and the like.

The processor may fetch, decode, and execute the instructions <NUM> to identify a group <NUM> of members 122A-122N and a resource 130A. That is, the processor may identify a group <NUM> of members 122A-122N for which a privilege level of the group <NUM> is to be determined for a resource 130A. The processor may fetch, decode, and execute the instructions <NUM> to, for each of the members 122A-122N of the group <NUM>, determine historical usage of the resource 130A and determine a respective least privilege level for the resource 130A based on the determined historical usage. The processor may fetch, decode, and execute the instructions <NUM> to determine, based on the determined respective least privilege levels, a privilege level to be assigned to the group <NUM> for the resource 130A. The processor may determine the privilege level to be assigned to the group <NUM> as corresponding to, for instance, a majority of the determined respective least privilege levels. The processor may fetch, decode, and execute the instructions <NUM> to assign the determined privilege level to the group <NUM> for the resource 130A. The processor may further fetch, decode, and execute the instructions <NUM> to store the assigned privilege level of the group for the resource.

According to examples, the processor may fetch, decode, and execute additional instructions to determine a number of the members 122A-122N having least privilege levels that are lower than the assigned privilege level of the group <NUM> for the resource 130A, determine whether the determined number exceeds a predefined threshold value, and based on the determined number exceeding the predefined threshold value, determine that the assigned privilege level of the group <NUM> is to be modified. In addition or alternatively, the processor may fetch, decode, and execute additional instructions to identify a member 122A of the group <NUM> having a determined least privilege level that falls below the assigned privilege level of the group <NUM> and may assign and store the determined least privilege level to the identified member 122A. In addition or alternatively, the processor may fetch, decode, and execute additional instructions to determine whether any of the members 122A of the group <NUM> has a determined least privilege level that exceeds the assigned privilege level of the group <NUM> for the resource 130A and may assign and store the determined least privilege level to the members 122A of the group <NUM> determined to have a determined least privilege level that exceeds the assigned privilege level of the group <NUM> for the resource 130A.

In yet other examples, the processor may fetch, decode, and execute additional instructions to determine a number of the members 122A-122N having least privilege levels that are lower than the assigned privilege level of the group <NUM> for the resource 130A. In these examples, the processor may also determine whether the determined number exceeds a predetermined value and based on the determined number falling below the predetermined value, may partition the group into a first sub-group and a second sub-group. The processor may further assign a first privilege level to the first sub-group and may assign a second privilege level to the second sub-group. The processor may assign the members 122A-122N into the respective sub-groups based on their determined least privilege levels for the resource 130A. The processor may further partition the first sub-group into descendent sub-groups as discussed herein. Additionally, the processor may partition the group and/or the sub-group (as well as any other descendent sub-groups) based on a determination that such partitioning would not result in a complexity threshold being exceeded.

Although described specifically throughout the entirety of the instant disclosure, representative examples of the present disclosure have utility over a \wide range of applications, and the above discussion is not intended and should not be construed to be limiting, but is offered as an illustrative discussion of aspects of the disclosure.

Claim 1:
An apparatus (<NUM>) comprising:
a processor (<NUM>); and
a memory (<NUM>) on which is stored machine-readable instructions that cause the processor to:
determine (<NUM>), for each of a plurality of members (122A-122N) in a group (<NUM>), a respective least privilege level for a resource (130A);
determine (<NUM>), based on the determined respective least privilege levels, a privilege level to be assigned to the group (<NUM>) for the resource (130A);
assign (<NUM>) the determined privilege level to the group (<NUM>) for the resource (130A);
determine (<NUM>) a number of the members having least privilege levels that are lower than the assigned privilege level of the group;
determine (<NUM>) whether the determined number exceeds a predetermined value; and
based on the determined number falling below the predetermined value,
partition (<NUM>) the group into a first sub-group and a second sub-group;
assign (<NUM>) the privilege level assigned to the group to the first sub-group; and
assign (<NUM>) a different privilege level to the second sub-group; and
apply (<NUM>) the assigned privilege levels to the members (122A-122N) in each of the respective sub-groups.