Extending XACML profile for RBAC with semantic concepts

Helil, Nurmamat; Rahman, Kaysar

doi:10.1109/iccasm.2010.5622888

Cited by 3 publications

(4 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is well-known that XACML is very verbose and can become unreadable with few different polices [19,15]. It also, lacks a formal semantics for policy combination algorithms [4,18].…”

Section: Related Workmentioning

confidence: 98%

“…Helil et. al [15], presented an extension of XACML profile for Role-based Access Control based on the semantic concepts. A OWL-DL reasoner is needed for evaluate the policy and a preliminary evaluation shown a low response time for the evaluation.…”

Section: Related Workmentioning

confidence: 99%

“…One reason for this, could be found in the fact that provenance data are stored in relational databases or RDF stores, with the access control left to the security mechanisms provided by these technologies. Security for database technologies has been extensively studied in the past (see [8] for an overview) and the increasing need for maintaining semantic resources has developed a large set of works focused on security for RDF data [9,10,11,12,13,14,15,16,17,18,19].…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Access control and view generation for provenance graphs

Dánger

Ćurčin

Missier

et al. 2015

Future Generation Computer Systems

View full text Add to dashboard Cite

“…It is well-known that XACML is very verbose and can become unreadable with few different polices [19,15]. It also, lacks a formal semantics for policy combination algorithms [4,18].…”

Section: Related Workmentioning

confidence: 98%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Access control and view generation for provenance graphs

Dánger

Ćurčin

Missier

et al. 2015

Future Generation Computer Systems

View full text Add to dashboard Cite

“…Specific policies for provenance data can be implemented either by using either a dedicated provenance access control language [54,55,56], or an existing standard such as OASIS eXtensible Access Control Markup Language (XACML). Since XACML is not generally suitable for RDF data [57,54,58,59,60], extensions to it are necessary [61,60].…”

Section: Securitymentioning

confidence: 99%

Implementing interoperable provenance in biomedical research

Ćurčin

Miles

Dánger

et al. 2014

Future Generation Computer Systems

View full text Add to dashboard Cite

The provenance of a piece of data refers to knowledge about its origin, in terms of entities and actors involved in its creation, e.g. data sources used, operations carried out on them, and users enacting those operations. Provenance is used to better understand the data and the context of its production, and to assess its reliability, by asserting whether correct procedures were followed. Providing evidence for validating research is of particular importance in the biomedical domain, where the strength of the results depends on the data sources and processes used. In recent times, previously manual processes have become fully or semi-automated, e.g. clinical trial recruitment, epidemiological studies, diagnosis making. The latter is typically achieved through interactions of heterogeneous software systems in multiple settings (hospitals, clinics, academic and industrial research organisations). Provenance traces of these software need to be integrated in a consistent and meaningful manner, but since these software systems rarely share a common platform, the provenance interoperability between them has to be achieved on the level of conceptual models. It is a non-trivial matter to determine where to start in making a biomedical software system provenance-aware. In this paper, we specify recommendations to developers on how to approach provenance modelling, capture, security, storage and querying, based on our expe- * riences with two large-scale biomedical research projects: Translational Research and Patient Safety in Europe (TRANSFoRm) and Electronic Health Records for Clinical Research (EHR4CR). While illustrated with concrete issues encountered, the recommendations are sufficiently high level so as to be reusable across the biomedical domain.

show abstract