Publication | Closed Access
Security through Diversity: Leveraging Virtual Machine Technology
94
Citations
13
References
2009
Year
EngineeringInformation SecurityVirtual Machine TechnologySoftware SystemsSoftware EngineeringSoftware AnalysisBinary AnalysisCode InjectionDefense SystemsVirtualization SecurityVirtualization SupportBiological SystemsComputer ScienceDiverse Biological SystemsData SecurityBiologySoftware SecurityOperating SystemsProgram AnalysisCloud ComputingComputational BiologyUnikernelsVirtualization ToolSystems BiologySystem SoftwareVirtual Machine
Lack of diversity in biological and software systems creates fragility, making networked computing vulnerable to large‑scale attacks. The authors created the Genesis Software Development Toolchain to emulate biological resilience in software development. Genesis employs an application‑level virtual machine that applies diversity transforms at any point in the toolchain. Using Genesis, the authors showed that judiciously applied diversity effectively defends against return‑to‑libc and code injection attacks.
Biologists have long recognized the dangers of the lack of diversity or monocultures in biological systems. Recently, it has been noted that much of the fragility of our networked computing systems can be attributed to the lack of diversity or monoculture of our software systems. The problem is severe. Because it is virtually inevitable that software will ship with flaws, our software monoculture leaves systems open to large-scale attacks by knowledgeable adversaries. Inspired by the resilience of diverse biological systems, the authors developed the Genesis Software Development Toolchain. An innovative aspect of Genesis is the use of an application-level virtual machine technology that enables the application of diversity transforms at any point in the software toolchain. Using Genesis, they authors demonstrated that diversity, when judiciously applied, is a practical and effective defense against two widely used types of attacks—return-to-libc and code injection.
| Year | Citations | |
|---|---|---|
Page 1
Page 1