2009
DOI: 10.1007/978-3-642-01187-0_5
|View full text |Cite
|
Sign up to set email alerts
|

A Non-technical User-Oriented Display Notation for XACML Conditions

Abstract: Abstract. Ideally, access control to resources in complex IT systems ought to be handled by business decision makers who own a given resource (e.g., the pay and benefits section of an organization should decide and manage the access rules to the payroll system). To make this happen, the security and database communities need to develop vendor-independent access management tools, useable by decision makers, rather than technical personnel detached from a given business function. We have developed and implemente… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
10
0

Year Published

2010
2010
2016
2016

Publication Types

Select...
4
4
2

Relationship

2
8

Authors

Journals

citations
Cited by 19 publications
(11 citation statements)
references
References 1 publication
1
10
0
Order By: Relevance
“…We found that the XACML-based policy mechanism built into CDAShip was readily capable of expressing all these scenarios, but their native XACML representation was virtually incomprehensible for persons without formal training in computer science. We agree with Stepien et al that further abstractions are necessary to allow more useroriented authoring of consent policies (Stepien et al 2009). …”
Section: Practical Case Studysupporting
confidence: 57%
“…We found that the XACML-based policy mechanism built into CDAShip was readily capable of expressing all these scenarios, but their native XACML representation was virtually incomprehensible for persons without formal training in computer science. We agree with Stepien et al that further abstractions are necessary to allow more useroriented authoring of consent policies (Stepien et al 2009). …”
Section: Practical Case Studysupporting
confidence: 57%
“…With regard to our own past work, as mentioned, this work extends our work on conflict detection for firewalls [2]. We have also been involved in work on a tool for administering XACML policies, with a focus on usability for policy administrators that do not necessarily have a technical background [9,10]. An implementation of conflict detection (unverified) was also part of that work.…”
Section: Resultsmentioning
confidence: 89%
“…In more dynamic scenarios, however, the generation of the PDP may add a constant time to policy evaluation. Finally, the use of a non-XML syntax for XACML is not new; e.g., a syntax similar to that of FACPL is proposed in [15], while a 'display' notation that combines a graphical interface with a natural language like format is introduced in [17]. But, again, such approaches do not rely on a formal semantics.…”
Section: Related Workmentioning
confidence: 99%