BB24.I Semantic Attribute Based Access Control (S-ABAC)
From its-wiki.no
| Title | Semantic Attribute Based Access Control (S-ABAC) |
|---|---|
| Page Title | BB24.I Semantic Attribute Based Access Control (S-ABAC) |
| Technology Line | Distributed Cloud Integration |
| Lead partner | UiO |
| Leader | Christian Johansen |
| Contributors | UiO, Wolffia, SmartIO |
| Related to Use Cases | SCOTT:WP8, SCOTT:WP11, SCOTT:WP12, SCOTT:WP13, SCOTT:WP14, SCOTT:WP15, SCOTT:WP21 |
| Description | A Semantic Attribute based access control provides the means for different actors having access to different types of information of a system. The former notation of Role-based access control (RBAC) is extended, where "role" is one attribute deciding on the access. As an example, your data of your "heat pump" (energy efficiency) are of interest for a) the house owner, b) the manufacturer, c) the municipalities, d) the maintenance company, e) the person renting the flat, f) the energy distributor. Which data (e.g. statistical) and who has access (attribute: grade of access: monitor, control, configure) might be subject to a security and privacy analysis (attribute: required security level). S-ABAC is seen as tool to provide the functionality, but needs R&I to become usable in a distributed cloud. |
| Main output | One output would be Ontologies related to Access Control for the specific domains that SCOTT works with.
Another output is a methodology and technology description for how to include semantic specifications, i.e., the above mentioned ontologies, in the ABAC model. A third outcome would be a software implementation of a S-ABAC engine that would extend existing ABAC engine/framework with semantic reasoning tools and ontology editing capabilities. These software components would form the S-ABAC-framework and would include components like policy definition endpoint and tool including Semantic concepts, policy enforcement point, Attribute management point, etc. |
| BB category | Methodology (for SW/HW development), SW component, Profile, Tool or tool chain, Interface, Standard, Means for establishing cross-domain interoperability, Other |
| Baseline | Attribute Based Access Control (ABAC) starts to penetrate the industry, and has been used especially in the health domain where fine grained access policies are needed. Industrial standards already exist, e.g., XACML and SAML, and industry standard implementations of ABAC also exist, e.g., Balana ...
We plan to include in ABAC notions from Semantic Technologies, e.g. ontologies for the specific domains that SCOTT works on, and reasoning engines like Protege. Semantic technologies are widely used in industries for and specific domains, with the purpose to provide amore structures way of managing and querying data. We want to use the powerful tools of ST in conjunction with ABAC models, to improve the flexibility of ABAC and ease the adoption by industry. |
| Current TRL | 9 for Semantic Technologies 9 for ABAC |
| Target TRL | Aim to reach TRL 6 for S-ABAC . |
Contents
Activities
- Title= A language-based policy specification and enforcement in a semantic-directed, integrated and automated approach.
- status= Progress
- author= Toktam Ramezani
- Title= attribute-based encryption (from Chalmers via WP21 SharePoint)
- status= Initiation
- author= Christian Johansen