Abstract Context: Infrastructure as code (IaC) is the practice to automatically configure
system dependencies and to provision local and remote instances. Practitioners consider …

Adversaries are often able to penetrate networks and compromise systems by exploiting
vulnerabilities in people and systems. The key to the success of these attacks is information …

Large-scale cloud services deploy hundreds of configuration changes to production systems
daily. At such velocity, configuration changes have inevitably become prevalent causes of …

A large percentage of real-world software configuration issues, such as misconfigurations,
involve multiple interdependent configuration parameters. However, existing techniques and …

Many techniques were proposed for detecting software misconfigurations in cloud systems
and for diagnosing unintended behavior caused by such misconfigurations. Detection and …

Configuration changes are among the dominant causes of failures of large-scale software
system deployment. Given the velocity of configuration changes, typically at the scale of …

Misconfigurations are the major causes of software failures. Existing configuration validation
techniques rely on manually written rules or test cases, which are expensive to implement …

Today's software failures have two dominating root causes: code bugs and
misconfigurations. To combat failure-inducing software changes, unified regression testing …

Continuous Integration (CI) allows developers to check whether their code can build
successfully and pass tests across various system environments with every commit. To use a …

Configuration error injection testing (CEIT) could systematically evaluate software reliability
and diagnosability to runtime configuration errors. This paper explores the challenges and …