US20050138419A1 - Automated role discovery - Google Patents
Automated role discovery Download PDFInfo
- Publication number
- US20050138419A1 US20050138419A1 US10/741,634 US74163403A US2005138419A1 US 20050138419 A1 US20050138419 A1 US 20050138419A1 US 74163403 A US74163403 A US 74163403A US 2005138419 A1 US2005138419 A1 US 2005138419A1
- Authority
- US
- United States
- Prior art keywords
- roles
- identities
- recommended
- attributes
- role
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Definitions
- the present invention relates generally to the field of software and in particular to a system and method of automated role discovery in role based control systems.
- Role based control systems comprise an emerging and promising class of control systems that simplify and streamline the control task by elevating system control rules and decisions from the individual user or process level to a group level.
- the grouping of identities in a role based control system reflects the roles the corresponding individuals have as part of an organization that owns, controls, and/or manages the system.
- RBAC Role Based Access Control
- I Information Technology
- RBAC Access Control
- Access control is defined as the means by which the ability to utilize the system is explicitly enabled or restricted in some way. Access control typically comprises both physical and system-based controls. Computer-based access controls can prescribe not only which individuals or processes may have access to a specific system resource, but also the type of access that is permitted. These controls may be implemented in the computer system or in external devices.
- RBAC access decisions are based on the roles that individual users have as part of an organization. Users take on assigned roles (such as engineer, manager, and human resources (HR) personnel). Access rights are grouped by role name, and the use of resources is restricted to individuals authorized to assume the associated role. For example, an HR employee may require full access to personnel records from which engineers should be restricted to preserve privacy, and engineers may require full access to technical design or product data from which HR employees should be restricted to preserve secrecy, while engineering managers require limited access to both types of data. Rather than set up (and maintain) each individual employee's access controls to the personnel and technical data, under RBAC, three roles may be defined: HR, engineer, and manager. All individuals in the organization who perform the associated role are grouped together, and access controls are assigned and maintained on a per-group basis.
- roles to control access can be an effective means for developing and enforcing enterprise-specific security policies, and for streamlining the security management process.
- User membership into roles can be revoked easily and new memberships established as job assignments dictate.
- New roles and their concomitant access privileges can be established when new operations are instituted, and old roles can be deleted as organizational functions change and evolve. This simplifies the administration and management of privileges; roles can be updated without updating the privileges for every user on an individual basis.
- the present invention relates to a method of automatic role discovery.
- the method includes automatically extracting identities and associated attributes from one or more data sources, and automatically clustering the identities to form recommended roles, based on those attributes.
- the recommended roles are incorporated into a role based control system. Additionally, the recommended roles may optionally be reviewed by an administrator prior to the incorporation, and the user may optionally modify the recommended roles. These modifications cause an automatic re-clustering of the identities to form revised recommended roles, and the revised recommended roles are then incorporated into the role based control system.
- the present invention relates to a method of auditing the access permissions of an information technology (IT) system via a role based access control system.
- the auditing method comprises automatically generating initial roles of individuals having access to the IT system, based on attributes associated with the individuals' identities.
- subsequent roles of individuals then having access to the IT system are automatically generated based on attributes then associated with the identities.
- the initial roles and the subsequent roles are then compared to discover erroneous system accesses.
- the present invention relates to a method of refining roles in a role based control system.
- the method comprises automatically generating initial roles of identities based on attributes associated with the identities.
- the initial roles are then aggregated to generate refined roles.
- One procedure for aggregating the initial roles is to define the role description of at least two of the initial roles as an attribute of each identity in each of the initial rolls, and automatically generating refined roles of identities based on attributes associated with the identities, including the newly defined attributes.
- FIG. 1 is a functional block diagram of an automatic role discovery method according to one embodiment of the present invention.
- FIG. 2 is a functional block diagram of an access audit method according to one embodiment of the present invention.
- FIG. 3 is a flow diagram depicting a role definition algorithm according to one embodiment of the present invention.
- the present invention relates to a “bottom-up” role discovery process.
- existing roles in the organization are discovered by an analysis of the organization's IT infrastructure.
- access roles are discovered by an analysis of the existing IT system security structure.
- user entitlement data the systems, programs, resources, and data that a user has permission to access or modify—may be extracted for each user from the existing IT system. Users with the same or similar entitlements may then be intelligently clustered into groups that reflect their actual, existing roles within the organization.
- the bottom-up method of role discovery avoids the significant investment in time and effort required to define roles in a top-down process, it may also circumvent a disconnect between an organization's perceived roles and its actual roles. That is, the bottom-up method of role discovery is likely to be more accurate in that it reflects the actual, existing roles of users in the organization, as opposed to an individual's or committee's view of what such roles should look like.
- Another significant advantage to the bottom-up role discovery process of the present invention is that it may be automated. That is, the process may be programmed in software and performed by one or more computers, taking advantage of powerful data mining tools and methodologies, and making the process feasible for very large data sets.
- the term “automatically” means the associated action is performed in software on a computer, as opposed to being performed manually.
- Role Based Access Control a security application that restricts and manages users' access to an organization's resources.
- RBAC Role Based Access Control
- many other role based control systems are possible.
- the operational parameters of a system may vary based on the role of a user, such as pilots having different roles experiencing correspondingly varying levels of performance and difficulty in a flight simulator, based on their role (which may, for example, model license level, experience, or type of aircraft for which the pilot is qualified).
- an IT resource may not have a role based access control; however, the present invention may still be used to define the access controls for that resource. While the present invention is described herein as applied to a RBAC system, the invention is not so limited.
- the role discovery process of the present invention may be advantageously applied to any role based control system, and the scope of the invention is determined by the claims, and is not limited to the exemplary embodiments and applications described herein.
- FIG. 1 depicts a bottom-up role discovery process according to one embodiment of the present invention, indicated generally by the numeral 10 .
- the role discovery process begins by analyzing data sources 12 .
- data sources 12 may include, for example, IT resources such as computer systems, communications channels, and the like; HR systems such as payroll, personnel databases and management applications, and the like; applications such as computer aided design tools, software development and version control tools, web applications, and the like; databases such as DB 2 , Oracle, and the like; and operating system security and access parameters relevant to an operating system, such as groups in Unix, administrators in Windows NT, and the like.
- FIG. 1 depicts a Linux system 14 and Windows system 16 as representative data sources 12 .
- a wide range of data may be extracted from the data sources 12 by data extraction and transformation tools 18 .
- the data extraction and transformation tools 18 may, in general, comprise a wide variety of data mining and analysis tools.
- the data extraction and transformation tools 18 may create lists of identities, and attributes associated with those identities. Attributes may include personal information such as employee title, location, date of hire, overtime/exempt status, and the like.
- a particular class of attributes of interest, defined herein as entitlements are attributes associated with an identity that define or relate to the user's permissions, authorizations, and levels of access to organization resources.
- entitlements may include the computer systems to which a user has access (i.e., an account or log in), the groups to which a user is assigned, file permissions, software or other resource licenses, communications system accesses, and the like.
- the data extraction and transformation tools 18 also intelligently transform attributes, including entitlements, from disparate data sources to a common format. For example, the file permissions, groups, and similar entitlement attributes relevant to a Unix operating system do not compare directly to similar entitlements for a Macintosh, Windows, or other operating system. However, most operating systems implement similar distinctions among users regarding permissions and access.
- the data extraction and transformation tools 18 intelligently assess the attributes, including entitlements, associated with the identities and transform them into a common format, so that like entitlements relating to different data sources 12 may be compared. For example, a user with “administrator” status in a Windows NT system may be equated to a user having a “root” login on a Unix system.
- a comprehensive set of heuristics and rules for transforming entitlements into a common format may be assembled and the transformations executed based on them, according to techniques well known in the art.
- the extracted and transformed data is processed at block 20 , where individuals are clustered into proposed or recommended groups or roles, based on the attributes associated with the individuals.
- roles pertinent to a Role Based Access Control system are generated by clustering identities according to entitlements associated with the identities.
- a variety of intelligent clustering or grouping procedures are known in the art, such as for example, through the use of various proximity algorithms.
- the clustering 20 is a completely automated process, proceeding according to rules, heuristics, and algorithmic constraints selected or programmed into the clustering software.
- the recommended roles generated by the clustering 20 may be reviewed by one or more users at step 22 , such as via a Graphic User Interface (GUI).
- GUI Graphic User Interface
- the user may inspect the recommended roles, and may specify changes to the recommended roles.
- the user may add, delete, modify, join, or split the recommended roles at block 24 .
- the user may combine or aggregate roles to create more general-purpose roles.
- the user may restrict certain identities or classes of identities from a recommended role, perhaps generating a new role to contain the selected identities.
- the user may alter the weighting of various attributes, causing different roles to be generated during the clustering step 20 .
- a wide variety of editing functions may be performed on the recommended roles.
- the clustering at step 20 may be re-executed, generating a new set of recommended roles. This process may be repeated as necessary or desired.
- the ability to inspect automatically generated recommended roles at step 22 , and modify them at step 24 introduces an iterative element of control into the otherwise completely automated bottom-up role discovery process.
- the user may approve the roles, at which point they are implemented into the desired system.
- the generated roles may be passed into a Role Based Access Control (RBAC) system management application 26 .
- RBAC Role Based Access Control
- the system management application 26 then manages the organization's resources, including data sources 12 , defining permissions, access levels, available resources, and the like based on individuals' roles rather than attempting to define such for each individual in the organization on an individual basis.
- FIG. 2 depicts a flow diagram of the audit process, indicated generally by the number 30 .
- the automated role discovery process is performed at time T 1 , as shown in step 32 .
- the automated role discovery process may be completely re-executed at time T 2 , as depicted in step 34 , to generate a new set of roles based on the same set of systems and resources that generated the roles at time T 1 .
- any editing of the automatically-generated roles at T 1 should be noted or recorded by the role discovery application, and the same edits applied—manually or automatically—to the automatically-generated roles at time T 2 .
- the discovered roles from times T 1 and T 2 are compared at step 36 . Differences in the roles are detected and analyzed at step 38 . Such differences may include roles generated at T 1 that were not generated at T 2 , which may indicate that a role or function within the organization has terminated or been disbanded. Alternatively, new roles generated at T 2 that were not generated at T 1 may reflect a function or discipline added to the organization. Also, differences in the memberships of the various corresponding roles will indicate the movement of individuals—those leaving or joining the organization as well as an individual's changing functions within the organization.
- the benign or acceptable detected differences may be incorporated into the RBAC system management at step 40 , such as by adding the newly defined roles, deleting roles no longer justified, moving identities within roles, and the like.
- An additional and significant benefit to the audit process 30 is the ability to discover, through differences in generated roles identified at step 38 , erroneous or no longer justified accesses and permissions.
- roles generated at T 2 may lack certain identities that were part of the corresponding roles generated at T 1 . In this case, those individuals may retain access levels or permissions from their prior assignment to the T 1 role. Identifying such identities may assist the system management program to identify and eliminate potential security threats and weaknesses.
- the automated extraction of data and clustering of individuals into roles according to the present invention may initially generate a large number of relatively small recommended roles.
- the automated clustering process may generate a recommended role comprising individuals that have a specific access level on a particular computer system who share offices in a particular building, when effective role based access control may require a coarser level of granularity, for example, all software engineers.
- the bottom-up automated role discovery process may be implemented in multiple passes, with role definitions from one pass being utilized as entitlements for further clustering in subsequent pass(es). The process also finds utility in scaling to a large number of user attributes.
- FIG. 3 depicts a flow chart describing a multi-pass role discovery process, indicated generally by the number 50 .
- an initial automated role discovery process is initiated at step 54 . This may generate a large number of recommended roles.
- the number of roles, and their properties, are inspected at step 56 . If the roles are of the appropriate granularity, they may be incorporated into a role based control system, such as the role based access control system depicted at step 58 .
- the role definition may be defined as an entitlement and the entitlement added to the list of attributes of each identity within the role.
- the automated role discovery process is then re-executed at step 54 , with the identities having the role memberships as the attributes. This process may be repeated as necessary or desired, until the roles have aggregated to the desired size and scope.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Stored Programmes (AREA)
Abstract
An automated, bottom-up role discovery method for a role based control system includes automatically extracting identities and attributes from data sources and automatically clustering the identities based on the attributes to form recommended roles. The recommended roles may be modified by intervention of an administrator. Additionally, the recommended roles may be aggregated by defining the role definition as an attribute of each constituent identity, and re-clustering the identities to generate refined roles. The recommended, modified, and/or refined roles may then be utilized in a role based control system, such as a role based access control system. Periodically performing the role discovery process provides a means to audit a role based access control system.
Description
- The present invention relates generally to the field of software and in particular to a system and method of automated role discovery in role based control systems.
- Role based control systems comprise an emerging and promising class of control systems that simplify and streamline the control task by elevating system control rules and decisions from the individual user or process level to a group level. In particular, the grouping of identities in a role based control system reflects the roles the corresponding individuals have as part of an organization that owns, controls, and/or manages the system.
- A application for role based control systems is Role Based Access Control (RBAC). With respect to RBAC, access is defined as the ability to utilize a system, typically an Information Technology (IT) resource, such as a computer system. Examples of ways one may utilize a computer include executing programs; using communications resources; viewing, adding, changing, or deleting data; and the like. Access control is defined as the means by which the ability to utilize the system is explicitly enabled or restricted in some way. Access control typically comprises both physical and system-based controls. Computer-based access controls can prescribe not only which individuals or processes may have access to a specific system resource, but also the type of access that is permitted. These controls may be implemented in the computer system or in external devices.
- With RBAC, access decisions are based on the roles that individual users have as part of an organization. Users take on assigned roles (such as engineer, manager, and human resources (HR) personnel). Access rights are grouped by role name, and the use of resources is restricted to individuals authorized to assume the associated role. For example, an HR employee may require full access to personnel records from which engineers should be restricted to preserve privacy, and engineers may require full access to technical design or product data from which HR employees should be restricted to preserve secrecy, while engineering managers require limited access to both types of data. Rather than set up (and maintain) each individual employee's access controls to the personnel and technical data, under RBAC, three roles may be defined: HR, engineer, and manager. All individuals in the organization who perform the associated role are grouped together, and access controls are assigned and maintained on a per-group basis.
- The use of roles to control access can be an effective means for developing and enforcing enterprise-specific security policies, and for streamlining the security management process. User membership into roles can be revoked easily and new memberships established as job assignments dictate. New roles and their concomitant access privileges can be established when new operations are instituted, and old roles can be deleted as organizational functions change and evolve. This simplifies the administration and management of privileges; roles can be updated without updating the privileges for every user on an individual basis.
- The current process of defining roles, often referred to as role engineering, is based on a manual analysis of how an organization operates, and attempts to map that organizational structure to the organization's IT infrastructure. This “top-down” process requires a substantial amount of time and resources, both for the analysis and implementation. The prospect of this daunting task is itself a significant disincentive for organizations using traditional access control methods to adopt RBAC.
- The present invention relates to a method of automatic role discovery. The method includes automatically extracting identities and associated attributes from one or more data sources, and automatically clustering the identities to form recommended roles, based on those attributes. The recommended roles are incorporated into a role based control system. Additionally, the recommended roles may optionally be reviewed by an administrator prior to the incorporation, and the user may optionally modify the recommended roles. These modifications cause an automatic re-clustering of the identities to form revised recommended roles, and the revised recommended roles are then incorporated into the role based control system.
- In another aspect, the present invention relates to a method of auditing the access permissions of an information technology (IT) system via a role based access control system. The auditing method comprises automatically generating initial roles of individuals having access to the IT system, based on attributes associated with the individuals' identities. At a later time, subsequent roles of individuals then having access to the IT system are automatically generated based on attributes then associated with the identities. The initial roles and the subsequent roles are then compared to discover erroneous system accesses.
- In yet another aspect, the present invention relates to a method of refining roles in a role based control system. The method comprises automatically generating initial roles of identities based on attributes associated with the identities. The initial roles are then aggregated to generate refined roles. One procedure for aggregating the initial roles is to define the role description of at least two of the initial roles as an attribute of each identity in each of the initial rolls, and automatically generating refined roles of identities based on attributes associated with the identities, including the newly defined attributes.
-
FIG. 1 is a functional block diagram of an automatic role discovery method according to one embodiment of the present invention. -
FIG. 2 is a functional block diagram of an access audit method according to one embodiment of the present invention. -
FIG. 3 is a flow diagram depicting a role definition algorithm according to one embodiment of the present invention. - In contrast to the “top-down” role definition process of the prior art, the present invention relates to a “bottom-up” role discovery process. In this process, existing roles in the organization are discovered by an analysis of the organization's IT infrastructure. In particular, access roles are discovered by an analysis of the existing IT system security structure. For example, user entitlement data—the systems, programs, resources, and data that a user has permission to access or modify—may be extracted for each user from the existing IT system. Users with the same or similar entitlements may then be intelligently clustered into groups that reflect their actual, existing roles within the organization. Not only does the bottom-up method of role discovery avoid the significant investment in time and effort required to define roles in a top-down process, it may also circumvent a disconnect between an organization's perceived roles and its actual roles. That is, the bottom-up method of role discovery is likely to be more accurate in that it reflects the actual, existing roles of users in the organization, as opposed to an individual's or committee's view of what such roles should look like.
- Another significant advantage to the bottom-up role discovery process of the present invention is that it may be automated. That is, the process may be programmed in software and performed by one or more computers, taking advantage of powerful data mining tools and methodologies, and making the process feasible for very large data sets. As used herein, the term “automatically” means the associated action is performed in software on a computer, as opposed to being performed manually.
- As discussed above, a well known application for role based control systems is Role Based Access Control (RBAC), a security application that restricts and manages users' access to an organization's resources. However, many other role based control systems are possible. For example, the operational parameters of a system may vary based on the role of a user, such as pilots having different roles experiencing correspondingly varying levels of performance and difficulty in a flight simulator, based on their role (which may, for example, model license level, experience, or type of aircraft for which the pilot is qualified). Additionally, an IT resource may not have a role based access control; however, the present invention may still be used to define the access controls for that resource. While the present invention is described herein as applied to a RBAC system, the invention is not so limited. In general, the role discovery process of the present invention may be advantageously applied to any role based control system, and the scope of the invention is determined by the claims, and is not limited to the exemplary embodiments and applications described herein.
-
FIG. 1 depicts a bottom-up role discovery process according to one embodiment of the present invention, indicated generally by thenumeral 10. The role discovery process begins by analyzingdata sources 12. These may include, for example, IT resources such as computer systems, communications channels, and the like; HR systems such as payroll, personnel databases and management applications, and the like; applications such as computer aided design tools, software development and version control tools, web applications, and the like; databases such as DB2, Oracle, and the like; and operating system security and access parameters relevant to an operating system, such as groups in Unix, administrators in Windows NT, and the like. By way of example and without limitation,FIG. 1 depicts a Linuxsystem 14 and Windowssystem 16 asrepresentative data sources 12. - A wide range of data may be extracted from the
data sources 12 by data extraction andtransformation tools 18. The data extraction andtransformation tools 18 may, in general, comprise a wide variety of data mining and analysis tools. The data extraction andtransformation tools 18 may create lists of identities, and attributes associated with those identities. Attributes may include personal information such as employee title, location, date of hire, overtime/exempt status, and the like. A particular class of attributes of interest, defined herein as entitlements, are attributes associated with an identity that define or relate to the user's permissions, authorizations, and levels of access to organization resources. For example, entitlements may include the computer systems to which a user has access (i.e., an account or log in), the groups to which a user is assigned, file permissions, software or other resource licenses, communications system accesses, and the like. In general, the more comprehensive the data extraction process is, the more accurate the discovered roles will be. - In addition to data mining and extraction, the data extraction and
transformation tools 18 also intelligently transform attributes, including entitlements, from disparate data sources to a common format. For example, the file permissions, groups, and similar entitlement attributes relevant to a Unix operating system do not compare directly to similar entitlements for a Macintosh, Windows, or other operating system. However, most operating systems implement similar distinctions among users regarding permissions and access. The data extraction andtransformation tools 18 intelligently assess the attributes, including entitlements, associated with the identities and transform them into a common format, so that like entitlements relating todifferent data sources 12 may be compared. For example, a user with “administrator” status in a Windows NT system may be equated to a user having a “root” login on a Unix system. In general, a comprehensive set of heuristics and rules for transforming entitlements into a common format may be assembled and the transformations executed based on them, according to techniques well known in the art. - The extracted and transformed data is processed at
block 20, where individuals are clustered into proposed or recommended groups or roles, based on the attributes associated with the individuals. In particular, roles pertinent to a Role Based Access Control system are generated by clustering identities according to entitlements associated with the identities. A variety of intelligent clustering or grouping procedures are known in the art, such as for example, through the use of various proximity algorithms. According to the present invention, theclustering 20 is a completely automated process, proceeding according to rules, heuristics, and algorithmic constraints selected or programmed into the clustering software. - Optionally, according to the present invention, the recommended roles generated by the
clustering 20 may be reviewed by one or more users atstep 22, such as via a Graphic User Interface (GUI). The user may inspect the recommended roles, and may specify changes to the recommended roles. - If desired, the user may add, delete, modify, join, or split the recommended roles at
block 24. For example, the user may combine or aggregate roles to create more general-purpose roles. Alternatively, the user may restrict certain identities or classes of identities from a recommended role, perhaps generating a new role to contain the selected identities. Additionally, the user may alter the weighting of various attributes, causing different roles to be generated during theclustering step 20. In general, a wide variety of editing functions may be performed on the recommended roles. - As a result of modifications made to the recommended roles at
step 24, the clustering atstep 20 may be re-executed, generating a new set of recommended roles. This process may be repeated as necessary or desired. As such, the ability to inspect automatically generated recommended roles atstep 22, and modify them atstep 24, introduces an iterative element of control into the otherwise completely automated bottom-up role discovery process. - When the user, at
step 22, is satisfied with the recommended roles, the user may approve the roles, at which point they are implemented into the desired system. For example, where the clustering atstep 20 is based at least partially on entitlements associated with identities, the generated roles may be passed into a Role Based Access Control (RBAC)system management application 26. Thesystem management application 26 then manages the organization's resources, includingdata sources 12, defining permissions, access levels, available resources, and the like based on individuals' roles rather than attempting to define such for each individual in the organization on an individual basis. - According to one aspect of the present invention, the automated role discovery process may be advantageously utilized to perform periodic system audits and updates.
FIG. 2 depicts a flow diagram of the audit process, indicated generally by thenumber 30. - Initially, the automated role discovery process is performed at time T1, as shown in
step 32. Subsequently, the automated role discovery process may be completely re-executed at time T2, as depicted instep 34, to generate a new set of roles based on the same set of systems and resources that generated the roles at time T1. Note that any editing of the automatically-generated roles at T1 should be noted or recorded by the role discovery application, and the same edits applied—manually or automatically—to the automatically-generated roles at time T2. - The discovered roles from times T1 and T2 are compared at
step 36. Differences in the roles are detected and analyzed atstep 38. Such differences may include roles generated at T1 that were not generated at T2, which may indicate that a role or function within the organization has terminated or been disbanded. Alternatively, new roles generated at T2 that were not generated at T1 may reflect a function or discipline added to the organization. Also, differences in the memberships of the various corresponding roles will indicate the movement of individuals—those leaving or joining the organization as well as an individual's changing functions within the organization. - The benign or acceptable detected differences may be incorporated into the RBAC system management at
step 40, such as by adding the newly defined roles, deleting roles no longer justified, moving identities within roles, and the like. - An additional and significant benefit to the
audit process 30 is the ability to discover, through differences in generated roles identified atstep 38, erroneous or no longer justified accesses and permissions. For example, roles generated at T2 may lack certain identities that were part of the corresponding roles generated at T1. In this case, those individuals may retain access levels or permissions from their prior assignment to the T1 role. Identifying such identities may assist the system management program to identify and eliminate potential security threats and weaknesses. - The automated extraction of data and clustering of individuals into roles according to the present invention may initially generate a large number of relatively small recommended roles. For example, the automated clustering process may generate a recommended role comprising individuals that have a specific access level on a particular computer system who share offices in a particular building, when effective role based access control may require a coarser level of granularity, for example, all software engineers. In this case, according to one embodiment of the present invention, the bottom-up automated role discovery process may be implemented in multiple passes, with role definitions from one pass being utilized as entitlements for further clustering in subsequent pass(es). The process also finds utility in scaling to a large number of user attributes.
-
FIG. 3 depicts a flow chart describing a multi-pass role discovery process, indicated generally by thenumber 50. Starting atblock 52, an initial automated role discovery process is initiated atstep 54. This may generate a large number of recommended roles. The number of roles, and their properties, are inspected atstep 56. If the roles are of the appropriate granularity, they may be incorporated into a role based control system, such as the role based access control system depicted atstep 58. - Alternatively, if more generic or higher-level roles are desired, such as for example if the number of roles inspected at
step 56 is excessive, then atstep 50, the role definition may be defined as an entitlement and the entitlement added to the list of attributes of each identity within the role. The automated role discovery process is then re-executed atstep 54, with the identities having the role memberships as the attributes. This process may be repeated as necessary or desired, until the roles have aggregated to the desired size and scope. - Although the present invention has been described herein with respect to particular features, aspects and embodiments thereof, it will be apparent that numerous variations, modifications, and other embodiments are possible within the broad scope of the present invention, and accordingly, all variations, modifications and embodiments are to be regarded as being within the scope of the invention. The present embodiments are therefore to be construed in all aspects as illustrative and not restrictive and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.
Claims (22)
1. A method of automatic role discovery, comprising:
automatically extracting identities and associated attributes from one or more data sources;
automatically clustering said identities to form recommended roles, based on said attributes; and
incorporating said recommended roles into a role based control system.
2. The method of claim 1 further comprising:
optionally reviewing said recommended roles by an administrator prior to said incorporation; and
optionally modifying said recommended roles by the administrator, said modifications causing an automatic re-clustering of said identities to form revised recommended roles; and
wherein incorporating said recommend roles into a role based control system comprises incorporating said revised recommended roles into said role based control system.
3. The method of claim 2 wherein modifying said recommended roles by the administrator comprises weighting said attributes.
4. The method of claim 2 wherein modifying said recommended roles by the administrator comprises altering which of said attributes are considered in said re-clustering.
5. The method of claim 1 further comprising transforming said attributes extracted from said data sources to a common format prior to said clustering.
6. The method of claim 1 wherein said attributes include entitlements, and wherein said clustering is based on said entitlements.
7. The method of claim 6 wherein said entitlements comprise the associated identity's access to resources.
8. The method of claim 1 wherein said role based control system is a role based access control system.
9. The method of claim 1 wherein automatically extracting identities and associated attributes from one or more data sources comprises, for each said data source, automatically forming a list of all identities contained in said data source and, for each said identity, all attributes contained in said data source that are associated with that identity.
10. The method of claim 1 wherein automatically clustering said identities to form recommended roles based on said attributes comprises grouping said identities according to the proximity of disparate identities' attributes.
11. The method of claim 10 wherein said attributes are entitlements, and wherein identities within each said recommended role have a similar level of access to resources.
12. A method of auditing the access permissions of an information technology (IT) system via a role based access control system, comprising:
automatically generating initial roles of identities having access to said IT system, based on attributes associated with said identities;
later, automatically generating subsequent roles of identities then having access to said IT system, based on attributes then associated with said identities; and
comparing said initial roles and said subsequent roles to discover erroneous system accesses.
13. The method of claim 12 wherein automatically generating both said initial roles and said subsequent roles comprises:
automatically extracting identities and associated attributes from one or more data sources;
automatically clustering said identities to form recommended roles, based on said attributes; and
incorporating said recommended roles into a role based control system.
14. The method of claim 13 wherein automatically generating both said initial roles and said subsequent roles further comprises:
optionally reviewing said recommended roles by an administrator prior to said incorporation; and
optionally modifying said recommended roles by the administrator, said modifications causing an automatic re-clustering of said identities to form revised recommended roles; and
wherein incorporating said recommend roles into a role based control system comprises incorporating said revised recommended roles into said role based access control system.
15. A method of refining roles in a role based control system, comprising:
automatically generating initial roles of identities based on attributes associated with said identities; and
aggregating said initial roles to generate refined roles.
16. The method of claim 15 wherein aggregating said initial roles to generate refined roles comprises:
defining the role description of at least two said initial roles as an attribute of each identity in each said at least two initial roles; and
automatically generating refined roles of identities based on attributes associated with said identities, including said newly defined attributes.
17. The method of claim 16 wherein automatically generating both said initial roles and said refined roles comprises:
automatically extracting identities and associated attributes from one or more data sources;
automatically clustering said identities to form recommended roles, based on said attributes; and
incorporating said recommended roles into said role based control system.
18. The method of claim 17 wherein automatically generating both said initial roles and said refined roles further comprises:
optionally reviewing said recommended roles by an administrator prior to said incorporation; and
optionally modifying said recommended roles by the administrator, said modifications causing an automatic re-clustering of said identities to form revised recommended roles; and
wherein incorporating said recommend roles into said role based control system comprises incorporating said revised recommended roles into said role based control system.
19. An automated method of role based access control, comprising:
automatically extracting identities and associated attributes from one or more data sources;
automatically clustering said identities to form initial recommended roles, based on said attributes;
optionally aggregating said initial recommended roles by defining the role description of at least two said recommended roles as an attribute of each identity in each said roles and automatically generating initial refined roles of identities based on attributes associated with said identities, including said newly defined attributes.
incorporating said initial recommended roles and optionally said initial refined roles into said role based control system;
later, automatically extracting identities and associated attributes from said data sources;
automatically clustering said identities to form subsequent recommended roles, based on said attributes;
optionally aggregating said subsequent recommended roles to form subsequent refined roles;
incorporating said subsequent recommended roles and optionally said subsequent refined roles into said role based control system; and
comparing said initial roles and said subsequent roles to discover erroneous system accesses.
20. A computer readable medium including one or more computer programs operative to cause a computer to generate roles suitable for a role based control system, the computer programs causing the computer to perform the steps of:
extracting identities and associated attributes from one or more data sources;
clustering said identities to form recommended roles, based on said attributes; and
incorporating said recommended roles into a role based control system.
21. The computer readable medium of claim 20 , said computer programs causing the computer to further perform the steps of:
displaying said recommended roles prior to said incorporation; and
modifying said recommended roles based on input by an administrator, said modifications causing a re-clustering of said identities to form revised recommended roles; and
wherein incorporating said recommend roles into a role based control system comprises incorporating said revised recommended roles into said role based control system.
22. The computer readable medium of claim 20 , said computer programs causing the computer to further perform the steps of
transforming said attributes extracted from said data sources to a common format prior to said clustering.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/741,634 US20050138419A1 (en) | 2003-12-19 | 2003-12-19 | Automated role discovery |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/741,634 US20050138419A1 (en) | 2003-12-19 | 2003-12-19 | Automated role discovery |
Publications (1)
Publication Number | Publication Date |
---|---|
US20050138419A1 true US20050138419A1 (en) | 2005-06-23 |
Family
ID=34678212
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/741,634 Abandoned US20050138419A1 (en) | 2003-12-19 | 2003-12-19 | Automated role discovery |
Country Status (1)
Country | Link |
---|---|
US (1) | US20050138419A1 (en) |
Cited By (74)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040162781A1 (en) * | 2003-02-14 | 2004-08-19 | Kennsco, Inc. | Monitoring and alert systems and methods |
US20060136991A1 (en) * | 2004-12-17 | 2006-06-22 | International Business Machines Corporation | Method and system for assigning access rights in a computer system |
US20070117635A1 (en) * | 2005-11-21 | 2007-05-24 | Microsoft Corporation | Dynamic spectator mode |
US20070240231A1 (en) * | 2006-03-29 | 2007-10-11 | Haswarey Bashir A | Managing objects in a role based access control system |
US20070276717A1 (en) * | 2006-05-26 | 2007-11-29 | Alburey Aaron D | Headcount estimating system, method and tool |
US20080005115A1 (en) * | 2006-06-30 | 2008-01-03 | International Business Machines Corporation | Methods and apparatus for scoped role-based access control |
US20080082538A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Access management in an off-premise environment |
US20080080526A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Migrating data to new cloud |
US20080080396A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Marketplace for cloud services resources |
US20080082670A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Resilient communications between clients comprising a cloud |
US20080082463A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Employing tags for machine learning |
US20080082546A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote provisioning of information technology |
US20080083025A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Remote management of resource license |
US20080082782A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Location management of off-premise resources |
US20080082490A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Rich index to cloud-based resources |
US20080082667A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote provisioning of information technology |
US20080082480A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Data normalization |
US20080083036A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Off-premise encryption of data storage |
US20080080718A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Data security in an off-premise environment |
US20080082311A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Transformations for virtual guest representation |
US20080082857A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Operating system with corrective action service and isolation |
US20080082467A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Personal data mining |
US20080082652A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | State replication |
US20080082600A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote network operating system |
US20080083040A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Aggregated resource license |
US20080082601A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Resource standardization in an off-premise environment |
US20080082693A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Transportable web application |
US20080082465A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Guardian angel |
US20080082641A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | State reflection |
US20080082466A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Training item recognition via tagging behavior |
US20080082464A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Dynamic environment evaluation and service adjustment |
US20080080497A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Determination of optimized location for services and data |
US20080083031A1 (en) * | 2006-12-20 | 2008-04-03 | Microsoft Corporation | Secure service computation |
US20080079752A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Virtual entertainment |
US20080080552A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Hardware architecture for cloud services |
US20080086758A1 (en) * | 2006-10-10 | 2008-04-10 | Honeywell International Inc. | Decentralized access control framework |
US20080091613A1 (en) * | 2006-09-28 | 2008-04-17 | Microsoft Corporation | Rights management in a cloud |
US20080104699A1 (en) * | 2006-09-28 | 2008-05-01 | Microsoft Corporation | Secure service computation |
US20080104393A1 (en) * | 2006-09-28 | 2008-05-01 | Microsoft Corporation | Cloud-based access control list |
US20080134320A1 (en) * | 2006-11-30 | 2008-06-05 | Saurabh Desai | Method for automatic role activation |
US20080155239A1 (en) * | 2006-10-10 | 2008-06-26 | Honeywell International Inc. | Automata based storage and execution of application logic in smart card like devices |
US20080215450A1 (en) * | 2006-09-28 | 2008-09-04 | Microsoft Corporation | Remote provisioning of information technology |
US20080222096A1 (en) * | 2007-03-05 | 2008-09-11 | Microsoft Corporation | Dynamic computation of identity-based attributes |
US20080295145A1 (en) * | 2007-05-23 | 2008-11-27 | Motorola, Inc. | Identifying non-orthogonal roles in a role based access control system |
US7505995B2 (en) | 2006-06-30 | 2009-03-17 | Microsoft Corporation | Object-relational model based user interfaces |
US20090076865A1 (en) * | 2007-09-17 | 2009-03-19 | Rousselle Philip J | Methods to provision, audit and remediate business and it roles of a user |
US20090144803A1 (en) * | 2007-07-31 | 2009-06-04 | Hewlett-Packard Development Company, L.P. | Computer-Implemented Method for Role Discovery and Simplification in Access Control Systems\ |
US20090172789A1 (en) * | 2007-12-27 | 2009-07-02 | Hewlett-Packard Development Company, L.P. | Policy Based, Delegated Limited Network Access Management |
WO2009105540A1 (en) * | 2008-02-21 | 2009-08-27 | Syracuse University | Active access control system and method |
US20090222882A1 (en) * | 2008-02-29 | 2009-09-03 | Microsoft Corporation | Unified management policy |
US20090328132A1 (en) * | 2008-06-27 | 2009-12-31 | Bank Of America Corporation | Dynamic entitlement manager |
US20100115577A1 (en) * | 2008-10-30 | 2010-05-06 | Kiran Kumar Satya Srinivasa Ratnala | Method of Role Creation |
US20100146584A1 (en) * | 2008-12-08 | 2010-06-10 | Motorola, Inc. | Automatic generation of policies and roles for role based access control |
US20100175111A1 (en) * | 2009-01-07 | 2010-07-08 | Hewlett-Packard Development Company, L.P. | Computer-Implemented Method for Obtaining a Minimum Biclique Cover in a Bipartite Dataset |
US20100281513A1 (en) * | 2008-06-27 | 2010-11-04 | Bank Of America Corporation | Dynamic entitlement manager |
US20100281512A1 (en) * | 2008-06-27 | 2010-11-04 | Bank Of America Corporation | Dynamic community generator |
US7930197B2 (en) | 2006-09-28 | 2011-04-19 | Microsoft Corporation | Personal data mining |
US20110271231A1 (en) * | 2009-10-28 | 2011-11-03 | Lategan Christopher F | Dynamic extensions to legacy application tasks |
US20120174194A1 (en) * | 2009-09-10 | 2012-07-05 | Nec Corporation | Role setting apparatus, and role setting method |
US20130031070A1 (en) * | 2011-07-27 | 2013-01-31 | Aveksa, Inc. | System and Method for Reviewing Role Definitions |
US8635689B2 (en) | 2011-10-27 | 2014-01-21 | International Business Machines Corporation | Hybrid role mining |
US8875230B1 (en) * | 2013-12-19 | 2014-10-28 | Medidata Solutions, Inc. | Controlling access to a software application |
US9280566B2 (en) | 2012-11-02 | 2016-03-08 | Ca, Inc. | System and method for visual role engineering |
US20160379001A1 (en) * | 2015-06-26 | 2016-12-29 | Sap Se | Role Analyzer and Optimizer in Database Systems |
US20170091658A1 (en) * | 2015-09-29 | 2017-03-30 | International Business Machines Corporation | Using classification data as training set for auto-classification of admin rights |
US9679264B2 (en) | 2012-11-06 | 2017-06-13 | Oracle International Corporation | Role discovery using privilege cluster analysis |
US20170201525A1 (en) * | 2016-01-10 | 2017-07-13 | International Business Machines Corporation | Evidence-based role based access control |
US10044722B2 (en) | 2015-04-02 | 2018-08-07 | Sap Se | Behavioral multi-level adaptive authorization mechanisms |
US20180300494A1 (en) * | 2015-10-14 | 2018-10-18 | Minereye Ltd. | Method of identifying and tracking sensitive data and system thereof |
US20190199731A1 (en) * | 2017-12-22 | 2019-06-27 | International Business Machines Corporation | Jointly discovering user roles and data clusters using both access and side information |
US10659523B1 (en) * | 2014-05-23 | 2020-05-19 | Amazon Technologies, Inc. | Isolating compute clusters created for a customer |
US10764299B2 (en) | 2017-06-29 | 2020-09-01 | Microsoft Technology Licensing, Llc | Access control manager |
US11416771B2 (en) * | 2019-11-11 | 2022-08-16 | International Business Machines Corporation | Self-learning peer group analysis for optimizing identity and access management environments |
US20240143798A1 (en) * | 2022-11-02 | 2024-05-02 | Sap Se | Role management system based on an integrated role recommendation engine |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US20020026592A1 (en) * | 2000-06-16 | 2002-02-28 | Vdg, Inc. | Method for automatic permission management in role-based access control systems |
US20020144142A1 (en) * | 2001-04-03 | 2002-10-03 | Dalia Shohat | Automatic creation of roles for a role-based access control system |
US20020147801A1 (en) * | 2001-01-29 | 2002-10-10 | Gullotta Tony J. | System and method for provisioning resources to users based on policies, roles, organizational information, and attributes |
US20020178119A1 (en) * | 2001-05-24 | 2002-11-28 | International Business Machines Corporation | Method and system for a role-based access control model with active roles |
US20040225893A1 (en) * | 2003-05-06 | 2004-11-11 | Oracle International Corporation | Distributed capability-based authorization architecture using roles |
US7185192B1 (en) * | 2000-07-07 | 2007-02-27 | Emc Corporation | Methods and apparatus for controlling access to a resource |
US7219234B1 (en) * | 2002-07-24 | 2007-05-15 | Unisys Corporation | System and method for managing access rights and privileges in a data processing system |
-
2003
- 2003-12-19 US US10/741,634 patent/US20050138419A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088679A (en) * | 1997-12-01 | 2000-07-11 | The United States Of America As Represented By The Secretary Of Commerce | Workflow management employing role-based access control |
US20020026592A1 (en) * | 2000-06-16 | 2002-02-28 | Vdg, Inc. | Method for automatic permission management in role-based access control systems |
US7185192B1 (en) * | 2000-07-07 | 2007-02-27 | Emc Corporation | Methods and apparatus for controlling access to a resource |
US20020147801A1 (en) * | 2001-01-29 | 2002-10-10 | Gullotta Tony J. | System and method for provisioning resources to users based on policies, roles, organizational information, and attributes |
US20020144142A1 (en) * | 2001-04-03 | 2002-10-03 | Dalia Shohat | Automatic creation of roles for a role-based access control system |
US20020178119A1 (en) * | 2001-05-24 | 2002-11-28 | International Business Machines Corporation | Method and system for a role-based access control model with active roles |
US7219234B1 (en) * | 2002-07-24 | 2007-05-15 | Unisys Corporation | System and method for managing access rights and privileges in a data processing system |
US20040225893A1 (en) * | 2003-05-06 | 2004-11-11 | Oracle International Corporation | Distributed capability-based authorization architecture using roles |
Cited By (126)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040162781A1 (en) * | 2003-02-14 | 2004-08-19 | Kennsco, Inc. | Monitoring and alert systems and methods |
US20060136991A1 (en) * | 2004-12-17 | 2006-06-22 | International Business Machines Corporation | Method and system for assigning access rights in a computer system |
US7761905B2 (en) * | 2004-12-17 | 2010-07-20 | International Business Machines Corporation | Method and system for assigning access rights in a computer system |
US20070117635A1 (en) * | 2005-11-21 | 2007-05-24 | Microsoft Corporation | Dynamic spectator mode |
US8025572B2 (en) | 2005-11-21 | 2011-09-27 | Microsoft Corporation | Dynamic spectator mode |
US20070240231A1 (en) * | 2006-03-29 | 2007-10-11 | Haswarey Bashir A | Managing objects in a role based access control system |
US20070276717A1 (en) * | 2006-05-26 | 2007-11-29 | Alburey Aaron D | Headcount estimating system, method and tool |
US20080243856A1 (en) * | 2006-06-30 | 2008-10-02 | International Business Machines Corporation | Methods and Apparatus for Scoped Role-Based Access Control |
US20080005115A1 (en) * | 2006-06-30 | 2008-01-03 | International Business Machines Corporation | Methods and apparatus for scoped role-based access control |
US8458337B2 (en) * | 2006-06-30 | 2013-06-04 | International Business Machines Corporation | Methods and apparatus for scoped role-based access control |
US7505995B2 (en) | 2006-06-30 | 2009-03-17 | Microsoft Corporation | Object-relational model based user interfaces |
US7716280B2 (en) | 2006-09-28 | 2010-05-11 | Microsoft Corporation | State reflection |
US7657493B2 (en) | 2006-09-28 | 2010-02-02 | Microsoft Corporation | Recommendation system that identifies a valuable user action by mining data supplied by a plurality of users to find a correlation that suggests one or more actions for notification |
US20080082782A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Location management of off-premise resources |
US20080082490A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Rich index to cloud-based resources |
US20080082667A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote provisioning of information technology |
US9746912B2 (en) | 2006-09-28 | 2017-08-29 | Microsoft Technology Licensing, Llc | Transformations for virtual guest representation |
US9253047B2 (en) | 2006-09-28 | 2016-02-02 | Microsoft Technology Licensing, Llc | Serialization of run-time state |
US8775677B2 (en) | 2006-09-28 | 2014-07-08 | Microsoft Corporation | Transportable web application |
US20080082311A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Transformations for virtual guest representation |
US20080082857A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Operating system with corrective action service and isolation |
US20080082467A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Personal data mining |
US20080082652A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | State replication |
US20080082600A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote network operating system |
US8719143B2 (en) | 2006-09-28 | 2014-05-06 | Microsoft Corporation | Determination of optimized location for services and data |
US8595356B2 (en) | 2006-09-28 | 2013-11-26 | Microsoft Corporation | Serialization of run-time state |
US20080082671A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Communication link generation in a cloud |
US20080082693A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Transportable web application |
US20080082465A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Guardian angel |
US20080082641A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | State reflection |
US20080082466A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Training item recognition via tagging behavior |
US20080082464A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Dynamic environment evaluation and service adjustment |
US20080080497A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Determination of optimized location for services and data |
US20080082538A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Access management in an off-premise environment |
US20080079752A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Virtual entertainment |
US20080080552A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Hardware architecture for cloud services |
US8402110B2 (en) | 2006-09-28 | 2013-03-19 | Microsoft Corporation | Remote provisioning of information technology |
US20080091613A1 (en) * | 2006-09-28 | 2008-04-17 | Microsoft Corporation | Rights management in a cloud |
US20080104699A1 (en) * | 2006-09-28 | 2008-05-01 | Microsoft Corporation | Secure service computation |
US20080104393A1 (en) * | 2006-09-28 | 2008-05-01 | Microsoft Corporation | Cloud-based access control list |
US8341405B2 (en) | 2006-09-28 | 2012-12-25 | Microsoft Corporation | Access management in an off-premise environment |
US20080080526A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Migrating data to new cloud |
US20080215603A1 (en) * | 2006-09-28 | 2008-09-04 | Microsoft Corporation | Serialization of run-time state |
US20080215450A1 (en) * | 2006-09-28 | 2008-09-04 | Microsoft Corporation | Remote provisioning of information technology |
US8012023B2 (en) | 2006-09-28 | 2011-09-06 | Microsoft Corporation | Virtual entertainment |
US20080082546A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Remote provisioning of information technology |
US8014308B2 (en) | 2006-09-28 | 2011-09-06 | Microsoft Corporation | Hardware architecture for cloud services |
US20080082463A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Employing tags for machine learning |
US7836056B2 (en) | 2006-09-28 | 2010-11-16 | Microsoft Corporation | Location management of off-premise resources |
US7930197B2 (en) | 2006-09-28 | 2011-04-19 | Microsoft Corporation | Personal data mining |
US20080080396A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Marketplace for cloud services resources |
US20080082670A1 (en) * | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Resilient communications between clients comprising a cloud |
US7716150B2 (en) | 2006-09-28 | 2010-05-11 | Microsoft Corporation | Machine learning system for analyzing and establishing tagging trends based on convergence criteria |
US7689524B2 (en) | 2006-09-28 | 2010-03-30 | Microsoft Corporation | Dynamic environment evaluation and service adjustment based on multiple user profiles including data classification and information sharing with authorized other users |
US7680908B2 (en) | 2006-09-28 | 2010-03-16 | Microsoft Corporation | State replication |
US7672909B2 (en) | 2006-09-28 | 2010-03-02 | Microsoft Corporation | Machine learning system and method comprising segregator convergence and recognition components to determine the existence of possible tagging data trends and identify that predetermined convergence criteria have been met or establish criteria for taxonomy purpose then recognize items based on an aggregate of user tagging behavior |
US7647522B2 (en) | 2006-09-28 | 2010-01-12 | Microsoft Corporation | Operating system with corrective action service and isolation |
US7797453B2 (en) | 2006-09-29 | 2010-09-14 | Microsoft Corporation | Resource standardization in an off-premise environment |
US8705746B2 (en) | 2006-09-29 | 2014-04-22 | Microsoft Corporation | Data security in an off-premise environment |
US20080082480A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Data normalization |
US20080083036A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Off-premise encryption of data storage |
US8474027B2 (en) | 2006-09-29 | 2013-06-25 | Microsoft Corporation | Remote management of resource license |
US20080080718A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Data security in an off-premise environment |
US20080083040A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Aggregated resource license |
US20080083025A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Remote management of resource license |
US8601598B2 (en) | 2006-09-29 | 2013-12-03 | Microsoft Corporation | Off-premise encryption of data storage |
US20080082601A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Resource standardization in an off-premise environment |
US20080155239A1 (en) * | 2006-10-10 | 2008-06-26 | Honeywell International Inc. | Automata based storage and execution of application logic in smart card like devices |
US20080086758A1 (en) * | 2006-10-10 | 2008-04-10 | Honeywell International Inc. | Decentralized access control framework |
US8166532B2 (en) | 2006-10-10 | 2012-04-24 | Honeywell International Inc. | Decentralized access control framework |
US9009777B2 (en) * | 2006-11-30 | 2015-04-14 | International Business Machines Corporation | Automatic role activation |
US20080134320A1 (en) * | 2006-11-30 | 2008-06-05 | Saurabh Desai | Method for automatic role activation |
US20080083031A1 (en) * | 2006-12-20 | 2008-04-03 | Microsoft Corporation | Secure service computation |
US20080222096A1 (en) * | 2007-03-05 | 2008-09-11 | Microsoft Corporation | Dynamic computation of identity-based attributes |
US7962493B2 (en) | 2007-03-05 | 2011-06-14 | Microsoft Corporation | Dynamic computation of identity-based attributes |
US20080295145A1 (en) * | 2007-05-23 | 2008-11-27 | Motorola, Inc. | Identifying non-orthogonal roles in a role based access control system |
US9405922B2 (en) * | 2007-07-31 | 2016-08-02 | Hewlett Packard Enterprise Development Lp | Computer-implemented method for role discovery and simplification in access control systems |
US9405921B1 (en) | 2007-07-31 | 2016-08-02 | Hewlett Packard Enterprise Development Lp | Computer-implemented method for role discovery in access control systems |
US20090144803A1 (en) * | 2007-07-31 | 2009-06-04 | Hewlett-Packard Development Company, L.P. | Computer-Implemented Method for Role Discovery and Simplification in Access Control Systems\ |
US20090076865A1 (en) * | 2007-09-17 | 2009-03-19 | Rousselle Philip J | Methods to provision, audit and remediate business and it roles of a user |
US20090172789A1 (en) * | 2007-12-27 | 2009-07-02 | Hewlett-Packard Development Company, L.P. | Policy Based, Delegated Limited Network Access Management |
US8453198B2 (en) * | 2007-12-27 | 2013-05-28 | Hewlett-Packard Development Company, L.P. | Policy based, delegated limited network access management |
US20090235334A1 (en) * | 2008-02-21 | 2009-09-17 | Park Joon S | Active access control system and method |
WO2009105540A1 (en) * | 2008-02-21 | 2009-08-27 | Syracuse University | Active access control system and method |
US8387115B2 (en) | 2008-02-21 | 2013-02-26 | Syracuse University | Active access control system and method |
US8196187B2 (en) | 2008-02-29 | 2012-06-05 | Microsoft Corporation | Resource state transition based access control system |
US20090222881A1 (en) * | 2008-02-29 | 2009-09-03 | Microsoft Corporation | Resource state transition based access control system |
US20090222882A1 (en) * | 2008-02-29 | 2009-09-03 | Microsoft Corporation | Unified management policy |
US8353005B2 (en) | 2008-02-29 | 2013-01-08 | Microsoft Corporation | Unified management policy |
US20100281512A1 (en) * | 2008-06-27 | 2010-11-04 | Bank Of America Corporation | Dynamic community generator |
US20130067589A1 (en) * | 2008-06-27 | 2013-03-14 | Bank Of America Corporation | Dynamic community generator |
US20090328132A1 (en) * | 2008-06-27 | 2009-12-31 | Bank Of America Corporation | Dynamic entitlement manager |
US20100281513A1 (en) * | 2008-06-27 | 2010-11-04 | Bank Of America Corporation | Dynamic entitlement manager |
US8316453B2 (en) * | 2008-06-27 | 2012-11-20 | Bank Of America Corporation | Dynamic community generator |
US8763069B2 (en) | 2008-06-27 | 2014-06-24 | Bank Of America Corporation | Dynamic entitlement manager |
US8225416B2 (en) | 2008-06-27 | 2012-07-17 | Bank Of America Corporation | Dynamic entitlement manager |
US8312515B2 (en) | 2008-10-30 | 2012-11-13 | Hewlett-Packard Development Company, L.P. | Method of role creation |
US20100115577A1 (en) * | 2008-10-30 | 2010-05-06 | Kiran Kumar Satya Srinivasa Ratnala | Method of Role Creation |
US20100146584A1 (en) * | 2008-12-08 | 2010-06-10 | Motorola, Inc. | Automatic generation of policies and roles for role based access control |
US8042150B2 (en) | 2008-12-08 | 2011-10-18 | Motorola Mobility, Inc. | Automatic generation of policies and roles for role based access control |
US8209742B2 (en) * | 2009-01-07 | 2012-06-26 | Hewlett-Packard Development Company, L.P. | Computer-implemented method for obtaining a minimum biclique cover in a bipartite dataset |
US20100175111A1 (en) * | 2009-01-07 | 2010-07-08 | Hewlett-Packard Development Company, L.P. | Computer-Implemented Method for Obtaining a Minimum Biclique Cover in a Bipartite Dataset |
US20120174194A1 (en) * | 2009-09-10 | 2012-07-05 | Nec Corporation | Role setting apparatus, and role setting method |
US20110271231A1 (en) * | 2009-10-28 | 2011-11-03 | Lategan Christopher F | Dynamic extensions to legacy application tasks |
US9106685B2 (en) * | 2009-10-28 | 2015-08-11 | Advanced Businesslink Corporation | Dynamic extensions to legacy application tasks |
US9495393B2 (en) * | 2011-07-27 | 2016-11-15 | EMC IP Holding Company, LLC | System and method for reviewing role definitions |
US20130031070A1 (en) * | 2011-07-27 | 2013-01-31 | Aveksa, Inc. | System and Method for Reviewing Role Definitions |
US8635689B2 (en) | 2011-10-27 | 2014-01-21 | International Business Machines Corporation | Hybrid role mining |
US9280566B2 (en) | 2012-11-02 | 2016-03-08 | Ca, Inc. | System and method for visual role engineering |
US9679264B2 (en) | 2012-11-06 | 2017-06-13 | Oracle International Corporation | Role discovery using privilege cluster analysis |
US8875230B1 (en) * | 2013-12-19 | 2014-10-28 | Medidata Solutions, Inc. | Controlling access to a software application |
US10659523B1 (en) * | 2014-05-23 | 2020-05-19 | Amazon Technologies, Inc. | Isolating compute clusters created for a customer |
US10044722B2 (en) | 2015-04-02 | 2018-08-07 | Sap Se | Behavioral multi-level adaptive authorization mechanisms |
US20160379001A1 (en) * | 2015-06-26 | 2016-12-29 | Sap Se | Role Analyzer and Optimizer in Database Systems |
US9842221B2 (en) * | 2015-06-26 | 2017-12-12 | Sap Se | Role analyzer and optimizer in database systems |
US20170091658A1 (en) * | 2015-09-29 | 2017-03-30 | International Business Machines Corporation | Using classification data as training set for auto-classification of admin rights |
US10679141B2 (en) * | 2015-09-29 | 2020-06-09 | International Business Machines Corporation | Using classification data as training set for auto-classification of admin rights |
US20180300494A1 (en) * | 2015-10-14 | 2018-10-18 | Minereye Ltd. | Method of identifying and tracking sensitive data and system thereof |
US11256821B2 (en) * | 2015-10-14 | 2022-02-22 | Minereye Ltd. | Method of identifying and tracking sensitive data and system thereof |
US10171471B2 (en) * | 2016-01-10 | 2019-01-01 | International Business Machines Corporation | Evidence-based role based access control |
US20170201525A1 (en) * | 2016-01-10 | 2017-07-13 | International Business Machines Corporation | Evidence-based role based access control |
US10764299B2 (en) | 2017-06-29 | 2020-09-01 | Microsoft Technology Licensing, Llc | Access control manager |
US20190199731A1 (en) * | 2017-12-22 | 2019-06-27 | International Business Machines Corporation | Jointly discovering user roles and data clusters using both access and side information |
US10805308B2 (en) * | 2017-12-22 | 2020-10-13 | International Business Machines Corporation | Jointly discovering user roles and data clusters using both access and side information |
US11416771B2 (en) * | 2019-11-11 | 2022-08-16 | International Business Machines Corporation | Self-learning peer group analysis for optimizing identity and access management environments |
US20240143798A1 (en) * | 2022-11-02 | 2024-05-02 | Sap Se | Role management system based on an integrated role recommendation engine |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20050138419A1 (en) | Automated role discovery | |
US7284000B2 (en) | Automatic policy generation based on role entitlements and identity attributes | |
US11451554B2 (en) | Role discovery for identity and access management in a computing system | |
US11451529B2 (en) | Security migration in a business intelligence environment | |
US10367821B2 (en) | Data driven role based security | |
US20050138420A1 (en) | Automatic role hierarchy generation and inheritance discovery | |
US9727744B2 (en) | Automatic folder access management | |
JP2015523661A (en) | Data detection and protection policy for email | |
EP3789899B1 (en) | Charter-based access controls for managing computer resources | |
US8312515B2 (en) | Method of role creation | |
US11321479B2 (en) | Dynamic enforcement of data protection policies for arbitrary tabular data access to a corpus of rectangular data sets | |
Hummer et al. | Adaptive identity and access management—contextual data based policies | |
US20100114897A1 (en) | Indexing and searching a network of multi-faceted entity data | |
Clemente et al. | Sptrack: Visual analysis of information flows within selinux policies and attack logs | |
Wang et al. | A trust and attribute-based access control framework in internet of things | |
Gkioulos et al. | Enhancing usage control for performance: An architecture for systems of systems | |
Diez et al. | Modeling xacml security policies using graph databases | |
JP4723930B2 (en) | Compound access authorization method and apparatus | |
Colantonio et al. | Evaluating the risk of adopting RBAC roles | |
Mont et al. | A systematic approach to privacy enforcement and policy compliance checking in enterprises | |
US11936653B2 (en) | Revision of access control process according to virtual roles of subjects based on attributes thereof | |
Winters et al. | Integrated Rule-Oriented Data System (iRODS) and High Performance Computing (HPC) Requirements Document | |
Wilk | Security of Composite Electronic Services | |
Aldo | Strategic role engineering approach to visual role based access control (V-RBAC) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GUPTA, PRATIK;SAMPATHKUMAR, GOVINDARAJ;KUEHR-MCLAREN, DAVID G.;AND OTHERS;REEL/FRAME:015449/0293;SIGNING DATES FROM 20031217 TO 20040601 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |