Risk-Based Attack Surface Approximation: How Much Data Is Enough?
暂无分享,去创建一个
Laurie A. Williams | Christopher Theisen | Brendan Murphy | Kim Herzig | L. Williams | Brendan Murphy | Kim Herzig | Christopher Theisen
[1] Mohammad Zulkernine,et al. Using complexity, coupling, and cohesion metrics as early indicators of vulnerabilities , 2011, J. Syst. Archit..
[2] Jeannette M. Wing,et al. An Attack Surface Metric , 2011, IEEE Transactions on Software Engineering.
[3] Shih-Kun Huang,et al. Software Crash Analysis for Automatic Exploit Generation on Binary Programs , 2014, IEEE Transactions on Reliability.
[4] Dongmei Zhang,et al. ReBucket: A method for clustering duplicate crash reports based on call stack similarity , 2012, 2012 34th International Conference on Software Engineering (ICSE).
[5] Alessandro Orso,et al. F3: fault localization for field failures , 2013, ISSTA.
[6] Bin Wang,et al. Automated support for classifying software failure reports , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..
[7] Nachiappan Nagappan,et al. Crash graphs: An aggregated view of multiple crashes to improve crash triage , 2011, 2011 IEEE/IFIP 41st International Conference on Dependable Systems & Networks (DSN).
[8] Sooyong Park,et al. Which Crashes Should I Fix First?: Predicting Top Crashes at an Early Stage to Prioritize Debugging Efforts , 2011, IEEE Transactions on Software Engineering.
[9] Andreas Zeller,et al. Fuzzing with Code Fragments , 2012, USENIX Security Symposium.
[10] Nitesh V. Chawla,et al. SMOTE: Synthetic Minority Over-sampling Technique , 2002, J. Artif. Intell. Res..
[11] Brendan Murphy,et al. Can developer-module networks predict failures? , 2008, SIGSOFT '08/FSE-16.
[12] Laurie A. Williams,et al. Evaluating Complexity, Code Churn, and Developer Activity Metrics as Indicators of Software Vulnerabilities , 2011, IEEE Transactions on Software Engineering.
[13] Michael Gegick,et al. Prioritizing software security fortification throughcode-level metrics , 2008, QoP '08.
[14] Witold Pedrycz,et al. A comparative analysis of the efficiency of change metrics and static code attributes for defect prediction , 2008, 2008 ACM/IEEE 30th International Conference on Software Engineering.
[15] Yonghee Shin,et al. Can fault prediction models and metrics be used for vulnerability prediction , 2010 .
[16] Andreas Zeller,et al. Predicting vulnerable software components , 2007, CCS '07.
[17] Indrajit Ray,et al. Using Attack Surface Entry Points and Reachability Analysis to Assess the Risk of Software Vulnerability Exploitability , 2014, 2014 IEEE 15th International Symposium on High-Assurance Systems Engineering.
[18] Laurie A. Williams,et al. Secure open source collaboration: an empirical study of linus' law , 2009, CCS.
[19] Rongxin Wu,et al. CrashLocator: locating crashing faults based on crash stacks , 2014, ISSTA 2014.
[20] N. Nagappan,et al. Use of relative code churn measures to predict system defect density , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..
[21] Acm Sigsoft. SIGSOFT 2004/FSE-12 : twelfth ACM SIGSOFT International Symposium on the Foundations of Software Engineering, October 31--November 5, 2004, Newport Beach, California, USA , 2004 .
[22] Miles McQueen,et al. Measuring the attack surfaces of two FTP daemons , 2006, QoP '06.
[23] Victor R. Basili,et al. The influence of organizational structure on software quality , 2008, 2008 ACM/IEEE 30th International Conference on Software Engineering.
[24] Bart Baesens,et al. Benchmarking Classification Models for Software Defect Prediction: A Proposed Framework and Novel Findings , 2008, IEEE Transactions on Software Engineering.
[25] Nachiappan Nagappan,et al. Predicting defects using network analysis on dependency graphs , 2008, 2008 ACM/IEEE 30th International Conference on Software Engineering.
[26] Ahmed E. Hassan,et al. Predicting faults using the complexity of code changes , 2009, 2009 IEEE 31st International Conference on Software Engineering.
[27] Philip J. Guo,et al. Characterizing and predicting which bugs get fixed: an empirical study of Microsoft Windows , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.
[28] Michael Howard,et al. Measuring Relative Attack Surfaces , 2005 .
[29] Laurie A. Williams,et al. Can traditional fault prediction models be used for vulnerability prediction? , 2011, Empirical Software Engineering.
[30] Andreas Zeller,et al. Predicting defects using change genealogies , 2013, 2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE).
[31] S. Dick,et al. Applying Novel Resampling Strategies To Software Defect Prediction , 2007, NAFIPS 2007 - 2007 Annual Meeting of the North American Fuzzy Information Processing Society.
[32] Tim Menzies,et al. Problems with Precision , 2007 .
[33] Laurie A. Williams,et al. Approximating Attack Surfaces with Stack Traces , 2015, 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering.
[34] Tracy Hall,et al. A Systematic Literature Review on Fault Prediction Performance in Software Engineering , 2012, IEEE Transactions on Software Engineering.
[35] Alex Aiken,et al. Building a Better Backtrace: Techniques for Postmortem Program Analysis , 2002 .
[36] Kim Herzig,et al. Using Pre-Release Test Failures to Build Early Post-Release Defect Prediction Models , 2014, 2014 IEEE 25th International Symposium on Software Reliability Engineering.
[37] Shaohua Wang,et al. Improving bug localization using correlations in crash reports , 2013, 2013 10th Working Conference on Mining Software Repositories (MSR).
[38] Thomas Zimmermann,et al. What Makes a Good Bug Report? , 2008, IEEE Transactions on Software Engineering.
[39] Laurie A. Williams,et al. Searching for a Needle in a Haystack: Predicting Security Vulnerabilities for Windows Vista , 2010, 2010 Third International Conference on Software Testing, Verification and Validation.