N-Variant Systems: A Secretless Framework for Security through Diversity
By Benjamin Cox, David E. Evans. USENIX Security Symposium, 2006
383 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/ca185be3b1d835e02701e58e525f1a3ae5f2bc5f
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Claire Le Goues
- Stephanie Forrest
- Westley Weimer
- Thanhvu Nguyen
- Fan Long
- Ahmed Khurshid
- Matthew C. Caesar
- Taesoo Kim
Citations in the corpus
- GenProg: A Generic Method for Automatic Software Repair (2012, methodology): “Techniques for automatically detecting software flaws include intrusion detection [8], model checking and lightweight static analyses [9], [10], and software diversity methods [11], [12].”
- Binary stirring: self-randomizing instruction addresses of legacy x86 binary code (2012, methodology): “Multi-variant Systems: Our work is also related to N-variant systems [11, 22, 47], which likewise leverage diversification to improve security.”
- Debugging the data plane with anteater (2011, background): “Monitoring the dynamics of the control plane can detect a broad class of failures [16, 20] with little overhead, but may miss bugs that only affect the data plane.”
- PlatPal: Detecting Malicious Documents with Platform Diversity (2017, methodology): “[10] randomize sensitive data in program variants to mitigate privacy leaks; Mx [24] uses multiple versions of the same program to survive update bugs; Cocktail [66] uses multiple web browser implementations to survive vendor-specific attacks; and Nvariant [15], Replicae [8], and GHUMVEE [61] run pr”