Familiarity breeds contempt
Authors:
Open Access
- 6 December 2010
- conference paper
- Published by Association for Computing Machinery (ACM)
- p. 251-260
Abstract
Work on security vulnerabilities in software has primarily focused on three points in the software life-cycle: (1) finding and removing software defects, (2) patching or hardening software after vulnerabilities have been discovered, and (3) measuring the rate of vulnerability exploitation. This paper examines an earlier period in the software vulnerability life-cycle, starting from the release date of a version through to the disclosure of the fourth vulnerability, with a particular focus on the time from release until the very first disclosed vulnerability. Analysis of software vulnerability data, including up to a decade of data for several versions of the most popular operating systems, server applications and user applications (both open and closed source), shows that properties extrinsic to the software play a much greater role in the rate of vulnerability discovery than do intrinsic properties such as software quality. This leads us to the observation that (at least in the first phase of a product's existence), software vulnerabilities have different properties from software defects. We show that the length of the period after the release of a software product (or version) and before the discovery of the first vulnerability (the 'Honeymoon' period) is primarily a function of familiarity with the system. In addition, we demonstrate that legacy code resulting from code re-use is a major contributor to both the rate of vulnerability discovery and the numbers of vulnerabilities found; this has significant implications for software engineering principles and practice.Keywords
Funding Information
- Office of Naval Research (N00014-07-1-907N00014-09-1-0770)
- Division of Computer and Network Systems (CCD-0810947CNS-0905434)
- National Science Foundation (CCD-0810947CNS-0905434)
This publication has 11 references indexed in Scilit:
- A few billion lines of code laterCommunications of the ACM, 2010
- Post-release reliability growth in software productsACM Transactions on Software Engineering and Methodology, 2008
- Improving vulnerability discovery models2007
- Modeling the Vulnerability Discovery Process2006
- An empirical study of operating systems errors2001
- Windows of vulnerability: a case study analysisComputer, 2000
- A quantitative model of the security intrusion process based on attacker behaviorIEEE Transactions on Software Engineering, 1997
- Theory of Program Testing-An OverviewBell System Technical Journal, 1983
- Time-Dependent Error-Detection Rate Model for Software Reliability and Other Performance MeasuresIEEE Transactions on Reliability, 1979
- A theory of software reliability and its applicationIEEE Transactions on Software Engineering, 1975