37th International Symposium on Microarchitecture (MICRO-37'04)
DOI: 10.1109/micro.2004.31
|View full text |Cite
|
Sign up to set email alerts
|

RIFLE: An Architectural Framework for User-Centric Information-Flow Security

Abstract: Even as modern computing systems allow the manipulation and distribution of massive amounts of information

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
125
0

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 187 publications
(125 citation statements)
references
References 34 publications
0
125
0
Order By: Relevance
“…However, prior methods of detecting noninterference have typically required access to the program running the system in question. These analyses either used the program for directly analyzing its code (see [9] for a survey), for running an instrumented version of the system (e.g., [10][11][12][13]), or for simulating multiple executions of the system (e.g., [14][15][16]). Traditionally, the requirement of access to the program has not been problematic since the analysis has been motivated as a tool for software engineers securing a program that they have designed.…”
Section: Prior Workmentioning
confidence: 99%
“…However, prior methods of detecting noninterference have typically required access to the program running the system in question. These analyses either used the program for directly analyzing its code (see [9] for a survey), for running an instrumented version of the system (e.g., [10][11][12][13]), or for simulating multiple executions of the system (e.g., [14][15][16]). Traditionally, the requirement of access to the program has not been problematic since the analysis has been motivated as a tool for software engineers securing a program that they have designed.…”
Section: Prior Workmentioning
confidence: 99%
“…This explains why we prefer to speak of data flow rather than information flow. Moreover, even if we plan to leverage results of static analyses, like [39], we want to detect these flows at runtime. Implementations of such data-flow tracking system have been realized for the operating system [3], X11 [4], OpenOffice [5] and Java byte code and can be used as PIP component to instantiate our model.…”
Section: Related Workmentioning
confidence: 99%
“…For instance, the whole system emulator QEMU [3] is employed by various solutions that implement DTA [13,20,27], while TaintBochs [7] builds on the Bochs IA-32 emulator. The architecture community attempted to integrate or assist dynamic taint tracking with hardware extensions [9,10,23,24], to alleviate the significant performance impact due to extra tag processing from DBI frameworks and emulators.…”
Section: Cross-process and Cross-host Taint Trackingmentioning
confidence: 99%
“…For example, many security-oriented DTA implementations [19] do not support configurable taint sources, and mark all incoming network as tainted -We improved on inter-process taint tracking over previous system-wide tracking systems (e.g. Minos [9], TaintBochs [7], Rakscha [10], RIFLE [24]), which are based on slow full-system emulators (e.g. Xen [2], QEMU [3], Bochs [4]), by enabling cross-host and cross-process tracking on the communication channels that matter to the target applications, rather than overloading every operation in the entire system with unnecessary heavyweight taint tracking operations -We evaluate the overhead imposed by Taint-Exchange, and show that it incurs minimal overhead over the baseline tool libdft…”
Section: Introductionmentioning
confidence: 99%