Graph-based access control
Graph-based access control (GBAC) is a declarative way to define access rights, task assignments, recipients and content in information systems. Access rights are granted to objects like files or documents, but also business objects such as an account. GBAC can also be used for the assignment of agents to tasks in workflow environments. Organizations are modeled as a specific kind of semantic graph comprising the organizational units, the roles and functions as well as the human and automatic agents (i.a. persons, machines). The main difference with other approaches such as role-based access control or attribute-based access control is that in GBAC access rights are defined using an organizational query language instead of total enumeration.
History
[edit]The foundations of GBAC go back to a research project named CoCoSOrg (Configurable Cooperation System) [[1]] (in English language please see[2]) at Bamberg University. In CoCoSOrg an organization is represented as a semantic graph and a formal language is used to specify agents and their access rights in a workflow environment. Within the C-Org-Project at Hof University's Institute for Information Systems (iisys), the approach was extended by features like separation of duty, access control in virtual organizations [3] and subject-oriented access control.[4]
Definition
[edit]Graph-based access control consists of two building blocks:
- A semantic graph modeling an organization
- A query language.
Organizational graph
[edit]
The organizational graph is divided into a type and an instance level. On the instance level there are node types for organizational units, functional units and agents. The basic structure of an organization is defined using so called "structural relations". They define the "is part of"- relations between functional units and organizational units as well as the mapping of agents to functional units. Additionally there are specific relationship types like "deputyship" or "informed_by". These types can be extended by the modeler. All relationships can be context sensitive through the usage of predicates.
On the type level organizational structures are described in a more general manner. It consists of organizational unit types, functional unit types and the same relationship types as on the instance level. Type definitions can be used to create new instances or reuse organizational knowledge in case of exceptions (for further reading see[1][2]).
Query language
[edit]In GBAC a query language is used to define agents having certain characteristics or abilities. The following table shows the usage of the query language in the context of an access control matrix.
The first query means that all managers working for the company for more than six months can read the financial report, as well as the managers who are classified by the flag "ReadFinancialReport".
The daily financial report can only be written by the manager of the controlling department or clerks of the department that are enabled to do that (WriteFinancialReport==TRUE).
| Data Object | Read | Write |
|---|---|---|
| Daily Financial Report | Manager(*).(Now() - HiringYear > 0.5) OR Manager.ReadFinancialReport == TRUE | Manager(Controlling) OR Clerk(Controlling).WriteFinancialReport == TRUE |
Implementation
[edit]
GBAC was first implemented in the CoCoS Environment within the organizational server CoCoSOrg.[1] In the C-Org-Project it was extended with more sophisticated features like separation of duty or access control in distributed environments. There is also a cloud-based implementation[5] on IBM's Bluemix[6] platform.
In all implementations the server takes a query from a client system and resolves it to a set of agents. This set is sent back to the calling client as response. Clients can be file systems, database management systems, workflow management systems, physical security systems or even telephone servers.
See also
[edit]- Access control list
- Attribute-based access control (ABAC)
- Capability-based security
- Context-based access control (CBAC)
- Discretionary access control (DAC)
- Lattice-based access control (LBAC)
- Mandatory access control (MAC)
- Organisation-based access control (OrBAC)
- Risk-based authentication
- Role-based access control (RBAC)
- Rule-set-based access control (RSBAC)
References
[edit]- ^ a b c Schaller, Thomas (1998). Organisationsverwaltung in CSCW-Systemen - Dissertation. Bamberg: Bamberg University.
- ^ a b Lawall, Schaller, Reichelt (2014). Enterprise Architecture: A Formalism for Modelling Organizational Structures in Information Systems. Thessaloniki: Enterprise and Organizatinal Modeling and Simulation: 10th International Workshop CAiSE2014.
{{cite book}}: CS1 maint: multiple names: authors list (link) - ^ Lawall, Schaller, Reichelt (2014). "Restricted Relations between Organizations for Cross-Organizational Processes". IEEE 16th Conference on Business Informatics (CBI), Geneva: 74–80.
{{cite journal}}: CS1 maint: multiple names: authors list (link) - ^ Lawall, Schaller, Reichelt (2015). S-BPM in the Wild: Role and Rights Management (1 ed.). Berlin: Springer. pp. 171–186. ISBN 978-3-319-17541-6.
{{cite book}}: CS1 maint: multiple names: authors list (link) - ^ Lawall, Alexander; Reichelt, Dominik; Schaller, Thomas (2015-04-23). "Resource management and authorization for cloud services". Proceedings of the 7th International Conference on Subject-Oriented Business Process Management. S-BPM ONE '15. New York, NY, USA: Association for Computing Machinery: 18:1–18:8. doi:10.1145/2723839.2723864. ISBN 978-1-4503-3312-2.
- ^ Bluemix