Leveraging SecDevOps to Tackle the Technical Debt Associated with Cybersecurity Attack Tactics
Context: Managing technical debt (TD) associated with external cybersecurity attacks on an organization can significantly improve decisions made when prioritizing which security weaknesses require attention. Whilst source code vulnerabilities can be found using static analysis techniques, malicious external attacks expose the vulnerabilities of a system at runtime and can sometimes remain hidden for long periods of time. By mapping malicious attack tactics to the consequences of weaknesses (i.e. exploitable source code vulnerabilities) we can begin to understand and prioritize the refactoring of the source code vulnerabilities that cause the greatest amount of technical debt on a system. Goal: To establish an approach that maps common external attack tactics to system weaknesses. The consequences of a weakness associated with a specific attack technique can then be used to determine the technical debt principal of said violation; which can be measured in terms of loss of business rather than source code maintenance. Method: We present a position study that uses Jaccard similarity scoring to examine how 11 malicious attack tactics can relate to Common Weakness Enumerations (CWEs). Results: We conduct a study to simulate attacks, and generate dependency graphs between external attacks and the technical consequences associated with CWEs. Conclusion: The mapping of cyber security attacks to weaknesses allows operational staff (SecDevOps) to focus on deploying appropriate countermeasures and allows developers to focus on refactoring the vulnerabilities with the greatest potential for technical debt.
Sun 26 MayDisplayed time zone: Eastern Time (US & Canada) change
14:00 - 15:00
|Leveraging SecDevOps to Tackle the Technical Debt Associated with Cybersecurity Attack Tactics|
|Balancing Resources and Load: Eleven Nontechnical Phenomena That Contribute to Formation or Persistence of Technical Debt|
Richard Brenner Chaco Canyon Consulting
|Identifying Scalability Debt in Open Systems|