REASSURE: A Self-contained Mechanism for Healing Software Using Rescue Points

Portokalidis, Georgios; Keromytis, Angelos D.

doi:10.1007/978-3-642-25141-2_2

Cited by 19 publications

(17 citation statements)

References 22 publications

(19 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Despite some previous work having addressed the problem of repairing applications at runtime by changing them dynamically [19][20] [21], none of them is generic, provides full recovery of applications and guarantees application correctness after recovery. By contrast, reboot-based techniques have shown a singular ability for overcoming transient failures.…”

Section: Problem Statementmentioning

confidence: 99%

Reboot-based recovery of performance anomalies in adaptive bitrate video-streaming services

Cunha

Silva

2017

IJHPCN

View full text Add to dashboard Cite

Abstract-Performance anomalies represent one common type of failures in Internet servers. Overcoming these failures without introducing server downtimes is of the utmost importance in video-streaming services. These services have large user abandonment costs when failures occur after users watch a significant part of a video. Reboot is the most popular and effective technique for overcoming performance anomalies but it takes several minutes from start until the server is warmed-up again to run at its full capacity. During that period, the server is unavailable or provides limited capacity to process end-users' requests. This paper presents a recovery technique for performance anomalies in HTTP Streaming services, which relies on Container-based Virtualization to implement an efficient multi-phase server reboot technique that minimizes the service downtime. The recovery process includes analysis of variance of request-response times to delimit the server warm-up period, after which the server is running at its full capacity. Experimental results show that the Virtual Container recovery process completes in 72 seconds, which contrasts with the 434 seconds required for full operating system recovery. Both recovery types generate service downtimes imperceptible to end-users.

show abstract

Section: Problem Statementmentioning

confidence: 99%

Reboot-based recovery of performance anomalies in adaptive bitrate video-streaming services

Cunha

Silva

2017

IJHPCN

View full text Add to dashboard Cite

show abstract

“…Self-healing (or self-fixing, self-repairing) software such as the Network Worm Vaccine Architecture [27,43,60], ClearView [41], and SHADOWS [59], aims to fix itself when something monitored goes wrong. However, runtime protection or monitoring mechanisms are often too expensive in practice to be applied in large scale.…”

Section: Self-healing Softwarementioning

confidence: 99%

Software Cruising: A New Technology for Building Concurrent Software Monitor

Liu

Zeng

et al. 2013

Secure Cloud Computing

View full text Add to dashboard Cite

We introduce a novel concurrent software monitoring technology, called software cruising. It leverages multicore architectures and utilizes lock-free data structures and algorithms to achieve efficient and scalable security monitoring. Applications include, but are not limited to, heap buffer integrity checking, kernel memory cruising, data structure and object invariant checking, rootkit detection, and information provenance and flow checking. In the software cruising framework, one or more dedicated threads, called cruising threads, are running concurrently with the monitored user or kernel code, to constantly check, or cruise, for security violations. We believe the software cruising technology would result in a game-changing capability in security monitoring for the cloud-based and traditional computing and network systems.We have developed two prototypical cruising systems: Cruiser, a lock-free concurrent heap buffer overflow monitor in user space, and Kruiser, a semisynchronized non-blocking OS kernel cruiser. Our experimental results showed that software cruising can be deployed in practice with modest overhead. In user space, heap buffer overflow cruising incurs only 5 % performance overhead on average for the SPEC CPU2006 benchmark, and the Apache throughput slowdown is only 3 % maximum and negligible on average. In kernel space, it is negligible for SPEC, and 3.8 % for Apache. Both technologies can be deployed in large scale for cloud data centers and server farms in an automated manner.

show abstract

“…The protection mechanisms that CSSH will enable include REASSURE [3], Write-Read Integrity Testing (WRIT), stack/heap buffer overflow protection, number handling vulnerability masking (divide-by-zero, integer overflow/underflow, etc. ), NULL pointer protection, Control Flow Integrity (CFI) [8], and limited race condition detection/avoidance.…”

Section: B Cssh: Collaborative Self-healing and Service Hardeningmentioning

confidence: 99%

“…Both components can be targeted to specific applications (or even portions of an application), and can share information to coordinate cloud-wide protection. The DMCC provides anomaly detection capabilities (both for use with CSSH, and as a fallback detector); it also gathers information that can be used to improved the functionality of other mechanisms (especially CSSH and CSIFT), e.g., identification of rescue points for use in self-healing [3]. MiSS and DREME provide code migration and containment capabilities, and Evade provides data migration capabilitiesall these are meant to be used both proactively (as a "moving target" defense) and reactively (in response to a detected compromise).…”

Section: Introductionmentioning

confidence: 99%

The MEERKATS Cloud Security Architecture

Keromytis

Geambasu

Sethumadhavan

et al. 2012

2012 32nd International Conference on Distributed Computing Systems Workshops

Self Cite

View full text Add to dashboard Cite

Abstract-MEERKATS is a novel architecture for cloud environments that elevates continuous system evolution and change as first-rate design principles. Our goal is to enable an environment for cloud services that constantly changes along several dimensions, toward creating an unpredictable target for an adversary. This unpredictability will both impede the adversary's ability to achieve an initial system compromise and, if a compromise occurs, to detect, disrupt, and/or otherwise impede his ability to exploit this success. Thus, we envision an environment where cloud services and data are constantly in flux, using adaptive (both proactive and reactive) protection mechanisms and distributed monitoring at various levels of abstraction. A key element of MEERKATS is the focus on both the software and the data in the cloud, not just protecting but leveraging both to improve mission resilience. MEERKATS seeks to effectively exploit "economies of scale" (in resources available) to provide higher flexibility and effectiveness in the deployment and use of protection mechanisms as and where needed, focusing on current and anticipated application and mission needs instead of an inefficient, "blanket" approach to protecting "everything the same way, all the time". We outline our vision for MEERKATS and describe our approach toward prototyping it.

show abstract

REASSURE: A Self-contained Mechanism for Healing Software Using Rescue Points

Cited by 19 publications

References 22 publications

Reboot-based recovery of performance anomalies in adaptive bitrate video-streaming services

Reboot-based recovery of performance anomalies in adaptive bitrate video-streaming services

Software Cruising: A New Technology for Building Concurrent Software Monitor

The MEERKATS Cloud Security Architecture

Contact Info

Product

Resources

About