2002 · 157 citations · 8 references
ComputingComputer ScienceCybersecurityApplication SecurityComputer SecurityVulnerability AnalysisExploit DevelopmentPatch AnalysisPatch ManagementSoftware MaintenanceSoftware Security EngineeringSoftware Vulnerability DiscoveryPatch Impact AssessmentPatch SchedulingPatch-based Vulnerability DiscoverySecure Software PatchingSecurity Patch EvaluationSecurity Patch ManagementSecurity Update ManagementSoftware Updates
Security vulnerabilities are discovered, become publicly known, get exploited by attackers, and patches come out. When should one apply security patches? Patch too soon, and you may suffer from instability induced by bugs in the patches. Patch too late, and you get hacked by attackers exploiting the vulnerability.Weexplore the factors affecting when it is best to apply security patches, providing both mathematical models of the factors affecting when to patch, and collecting empirical data to give the model practical value. Weconclude with a model that we hope will help provide a formal foundation for when the practitioner should apply security updates.
8
On the Elicitation of Preferences for Alternative Therapies
Barbara J. McNeil, Stephen G. Pauker, Harold C. Sox et al. · New England Journal of Medicine · 1982 · 1.7K citations
Why information security is hard - an economic perspective
Ross Anderson · 2005 · 825 citations
SubDomain: Parsimonious Server Security
Crispin Cowan, Steve Beattie, Greg Kroah-Hartman et al. · 2000 · 112 citations