BL

Bob Lord

Things Bob Says on Podcasts

Where to Find Them

Bob Lord has been a guest on CyberWire Daily (2 times) , The Lawfare Podcast and The Lawfare Podcast: Patreon Edition .

Recently: “Making software safer: Introducing the Software Safety Institute. [Special Edition]” on CyberWire Daily (November 2026); “Out of office, out of service.” on CyberWire Daily (November 2026); “Three CISA Senior Advisers on Secure by Design” on The Lawfare Podcast (December 2023); “Three CISA Senior Advisers on Secure by Design” on The Lawfare Podcast: Patreon Edition (December 2023).

What They Said

“The MITRE Corporation wrote a paper in 2007 called 'Unforgivable Vulnerabilities.' They're not prone to hyperbole or clickbaity articles. The vulnerabilities they called unforgivable were cross-site scripting, SQL injection, path traversal, classic buffer overflow. If you look at their 2025 report of the most dangerous vulnerabilities, those are still at the top of the list.” — Bob Lord, CyberWire Daily

Asked for examples of preventable harm from insecure software, Bob Lord points to the same basic classes of coding error topping the vulnerability lists 18 years apart.

CyberWire Daily · 2026-11-15 Permalink → Listen →
CyberWire Daily Around 05:53 into the episode
Bob Lord

…V, which are the visionaries. These are the people who have been telling us how to build safer software literally for decades. And it's time to give them the spotlight and the mic so that we can start doing the things that are really going on. To change the outcomes that Lauren just spoke about.

Dave Bittner

Well, Bob, let me stick with you here. When you talk about preventable harm from insecure software, what does that look like in practice? Are there any examples you can share?

Bob Lord

Yeah, so one of the things that we'll be doing at SSI is really trying to make some of these concepts a little bit more commonly understood. There are a number of topics that are secret, not because anybody's attempting to keep them secret, but just because the incentives don't reward people really talking about these. So, for example, if you go back to a paper written in 2007 called Unforgivable Vulnerabilities, it's written by the MITRE Corporation. And if you know their work, you know that they're not prone to hyperbole or clickbaity articles. And so you have to ask yourself what would cause them to say that certain classes of coding error are unforgivable. And so they came up with a methodology and ran the world of 2007 through this methodology. And they said the following kinds of vulnerabilities are unforgivable. What were they? Cross-site scripting, SQL injection, path traversal, classic buffer overflow, things like that. If you go and take a look at their 2025 report of the most dangerous vulnerabilities, you'll see that those are still at the top of the list. And if you take a look at other companies that have recently published other kinds of…

Dave Bittner

Lauren, you and Bob both helped lead CISA's Secure by Design initiative. What did that experience teach you about the relationship between the software manufacturers, their customers, and even the government?

Lauren Zabierek

That experience taught us so much. And we'll just say, too, that we're incredibly grateful for that opportunity. And especially to our former director of CISA, Jen Easterly, who really championed it. She didn't just say, yeah, go ahead and do it. She said, let's do this. She brought Bob in and…

Dave Bittner

I'd love to touch on the sort of carrot and the stick. You know, you've got incentives and you've got accountability. And I know one of your goals is to hope to realign the incentives here, if I have that right. What are those incentives today? And how do we go? About making them better for…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“If you go back to a paper written in 2007 called Unforgivable Vulnerabilities, it's written by the MITRE Corporation… they said the following kinds of vulnerabilities are unforgivable. What were they? Cross-site scripting, SQL injection, path traversal, classic buffer overflow, things like that. If you take a look at their 2025 report of the most dangerous vulnerabilities, you'll see that those are still at the top of the list… the industry as a whole has made little to no progress.” — Bob Lord, CyberWire Daily

Asked what preventable harm from insecure software looks like, Bob Lord, co-founder of the Software Safety Institute, points out that the bug classes MITRE called unforgivable in 2007 still top its 2025 danger list.

CyberWire Daily · 2026-11-13 Permalink → Listen →
CyberWire Daily Around 13:07 into the episode
Bob Lord

…V, which are the visionaries. These are the people who have been telling us how to build safer software literally for decades. And it's time to give them the spotlight and the mic so that we can start doing the things. That are really going to change the outcomes that Lauren just spoke about.

Dave Bittner

Well, Bob, let me stick with you here. When you talk about preventable harm from insecure software, what does that look like in practice? Are there any examples you can share?

Bob Lord

Yeah, so one of the things that we'll be doing at SSI is really trying to make some of these concepts a little bit more commonly understood. There are a number of topics that are secret, not because anybody's attempting to keep them secret, but just because the incentives don't reward people really talking about these. So, for example, if you go back to a paper written in 2007 called Unforgivable Vulnerabilities, it's written by the MITRE Corporation. And if you know their work, you know that they're not prone to hyperbole or clickbaity articles. And so you have to ask yourself, what would cause them to say that certain classes of coding error are unforgivable? And so they came up with a methodology and ran the world of 2007 through this methodology. And they said the following kinds of vulnerabilities are unforgivable. What were they?…

Dave Bittner

I'd love to touch on the sort of carrot and the stick. You know, you've got incentives and you've got accountability. And I know one of your goals is to hope to realign the incentives here, if I have that right. What are those incentives today? And how do we go about making them better for everyone?

Bob Lord

Well, the incentives today give you a world of unsafe software. And so one of the things I just want to echo what Lauren said, which is that when we had really great and productive conversations with the software companies, it was really clear how much they wanted to do more, but there were these…

Lauren Zabierek

Yeah, can I just jump in on that too, Dave? You know, this idea of economics and incentives is really core to this issue. Software security. And let me just say, too, that when we talk about software security and software safety, the security is the property of the product. Safety is the outcome.…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In