A declarative approach to hardening services against QoS vulnerabilities

Young Woo Kwon, Eli Tilevich

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

2 Scopus citations

Abstract

The Quality of Service (QoS) in a distributed service-oriented application can be negatively affected by a variety of factors. Network volatility, hostile exploits, poor service management, all can prevent a service-oriented application from delivering its functionality to the user. This paper puts forward a novel approach to improving the reliability, security, and availability of service-oriented applications. To counter service vulnerabilities, a special service detects vulnerabilities as they emerge at runtime, and then hardens the applications by dynamically deploying special components. The novelty of our approach lies in using a declarative framework to express both vulnerabilities and hardening strategies in a domain-specific language, independent of the service infrastructure in place. Thus, our approach will make it possible to harden service-oriented applications in a disciplined and systematic fashion.

Original languageEnglish
Title of host publication2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems, MESOCA 2011
DOIs
StatePublished - 2011
Event2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems, MESOCA 2011 - Williamsburg, VA, United States
Duration: 26 Sep 201126 Sep 2011

Publication series

Name2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems, MESOCA 2011

Conference

Conference2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems, MESOCA 2011
Country/TerritoryUnited States
CityWilliamsburg, VA
Period26/09/1126/09/11

Fingerprint

Dive into the research topics of 'A declarative approach to hardening services against QoS vulnerabilities'. Together they form a unique fingerprint.

Cite this