Graph-based access control: Difference between revisions

Revision as of 09:52, 3 July 2015

Revision as of 17:30, 3 July 2015

Line 2:

<!-- EDIT BELOW THIS LINE -->

'''Work in process'''

Graph-based access control is a rather new technique for granting users of information systems access rights to data objects like files or documents. It can also be used for the assignment of tasks in workflow environments. Organizations are modeled as a specific kind of semantic graph comprising the organizational structure, the roles and functions as well as the agents. Compared to other approaches like RBAC or ABAC the main difference is that in GBAC access rights are defined using an organization query language instead of total enumeration.

Looking at the various applications and systems needed for running a business one thing gets obvious: in almost every application there is the need to maintain a model of the organization structure, of the roles and the actors in order to define access rights or assign tasks to employees (in case of a workflow management system). These redundancies lead to a great maintenance overhead that – even for small businesses – can grow to a great burden. This problem can be avoided by deploying one logically central component offering this service to other applications. This component is called an organization server.

== History ==

== Graph-based Access Control ==

The idea of representing an organization as a semantic graph was first presented by Thomas Schaller in [<ref>{{cite book|last1=Schaller|first1=Thomas|title=Organisationsverwaltung in CSCW-Systemen|date=1998|publisher=Bamberg University|___location=Bamberg}}</ref>] (in English language please see <ref>{{cite book|last1=Lawall, Schaller, Reichelt|title=Enterprise Architecture: A Formalism for Modelling Organizational Structures in Information Systems|date=2014|publisher=Enterprise and Organizatinal Modeling and Simulation: 10th International Workshop CAiSE2014|___location=Thessaloniki}}</ref>) where the organization graph and a formal language was used to specify agents in a workflow environment.

After that approach was extended with features like ...

HGAC

== Definition ==

asdf

== Relation to other Techniques ==

=== Heading 2 ===

== See also ==

== References ==

<ref>{{cite book|last1=Schaller|first1=Thomas|title=Organisationsverwaltung in CSCW-Systemen|date=1998|publisher=Bamberg University|___location=Bamberg}}</ref>