2014
DOI: 10.1007/978-3-319-04897-0_3
|View full text |Cite
|
Sign up to set email alerts
|

Idea: Towards a Vision of Engineering Controlled Interaction Execution for Information Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2015
2015
2015
2015

Publication Types

Select...
1

Relationship

1
0

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 19 publications
0
2
0
Order By: Relevance
“…Elaborating seminal proposals for inference control in information systems, and being in the spirit of many similar approaches to secrecy as concisely exposed in [14], previous work on Controlled Interaction Execution, CIE, originally only dealt with a single owner of a logic-oriented database system like a relational one solely employed for querying, and later also included updates and non-monotonic belief management, see the summaries [4,5], and the abstraction [6]. Based on that, and grossly summarized, in our vision [7] we proposed an architecture of an inference control front-end for uniformly shielding a possibly heterogeneous collection of data sources.…”
Section: Introductionmentioning
confidence: 93%
See 1 more Smart Citation
“…Elaborating seminal proposals for inference control in information systems, and being in the spirit of many similar approaches to secrecy as concisely exposed in [14], previous work on Controlled Interaction Execution, CIE, originally only dealt with a single owner of a logic-oriented database system like a relational one solely employed for querying, and later also included updates and non-monotonic belief management, see the summaries [4,5], and the abstraction [6]. Based on that, and grossly summarized, in our vision [7] we proposed an architecture of an inference control front-end for uniformly shielding a possibly heterogeneous collection of data sources.…”
Section: Introductionmentioning
confidence: 93%
“…We also could distinguish whether a confidentiality requirement should refer to either the initial status of a potential secret or its current status or its full status history or, in some extension, even to any selection of points in time of its history. The meaning of phrases like "kept secret to", "not knowing", or "being sure" applied to an intelligent attacker strongly depends on its background, in particular its a priori knowledge about the integrated belief, its awareness about details of the controlled interaction system, and its reasoning methods [7]. However, in general the (defending) owner can only form reasonable assumptions about the (attacking) partner's background.…”
Section: Inference Controlmentioning
confidence: 99%