2012
DOI: 10.1007/978-3-642-28879-1_9
|View full text |Cite
|
Sign up to set email alerts
|

Representation-Independent Data Usage Control

Abstract: Abstract. Usage control is concerned with what happens to data after access has been granted. In the literature, usage control models have been defined on the grounds of events that, somehow, are related to data. In order to better cater to the dimension of data, we extend a usage control model by the explicit distinction between data and representation of data. A data flow model is used to track the flow of data in-between different representations. The usage control model is then extended so that usage contr… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
49
0

Year Published

2014
2014
2016
2016

Publication Types

Select...
5
1

Relationship

2
4

Authors

Journals

citations
Cited by 26 publications
(49 citation statements)
references
References 35 publications
(108 reference statements)
0
49
0
Order By: Relevance
“…Together, step 4 and 5 are called policy instantiation and they might be switched in order, depending upon the context detail to be added and the corresponding system implementation. Generic Architecture: We build upon an existing generic usage control infrastructure with three main components: a Policy Enforcement Point (PEP), able to observe, intercept, possibly modify and generate events in the system; a Policy Decision Point (PDP), representing the core of the usage control monitoring logic; and a Policy Information Point (PIP), which provides the data-container mapping to the PDP [5]. This infrastructure was extended with a Policy Management Point (PMP) with a dedicated sub-component, the Policy Translation Point (PTP) for policy derivation using action refinement.…”
Section: The Generic Approach To Policy Derivationmentioning
confidence: 99%
See 3 more Smart Citations
“…Together, step 4 and 5 are called policy instantiation and they might be switched in order, depending upon the context detail to be added and the corresponding system implementation. Generic Architecture: We build upon an existing generic usage control infrastructure with three main components: a Policy Enforcement Point (PEP), able to observe, intercept, possibly modify and generate events in the system; a Policy Decision Point (PDP), representing the core of the usage control monitoring logic; and a Policy Information Point (PIP), which provides the data-container mapping to the PDP [5]. This infrastructure was extended with a Policy Management Point (PMP) with a dedicated sub-component, the Policy Translation Point (PTP) for policy derivation using action refinement.…”
Section: The Generic Approach To Policy Derivationmentioning
confidence: 99%
“…In usage control, several enforcements exist at and across different layers of abstraction in various types of systems [2,3,5,[16][17][18]. In all these implementations, the focus has been on the implementation of event monitors; policy derivation has not been addressed.…”
Section: Related Work and Relevancementioning
confidence: 99%
See 2 more Smart Citations
“…Our solution works as follows: Data usage control technology [7,12,18,19] is integrated into the Software Execution Environment (SEE) (e.g., Java Runtime Environment (RTE), .NET CLR, PHP interpreter) which is then supposed to be provided in a Platform-as-a-Service (PaaS) manner by trustworthy entities. Such trustworthy entities might include the OSN operator herself, public universities, or consumer protection organizations (cf.…”
mentioning
confidence: 99%