Addressing the monoculture

@article{Goth2003AddressingTM,
  title={Addressing the monoculture},
  author={G. Goth},
  journal={IEEE Security \& Privacy Magazine},
  year={2003},
  volume={99},
  pages={8-10}
}
  • G. Goth
  • Published 2003
  • Computer Science
  • IEEE Security & Privacy Magazine
8 PUBLISHED BY THE IEEE COMPUTER SOCIETY 1540-7993/03/$17.00 © 2003 IEEE IEEE SECURITY & PRIVACY A new term has bubbled out of the specialized arena of academic nomenclature and into the mainstream, from daily newspaper columns to transcripts of Congressional hearings. That term is “monoculture.” According to some of the leading computer-security experts in the US, the dominance of Microsoft’s Windows operating system has created an unsafe monoculture, in which critical networks and… Expand
Software Self-Healing Using Collaborative Application Communities
TLDR
The concept of Application Communities is introduced and it is shown that ACs are practical and feasible for current applications: an AC of 15,000 members can collaboratively monitor Apache for new faults and immunize all members against them with only a 6% performance degradation for each member. Expand
Towards a Theory of Software Diversity for Security
TLDR
This thesis provides a framework for investigating software diversity in the context of security by proposing a simple model of a software ecosystem using sets of hosts and vulnerabilities represented as a bipartite graph and exhibiting a few examples of software security problems formulated precisely enough in this model to admit rigorous analysis. Expand
Security through network-wide diversity assignment
The best efforts of the computer security community have not eliminated software with hidden attackable vulnerabilities in the world. Code analyzers and hardened operating environments have reducedExpand
A Survey of Randomization Techniques Against Common Mode Attacks
Software systems often share common vulnerabilities that allow a single attack to compromise large numbers of machines (“write once, exploit everywhere”). Borrowing from biology, several researchersExpand
Application communities: using monoculture for dependability
TLDR
A set of parameters that define an Application Communities (AC) are proposed and the tradeoffs between the minimal size of an AC, the marginal overhead imposed on each member, and the speed with which new faults are detected are explored. Expand
Cyberdiversity: Measures and Initial Results
TLDR
A novel approach is introduced that measures the existing diversity in software by collecting specific information and then process it in order to find distinct similarities or differences within software. Expand
Software diversity as a defense against viral propagation: models and simulations
TLDR
It is shown that one can increase the epidemic threshold of a network even with a naive, random distribution of diverse software on the nodes of anetwork, and the value of strategic topology-sensitive assignment of diversity to improving the tolerance of a networks to malcode propagation is confirmed. Expand
Integrity postures for software self-defense
Software currently lacks the capability to respond intelligently and automatically to attacks in a way that preserves both its availability and its integrity. This problem is exacerbated by theExpand
Software self-healing using error virtualization
TLDR
This dissertation introduces and evaluates a set of techniques for recovering program execution in the presence of faults by effectively retrofitting legacy applications with exception handling techniques, Error Virtualization and ASSURE, and describes two deployment mechanisms that can reduce the cost of monitoring the application and, in turn, enable efficient deployment strategies for error virtualization systems. Expand
On the Evolution of Malware Species
TLDR
The departure of the democratic virus writing model in which even moderate programmers managed to create successful virus strains to an entirely aristocratic ecosystem of highly evolved malcode is demonstrated. Expand
...
1
2
...