DMCA
SPARE: Replicas on hold (2011)
| Venue: | In Proceedings of the 18th Network and Distributed System Security Symposium |
| Citations: | 7 - 3 self |
BibTeX
@INPROCEEDINGS{Distler11spare:replicas,
author = {Tobias Distler and Ivan Popov and Hans P. Reiser},
title = {SPARE: Replicas on hold},
booktitle = {In Proceedings of the 18th Network and Distributed System Security Symposium},
year = {2011},
pages = {407--420}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Despite numerous improvements in the development and maintenance of software, bugs and security holes exist in to-day’s products, and malicious intrusions happen frequently. While this is a general problem, it explicitly applies to web-based services. However, Byzantine fault-tolerant (BFT) replication and proactive recovery offer a powerful com-bination to tolerate and overcome these kinds of faults, thereby enabling long-term service provision. BFT replica-tion is commonly associated with the overhead of 3f + 1 replicas to handle f faults. Using a trusted component, some previous systems were able to reduce the resource cost to 2f +1 replicas. In general, adding support for proactive recovery further increases the resource demand. We believe this enormous resource demand is one of the key reasons why BFT replication is not commonly applied and consid-ered unsuitable for web-based services. In this paper we present SPARE, a cloud-aware ap-proach that harnesses virtualization to reduce the resource demand of BFT replication and to provide efficient support for proactive recovery. In SPARE, we focus on the main source of software bugs and intrusions; that is, the services and their associated execution environments. This approach enables us to restrict replication and request execution to only f + 1 replicas in the fault-free case while rapidly acti-vating up to f additional replicas by utilizing virtualization in case of timing violations and faults. For an instant reac-tion, we keep spare replicas that are periodically updated in a paused state. In the fault-free case, these passive repli-cas require far less resources than active replicas and aid efficient proactive recovery. 1.
Keyphrases
proactive recovery fault-free case resource demand web-based service bft replication previous system spare replica powerful com-bination additional replica present spare general problem main source to-day product request execution malicious intrusion instant reac-tion byzantine fault-tolerant passive repli-cas require numerous improvement security hole associated execution environment cloud-aware ap-proach bft replica-tion key reason paused state efficient support software bug aid efficient proactive recovery long-term service provision trusted component active replica resource cost enormous resource demand
