A holistic approach to service survivability

Abstract

We present SABER (Survivability Architecture: Block, Evade, React), a proposed survivability architecture that blocks, evades and reacts to a variety of attacks by using several security and survivability mechanisms in an automated and coordinated fashion.Contrary to the ad hoc manner in which contemporary survivable systems are built-using isolated, independent security mechanisms such as firewalls, intrusion detection systems and software sandboxes-SABER integrates several different technologies in an attempt to provide a unified framework for responding to the wide range of attacks malicious insiders and outsiders can launch.This coordinated multi-layer approach will be capable of defending against attacks targeted at various levels of the network stack, such as congestion-based DoS attacks, software-based DoS or code-injection attacks, and others. Our fundamental insight is that while multiple lines of defense are useful, most conventional, uncoordinated approaches fail to exploit the full range of available responses to incidents. By coordinating the response, the ability to survive successful security breaches increases substantially.We discuss the key components of SABER, how they will be integrated together, and how we can leverage on the promising results of the individual components to improve survivability in a variety of coordinated attack scenarios. SABER is currently in the prototyping stages, with several interesting open research topics.

Software Migration Frameworks for Software System Solutions: A Systematic Literature Review

“…It is also involve in the movement of core services program to different platform and freezing where the computation was ceased on the newer platform. For various critical safety systems, migration is known as the heart of the structural design of software [9]. Migration is considered an important strategy for system survivability service.…”

Retrofitting Autonomic Capabilities onto Legacy Systems

“…Effectors must be capable of tuning the target system via its exposed configuration parameters. They may also perform partial replacements by initiating and retiring system components, invoke special utilities such as process migration [20] and, in general, carry out nearly any feasible form of adaptation to individual components and connectors of the running system permitted by that target system. Effectors are necessarily more tightly coupled to the target system than the rest of the reference architecture.…”

“…We are also considering a wider range of application domains. One particularly intriguing application area is autonomic service survivability in the face of insider and outsider security attacks, to coordinate what would otherwise be isolated, independently operating security mechanisms, as we propose in [20].…”

On incremental file system development

“…The VFS objects of each entity (file or directory) are duplicated at the Wrapfs level. On Linux, many file systems have been derived from Wrapfs, including ones for encryption [Corner and Noble 2002;Halcrow 2004;Shanahan 2000], intrusion detection [Keromytis et al 2003], integrity checking , LISA], unification [Klotzbücher 2004;Wright et al 2006], tracing [Aranya et al 2004], versioning , replication [Tzachar 2003], compression Indra Networks 2004], RAID-like functionality [Joukov et al 2005], migration [Schaefer 2000], and more.…”