John Martin — Preventing a Cyberpocalypse

What happens when society’s dependence on software grows faster than its ability to make that software safe? John Martin, a commercial software security practitioner and SAFECode contributor, calls that widening gap a possible cyberpocalypse. He explains the combined pressures of vulnerable legacy code, expanding connectivity, and increasingly capable attackers. The hosts challenge his proposed responses, exploring software liability, standards, quality measurements, and the risk of constraining innovation. The discussion compares software assurance with product safety and building inspections, while questioning whether following a development process is enough evidence of a safe outcome. This is an exploratory debate about responsibility and incentives, with John urging the industry to confront systemic software risk before its consequences become harder to contain.

The Application Security Podcast is brought to you by Security Journey.

About Security Journey
Security Journey provides application security education for developers and everyone in the software development lifecycle.
→ Learn more about Security Journey

Connect with John Martin:
→ John Martin on LinkedIn

Mentioned in this episode:
→ SAFECode
→ Cloud Security Alliance

Follow the Application Security Podcast:
➜ Home
➜ X
➜ LinkedIn
➜ YouTube
➜ Instagram
➜ Facebook

Chapters:
00:00 Preventing a cyberpocalypse with John Martin
01:45 John’s security origin story
04:26 Connecting breaking and building software
09:27 What John means by cyberpocalypse
12:28 Sudden catastrophe or accumulating harm
16:15 Technical debt and deferred responsibility
17:38 Ways to improve software outcomes
19:54 Measuring software quality
21:27 Liability and defining safe software
25:39 Could safety requirements constrain innovation?
27:51 The difficulty of a meaningful safety standard
31:29 Measuring process versus results
36:43 Software assurance and independent inspection
38:21 Where the industry conversation is happening