EPISODE 186
“Fire Doesn’t Innovate” second edition

EP 186: “Fire Doesn’t Innovate” second edition

Our bi-weekly Inflection Point bulletin will help you keep up with the fast-paced evolution of cyber risk management.

Sign Up Now!

About this episode

June 17, 2025

The second edition of “Fire Doesn’t Innovate” has dropped. What’s new? Why it was updated? How can different types of readers get the most value from it? Let’s find out with your hosts Kip Boyle, CISO with Cyber Risk Opportunities, and Jake Bernstein, Partner with K&L Gates.

You can pick up a copy of “Fire Doesn’t Innovate” second edition (paperback or Kindle versions) — https://a.co/d/64hzmxN

See Episode 124 for full details on the “United Structures of America” case — https://cr-map.com/podcast/124/

See Episode 136 for full details on the “iRobot lawsuit against Expeditors International” — https://cr-map.com/podcast/136/

See Episode 141 for full details on the “NIST Cybersecurity Framework version 2” update — https://cr-map.com/podcast/141/

Tags:

Episode Transcript

Speaker 1: Welcome to the Cyber Risk Management Podcast. Our mission is to help executives thrive as cyber risk managers. Your hosts are Kip Boyle, Virtual Chief Information Security Officer at Cyber Risk Opportunities, and Jake Bernstein, partner at the law firm of K&L Gates. Visit them at cr-map.com and klgates.com.

Jake Bernstein: So Kip, what are we going to talk about today in episode 186 of the Cyber Risk Management Podcast?

Kip Boyle: I'm so excited to tell everybody about the topic today because it's the second edition of my book, Fire Doesn't Innovate and I worked really hard to get to this point. And if anybody out there has never written a book before, it is really cool once you actually get something out and available for people to purchase. And sometimes people ask me like, "Well, do you like being an author?" And I say, "Well, I like having written a book." It's all the sweat and effort to get to this point that is not terribly fun, but it is straightforward. It's a bit of a grind. But I want to talk today about why I did a second edition, what's new and how different readers can get the most value from it.

Jake Bernstein: Well, Kip, I have a couple of questions on this. This is very timely and I'm wondering what I should do here because I just brought a case of first edition to my office, so I realized I found them hiding in a cabinet in my office, and they'd been there a while. But exactly how long has it been since the first edition came out? See how I've worked this in?

Kip Boyle: Yeah. Yeah. That's good. Well, the first edition was published January 10th, 2019. So that's pre COVID, right?

Jake Bernstein: That is. Wow. And I think you actually announced that ... We had talked about it, and I know you had sent around some early drafts for people to read. Didn't we announce it in episode 20?

Kip Boyle: Yeah. Episode two zero and we're coming up on episode 200.

Jake Bernstein: So it's been a while.

Kip Boyle: Just over six years. And the second edition of my book came out. It actually went on sale May 9th, 2025. So yeah, six years. Now I'm really happy about the fact that I wrote a book that has to do with cybersecurity and it had a long shelf life. I think that's wonderful. But just to get the first edition out, that was the first time I actually published a book and I needed so much help to get it done. I actually had a writing coach, an editor. I had somebody do the interior layout. I had a cover artist. You name it. It was just working with a traditional publisher except I had to pay for it all because I didn't want to share rights with a traditional publisher. Anyway, that's a whole other conversation. But I spent the spring and summer of 2018 writing the manuscript, and then it came out, as I said, in January 2019. But yeah, that's the history.

Jake Bernstein: Well, at the risk of derailing us immediately, we had our little pre-show discussion, and of course we were talking about large language models and ChatGPT and Claude. And it occurs to me that when you wrote this, none of those ... If any of those things existed, they were in larval form, entirely experimental. I actually don't know. I think that was actually pre transformer, which means could it was was even pre GPT, like 1.0 or 2.0?

Kip Boyle: It could have been, but I didn't even know those things were-

Jake Bernstein: Yeah. It wouldn't have mattered because they were all ... If they did exist, and I don't know that they did, they were in research labs only. So things have changed a lot, right?

Kip Boyle: Yeah.

Jake Bernstein: Over six years now. In some ways in an unreasonably ridiculous amount, which I think just goes to underscore the incredible speed at which things have developed across over the last six years. And it isn't per se in cyber security. It's not like the fundamentals have changed over six years. It's not like you had to throw out Fire Doesn't Innovate first edition and just be like, "Well, I was totally obsolete."

Kip Boyle: Right. That can happen.

Jake Bernstein: Yeah. And we're going to talk about that. But before we get into all that, before I harass you and ask were you able to use AI? Did you use AI for anything in the book? And I think it's an interesting question. Because it comes with a lot of ethical components. There's no doubt that Amazon is probably already full of AI generated slop as the kids say. But there's lots of what I've started to call mental manual labor that you've already talked about. Interior layout, editing, generating cover ideas that frankly AI has become really good at. So maybe we'll come to that, maybe we won't. Maybe we can do a separate episode on that. But let's first start by asking how has the first edition been received? It's been out for a while. How has it done?

Kip Boyle: I think it's done really well. It's certainly achieved my goals, my expectations for it. But all you have to do is go to the Amazon page for it. And I'm happy to say it's got 4.6 out of five stars. There's actually 49 ratings on the book. I haven't really encouraged people to go give review. Some people do, and maybe I should have. I will again.

Jake Bernstein: But no offense, but Fire Doesn't Innovate is not a mass market paperback that's going to be read by millions of people. That was never the point.

Kip Boyle: Never part of my expectation.

Jake Bernstein: So if you ask me 49 ratings ... To have 49 readers actually go and rate you on Amazon is pretty cool.

Kip Boyle: I think it is. Yeah, I do. I'm glad you contextualized it because you're right. I didn't write this book for everybody. I wrote it for a very specific audience with a very specific idea. And so that's one of the reasons why I feel like it's done really well. Now these days, of course, with all the AI going on, I don't know if you've noticed, but Amazon-

Jake Bernstein: I have.

Kip Boyle: Putting a little AI summary of all the reviews, and I like how it summarized all these 49 ratings. It says, "Customers find the book to be a great guide for leading cybersecurity risk evaluation with one review highlighting its methodology for assessing security controlled maturity. People also say the book is remarkably easy to read, using everyday language for everyday people." And booyah, that's what I needed to be able to do.

Jake Bernstein: I am sorry to report, but booyah is like 20 plus years ago, just so we're clear.

Kip Boyle: I know. I know. Hey, I'm old. What can I say? But I like it. I like saying it. So sorry. Sorry. If there's any Gen Z in the audience, curse me now.

Jake Bernstein: Yeah. Well, what he meant was ... Actually, I don't even know what the Gen Z would say. Yeah.

Kip Boyle: So I've got Gen Alpha. I got kids that we're born 2013 and 2014, and it's just hilarious listening to them come home. Let's see, what would they say? Oh, they'd probably use skibbity or riz or something like that.

Jake Bernstein: Yeah. It's like a different language.

Kip Boyle: For sure. And of course, I can't help as a dad, I'm constantly using those words and knowingly using them wrong.

Jake Bernstein: Oh, that's the best part.

Kip Boyle: Oh, it's just so much fun. It's just so much fun. Anyway, but there was one favorite part in the AI review. I don't know how this person was thinking, but they said that they appreciated the book style it and readability so much that they compared it to reading a mystery novel. Can you believe that?

Jake Bernstein: That's great. A cybersecurity book that reads like a mystery novel is definitely an accomplishment.

Kip Boyle: That was not one of my goals.

Jake Bernstein: No. Well, there you go. Okay. So before you tell us what's new in the second edition, and maybe we talk about how you created the second edition, why don't you remind our listeners how people typically use the book, particularly since it's been probably six years since we really talked about it on the show?

Kip Boyle: Yeah. It has been a long time. So there's actually a lot of use cases for the book, and it really depends on your role. So for example, if you're a non-technical senior decision maker, so that's like CEO, chief operating officer, chief financial officer, chief legal officer, or maybe a corporate risk manager, somebody who's in charge of insurance and that sort of thing. What I find works for them is that they should read part one, which is called the Basics of Cybersecurity. And the idea there is you don't have to know any jargon to read part one. I wrote it jargon-free, just like the Amazon review said. And after they read part one, then they should go to a technical expert that they rely on for making major cybersecurity decisions and give it to them and then just say, "Hey, I just read this part one, and there's some stories in there, and I think we should talk about those stories because I think some of them apply to us. So just read it quickly." And so it's a conversation starter. It bridges that gap between the non-technical and the technical decision makers. So that's one of the use cases.

Jake Bernstein: Excellent. Excellent. So what about the technical folks now? What are they going to get from it? Are they going to read it as well?

Kip Boyle: Yes. Now the reason why we get people like CIOs, chief technical officers, VPs of IT, the reason why they read it isn't because they don't understand this stuff already necessarily. They probably get most of what I'm talking about. But what they get from it is a vocabulary for talking about something they understand, but doing it in a non-technical way. So they don't spew ones and zeros at people. Now, they can actually talk in a language that the non-technical people can understand. Now after they read it and they get that benefit, they have an opportunity to build a bridge too. So they should give it to non-technical senior decision makers who are in charge of budgeting. Give it to them and say, "Would you please read this?" Because technical decision makers need to have an ongoing conversation with the non-technical people as well. And so this is a really good way to do that. To kick off an ongoing conversation.

And I've had people say to me, yeah, there was this one anecdote you told, and we refer to that constantly because it resonated so strongly with us. And anytime I'm trying to bring somebody back to ground truth on this, I just reference the anecdote or the case study that you gave. I was really happy to hear that because that's exactly what I'm hoping people will do with it. Now, if you're a CISO I actually recommend you start with part two of the book, which is called Your Cyber Risk Management Action Plan, because that is all about implementing the NIST cyber security framework version two, using a top-down approach. That's how it's intended to be used. And so part two might be the best-

Jake Bernstein: The best place to start.

Kip Boyle: Mm-hmm.

Jake Bernstein: Okay. And we've talked about it before I think many times, but when you're implementing the NIST cyber security framework version two, or really any other major framework, why is the top-down approach so critical?

Kip Boyle: Oh, yeah. Well, okay, so let's first of all be clear on the difference. So a bottom-up method is going into the ones and zeros. You're at the technical level. So think Center for Internet Security's top 18 critical security controls. You're down in the weeds and you're going up from there. And that's what most security people have done for years and years and years. I have. It is just a very typical place to start. But the top-down approach does something that a bottom-up approach really struggles with or can't do it all, which is buy-in. You can increase the buy-in of your senior decision makers by using a top-down approach, and it makes it much easier to secure your organization's resources and to become more cyber resilient because of the buy-in factor.

And lately, I've been telling everybody, look, you have to be hard to hack. Of course, we've all known that, but now you also have to be fast to fix. And so that really is the cyber security framework. And so that's the idea of the top-down and why it's different. And I also should say that we have a lot of advisors who read the book, outside counsel, insurance Brokers, fractional CIOs, Fractional CISOs, which is what I do, and they use it so that they can better serve their clients. And I would say that they should either start with part one or part two, depending on what their immediate needs are.

Jake Bernstein: Got it. Got it. Okay. So this is super helpful information. I'd say about the first edition and then the CSF, which of course we talk about all the time. But let's get into what's new in the second edition.

Kip Boyle: Sure.

Jake Bernstein: So the book went from 266 pages to 287 pages. So just mathematically, you've added 21 pages of content, but I doubt you simply added 21 pages and called it a day. So what changed? What happened?

Kip Boyle: So ever since I published the book, anytime anybody ever said to me, have you considered this, or what about that, or whatever it was, whatever the feedback was, if it was a good piece of feedback, a constructive piece of feedback, I actually had a little file that I kept all the ideas in, all the suggestions. So when I sat down to rewrite it, I already had a lot of feedback that I could look at. And what I figured out from reading the feedback was part one needed a complete word for word rewrite because of-

Jake Bernstein: That is a little bit starting over in a sense.

Kip Boyle: Well, for part one, yes, but the structure of part one didn't need a lot of adjustment.

Jake Bernstein: Got it.

Kip Boyle: In other words, the topically, I didn't need to change much of what I was covering, but a lot of the cases ... There were so many better cases and more recent cases that I could use to make my point. When I released the book, first edition ransomware wasn't as big of an issue as it is now. So I added information on ransomware. I also deleted a whole bunch of stuff in order to make room for the newer material. Because I didn't want to just balloon the book out an extra a hundred pages or whatever. So I purged a lot of stuff. It was tough because I wanted to keep it, but at the same time, I just had to make those hard decisions. And then the other thing too is I kept my own notes based on Cybersecurity Framework version two, that came out since my first edition. And I've worked with so many customers, so many-

Jake Bernstein: I'm not even sure if version 1.1 was out for that long. by the time you published, it would've been close.

Kip Boyle: Yeah. I think version one of the framework was out just long enough for me to use it in the book-

Jake Bernstein: But not by much.

Kip Boyle: Yeah. It wasn't by much. But the Cybersecurity Framework version two has certainly been out for a while now. And so I absolutely had to include that. But in the six years since I released the first edition, oh my gosh, I've given so many presentations, worked with so many customers, partners, I've written so much stuff. I've created so many LinkedIn learning courses, Udemy courses. Podcast-

Jake Bernstein: We've recorded over 150 episodes.

Kip Boyle: Yeah. I just had so much more experience. I felt like I was just smarter this next time. So I had to factor all that in as well. So for example, the essential eight, I knew about the essential eight when I wrote the first edition, but it didn't really have a lot of experience with it. And now of course, I love it and recommend it. So that had to go in. And then we've got other things like security keys. So a USB security key, a near field communication security key. These are new and important things that I didn't mention last time. Pass keys. That's new. Generative artificial-

Jake Bernstein: Of course.

Kip Boyle: Deep fakes.

Jake Bernstein: Deep fakes. Yes.

Kip Boyle: Yeah. So there's just so much that has happened. And so I had to give coverage to all that as well.

Jake Bernstein: Absolutely. All of these things have really evolved since 2019, so I think that makes a great deal of sense.

Kip Boyle: Yep. Oh, and then one of my big accomplishments, although it was acceptably difficult, is I remember people saying, "Why doesn't your book have a subject matter index? A subject index?" And I just didn't even think about that the first time around at all. But now we have one. It's really good.

Jake Bernstein: Now you have one. Excellent. Okay. So that's improvements suggested by readers. What about the case studies? Because obviously a lot has happened in the six years. How did you even approach case studies for the book?

Kip Boyle: So here's what I figured. There's so many case studies, and I thought to myself, well, I have favorites. I don't mind saying that. And so I looked at our podcasts, and so I was like, well, if we did a podcast episode on a case, then that meant to me that it was worthy of consideration of putting in the book. For example, United Structures of America I think is a marvelous case because we did a podcast episode on that. That was in episode 124. And the reason why I love it is because here's a Houston, Texas-based steel manufacturer, a hundred million dollars of revenue, 450 employees. They were an industry leader, but they got catastrophically attacked by ransomware in 2019, and now they're bankrupt. And so it really shows what's at stake here. And the other thing that was really great about United Structures of America is that the CEO actually did a series of interviews with the Wall Street Journal where he actually said, "This is what it was like for me going through this and why I made the decisions that I made, and ultimately what I think I should have done compared to what I actually did." And you just don't get that kind of transparency very much. So that had to go in. And I'll put a link to that episode in the show notes, so if people want to check that out.

And then there was one other one that I want to mention now, which is Expeditors International. So they really got into a bad way, and there was a lawsuit that was filed against them, and the lawsuit contained all this incredible detail that I just thought, again, makes all of this very abstract cyber stuff very, very concrete. So if you go to episode 136, you can listen to that. But the bottom line is that Expeditors International is a freight forwarder. So if you buy something from China, they can either put it on a jet, put it on a boat, and then put it on a train and get it to wherever you want, but they also will store things in their warehouse and be your warehouse manager. And that's what happened here was iRobot, like the Roomba vacuums that you can have in your house. Well, they were a customer of Expeditors because Expeditors had a ransomware attack with a three-week total global outage of their freight forwarding network it caused iRobot to completely take over their own logistics at the drop of a pin, and they just had to just do so much to get themselves back in business.

And so they ended up filing a $2 million lawsuit against Expeditors. And they detailed all the machinations they had to go through because Expeditors couldn't provide their logistics anymore due to this outage. So yeah. So all these contractual violations happened and it ended up in a lawsuit. And I decide, again, just a very powerful case to illustrate what's at risk.

Jake Bernstein: It is. It is. Very, very useful in terms of determining and showing people what can go wrong. Let's talk about part two. What happened to part two?

Kip Boyle: Okay. So part two also got some heavy revisions, but the essence of part two is still the same, which is this methodology called the cyber risk management action Plan. That is a service that we perform for our customers. And in the first edition of the book, I actually disclosed a tremendous amount of step-by-step guidance on how we actually do it. Because I wanted to first of all give to the community. I wanted everybody to be able to make a CR map if they wanted to. And also, I felt like being transparent about how we work would be helpful to maybe encourage a few readers to work with us and that has happened.

So I like that. But I had to really do a serious revision of part two. First of all, I had to get the NIST Cybersecurity Framework version two in there. So now we have an all new question set that's aligned to version two, which will help you find your organization's top five cyber risks. And then we have a companion online workbook that's in Google Sheets, and that's been completely revised as well, so that it aligns with part two. And so that's what happened there. And then there was a lot of clarifications that I needed to make because people would ask me questions and I'd be like, "Oh yeah, that's not very clear, is it?"

Jake Bernstein: Well, that always happens, right? You can edit and revise forever if you're not careful.

Kip Boyle: That's a trap for sure.

Jake Bernstein: It really is. Okay. So why was it important to update for NIST CSF version two? I feel like that's a softball question, but there you go. I lobbed it for you.

Kip Boyle: Yeah, thank you very much. I appreciate that. Let me hit it now. Well, NIST CSF version two, it came out in February 2024. We're recording this at the end of May 2025. And so it better reflects the reality of the world that we live in now. And that's one of the reasons why I recommend CSF version two over other choices like ISO 27001 and other things, because it's fresh, it's more relevant. And so as an industry, we've learned a lot over the past decade. So CSF version one came out in February of 2014, that's 10 years. So I really felt like, okay, I've got to keep up with this and I don't want to overlook anything. So governs got its own function now. There's just so much really great refinement in version two of the framework compared to version one. And before I get distracted and launch into a discussion of that, I'm just going to say, everybody go listen to episode 141, because that's where we did a full treatment of what's new in version two. So anyway, it needed to be in there.

Jake Bernstein: It did. It did. Okay. So for the listeners who already have the first edition, is it worth getting the second edition?

Kip Boyle: I think so. And am I biased? Of course I'm biased. Of course I am. But let's talk about the practicality of it. Okay. So if you're actively working on your cybersecurity program, I would say getting the book for the case studies alone would probably justify it because they're more relevant, they're more timely, they're more reflective of what's really going on these days. There's nothing wrong with the case studies in part one except they're just stale. So I think you would want it for that. You would also possibly want it because part two is also a revision of our cyber risk management action plan method.

Jake Bernstein: I don't think you even called it that in 2018.

Kip Boyle: No. We called it a cyber risk management game plan. And that was one of the many marketing iterations that we went through in order to find a good name for this methodology. And listen, people marketing matters. Let me tell you, marketing matters. And I can't always explain why people react the way they do, but I thought a cyber risk management game plan was a very good name for this, but I actually got a lot of faces back at me that looked like somebody had sucked on a lemon. They did not like that. So I had to swap it for ... I took out game plan and I made it action plan and voila, chef kiss, everybody started really loving it. I didn't change it. I just gave it a different name. So there you go. There's a little marketing bit. And then of course, if you want to find easy ways to talk to your people about AI, deep fakes, pass keys, all that new stuff, well then reading the book to be able to use ordinary language to talk about that stuff, that could be helpful.

Jake Bernstein: Excellent. So where can people get the book Kip?

Kip Boyle: Amazon. You can get the paperback or the Kindle version right now, but you have to search for Fire Doesn't Innovate second edition because the first edition page is still live. Now I'm going to take it down eventually, but I'm not done with it yet. But just to save everybody some time, I will have a link in the show notes so you don't have to struggle.

Jake Bernstein: Well, there you go. Okay .so I think we can probably ... Well, no, not yet.

Kip Boyle: You're going to go for the wrap up.

Jake Bernstein: I was going to, but really I was going to punt it over to you because that's how we do wrap up. I do want to know one thing. Were you able to find a use case for generative AI in the revising process?

Kip Boyle: Yes. So generative AI, specifically Claude Sonnet 3.5 I think was the one, was a writing partner for me. All right. Now let me tell you what I mean by that. So I did not ask Claude Sonnet 3.5 to rewrite my book. I did not do that. What I did do is whenever I was stuck, I viscerally remember groping for an analogy to explain ... Because when I was trying to explain pass keys, for example, what's the difference between a pass key and a security key, because I wanted to be super clear about that and I wanted to be-

Jake Bernstein: Or a password. And I actually realized that I'm still not totally sure. So I guess I'll have to get the second edition.

Kip Boyle: Yeah. So whenever I was really struggling to figure something out, I would go to Sonnet and I'd say give me five different ways to describe the difference between a security key and a pass key. And so I would do brainstorming with it, and then that would get me unstuck and I would keep going. But I was very careful because you and I, Jake have told our clients, if you are going to copyright something, you better be careful how you use AI.

Jake Bernstein: Oh, for sure. For sure. Absolutely.

Kip Boyle: I wanted to be sure that there wouldn't be any awkwardness.

Jake Bernstein: Oh yeah. Yeah, for sure. As tempting as it sounds to feed the entire manuscript into an AI for editing, I don't think most AIs are able to really do that yet. You'd probably have to chunk it up just for proofreading purposes.

Kip Boyle: And honestly, I wouldn't trust it because if I did that ... Because we've both said to everybody who will listen, don't just use what it spits out at you.

Jake Bernstein: Of course not.

Kip Boyle: You've got to review it to make sure that it's correct. Well, I didn't want to have to read my whole book cover to cover to see what it got wrong. I was just like, "Oh God, no. I can't do it." I've read this book so many times.

Jake Bernstein: I'll give you a hint, Kip, when you want AI to review something, tell it, do not make any changes. Just give me suggestions and tell me where those changes should be made.

Kip Boyle: But still, it's non-deterministic here.

Jake Bernstein: Yes. And also at a book length, that's way less helpful than it is when I'm doing a short email or even a short memo.

Kip Boyle: Now see, that's different, like a short email, a short memo, I don't really have copyright concerns there.

Jake Bernstein: That's true. I do not.

Kip Boyle: Plus the length is more reasonable and within its grasp. So I agree with you. There are times when generative AI, at least at this stage of the game just can't do the job. So even if copyright wasn't a concern, it just can't do it now.

Jake Bernstein: I agree. I agree. Okay. Well now I think we can go ahead and wrap this episode up.

Kip Boyle: Yeah. So that does wrap up this episode of the Cyber Risk Management Podcast. Today, we talked about the second edition of my book, my baby, Fire Doesn't Innovate. We talked about what's new, why I updated it, how it's different, and how different types of readers can get the most value from it. So thanks everybody. We'll see you next time.

Jake Bernstein: See you next time.

Speaker 1: Thanks for joining us today on the Cyber Risk Management Podcast. If you need to overcome a cyber security hurdle that's keeping you from growing your business profitably, then please visit us at cr-map.com. Thanks for tuning in. See you next time.

Headshot of Kip BoyleYOUR HOST:

Kip Boyle
Cyber Risk Opportunities

Kip Boyle is a 20-year information security expert and is the founder and CEO of Cyber Risk Opportunities. He is a former Chief Information Security Officer for both technology and financial services companies and was a cyber-security consultant at Stanford Research Institute (SRI).

YOUR CO-HOST:

Jake Bernstein
K&L Gates LLC

Jake Bernstein, an attorney and Certified Information Systems Security Professional (CISSP) who practices extensively in cybersecurity and privacy as both a counselor and litigator.