article · 2012

Delegation Revocation

Cited by 0Abstract and details only

Abstract

Context: Role-based access control (RBAC) has become the de facto standard for access management in zation constraints have been proposed in the literature [1–5]. In contrast to common static SoD constraints (e.g., no user can be as-signed to the roles cashier and cashier supervisor by an adminis-trator), dynamic authorization constraints are more flexible and hence are needed in many organizations. A typical example of dy-namic SoD is the rule ‘‘A check must not be prepared, verified and signed by the same clerk’’. In this case, the access decision for sign-ing the check depends on the actions that have been previously role to another colleague to process the confirmation request. In a healthcare environment, physicians often need to consult a spe-cialist, and hence, need to pass on patient data. In such a situation, the attending physician needs to delegate read access for the patient data to the specialist. Sometimes delegations should be re-voked, e.g., on returning from vacation, a supervisor revokes priv-ileges from her colleague who was member of the delegated role. ⇑ Corresponding author. 1 In the access control literature, this constraint is often referred to as ‘‘object-based dynamic SoD’’. Due to the fact that the term ‘‘object’ ’ has another meaning in the context of UML, we use ‘‘resource’ ’ instead.

Cite this paper

APA 7

(2012). Delegation Revocation.

MLA 9

“Delegation Revocation.” 2012.

Chicago

2012. “Delegation Revocation.”

Harvard

(2012) ‘Delegation Revocation’.

BibTeX

@article{anon2012delegation,
  title = {{Delegation Revocation}},
  year = {2012}
}

Made from the index record. Check names, capitalisation and page numbers against the paper. Need another style? AI for Research has over 10,000.