Abstract
Most computer defense systems crash the process that they protect as part of their response to an attack. Although recent research explores the feasibility of self-healing to automatically recover from an attack, self-healing faces some obstacles before it can protect legacy applications and COTS (Commercial Off-The-Shelf) software. Besides the practical issue of not modifying source code, self-healing must know both when to engage and how to guide a repair. Previous work on a self-healing system, STEM, left these challenges as future work. This paper improves STEM-s capabilities along three lines to provide practical speculative execution for automated defense (SEAD). First, STEM is now applicable to COTS software: it does not require source code, and it imposes a roughly 73% performance penalty on Apache-s normal operation. Second, we introduce repair policy to assist the healing process and improve the semantic correctness of the repair. Finally, STEM can create behavior profiles based on aspects of data and control flow.
| Original language | English |
|---|---|
| Pages | 219-232 |
| Number of pages | 14 |
| State | Published - 2007 |
| Event | 2007 USENIX Annual Technical Conference, USENIX ATC 2007 - Santa Clara, United States Duration: 17 Jun 2007 → 22 Jun 2007 |
Conference
| Conference | 2007 USENIX Annual Technical Conference, USENIX ATC 2007 |
|---|---|
| Country/Territory | United States |
| City | Santa Clara |
| Period | 17/06/07 → 22/06/07 |
Fingerprint
Dive into the research topics of 'From STEM to SEAD: Speculative Execution for Automated Defense'. Together they form a unique fingerprint.Cite this
- APA
- Author
- BIBTEX
- Harvard
- Standard
- RIS
- Vancouver