EP 197: Operational Cyber Resilience
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
November 18, 2025
What happens when critical third-party services go down? What do your vendors actually owe you when that happens? Are new regulations going to make a difference? Let’s find out with our guest Dan Bowden, Global Business CISO with Marsh McLennan. Your hosts are Kip Boyle, CISO with Cyber Risk Opportunities, and Jake Bernstein, Partner with K&L Gates.
“Cyber Incident Reporting for Critical Infrastructure Act” (CIRCIA) episodes:
https://cr-map.com/podcast/161/
https://cr-map.com/podcast/162/
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 197 of the Cyber Risk Management Podcast?
Kip Boyle: Today we've got Dan Bowden, he's the global business CISO with Marsh McLennan, and we've invited him here because what we're going to talk about today is third-party risk management and resilience. As we were getting ready to go live, Dan's like, yeah, speaking of, we've got a doozy going on today that just popped out, so we might mention that. But generally, what we want to do today is explore what happens when critical services go down and when that happens, what do your vendors actually owe you, and how some new regulations we think are going to change the game. So, that's our subject today.
Jake Bernstein: Excellent. Well, I'm really looking forward to this conversation. Third-party risk is, I don't know, I don't want to say that it has overtaken in importance, everything else, but it does feel like it still doesn't get the attention that it deserves. So, look, every single organization I talk to deals with this. Whether they know it or not, it's frightening when they don't fully understand it. We're just all so dependent on cloud services and SaaS applications that when they fail, oftentimes people don't know what to do. We fail too. So, yeah.
Kip Boyle: Yeah, it's like going through a blackout, right? When the power fails, you're like, "Eh, I guess I just got to wait for the power to come back on."
Jake Bernstein: Yep.
Kip Boyle: And of course, artificial intelligence is the shiny new thing, so everybody's super interested in that. And third party risk...
Jake Bernstein: It's just more SaaS, right?
Kip Boyle: Mm-hmm, mm-hmm. Yeah. In many respects, it is. But I think Dan's the perfect person to help us understand this landscape. So, Dan, thank you. Welcome to the show. Now would you please tell our listeners about a little bit about you and your role at Marsh McLennan?
Dan Bowden: Well, thanks a lot, Kip. I am hoping to live up to being pretty good, I wasn't sure about perfect, but I'll try to pick it up a little bit if I can. Marsh McLennan, we're a global company, risk advisory and insurance broker career investments, reinsurance management consulting, but 90,000 colleagues, a hundred thirty-ish countries and not just the time, I've been there almost four years now and really enjoyed it.
Kip Boyle: That's an enormous scope of responsibility, both in terms of head count as well as geographical spread. What a complex environment. Okay, that's why I think you're the perfect person to talk to about this, right? You're the right guy in the right place at the right time. All right, let's start with a big question that I think a lot of CISOs lay awake night thinking about this, but what happens when you've got a critical third-party service and it goes down? I mean, I got to imagine that you guys have things like that, right?
Dan Bowden: Yeah, especially when you're a global company and you work in a lot of different markets and country in frequently, you're not actually wondering if something's going to happen. You're just waiting for when. And depending on the nature of business in a given country, different suppliers can have different impacts, and there's some of the global ones that maybe we use everywhere. Everyone uses Microsoft. Microsoft will be disrupted, that's a global event, but sometimes we have other suppliers that deliver a very particular application for us. And so, it's important to note that.
And on the Microsoft example, people remember going without Microsoft the day that there was a CrowdStrike software update that ran afoul and knocked down a lot of customers. And so, it can be something that happens frequently and you've just got to find ways to be prepared for it.
Kip Boyle: So, CrowdStrike happened over a year ago already, which is-
Jake Bernstein: Wow.
Kip Boyle: ... hard to believe, but definitely. And then right after or right around the time that the CrowdStrike thing happened, there was another distributed denial of service attack that happened a little bit later, right, Jake?
Jake Bernstein: Yeah, I mean there was Azure and the Microsoft 365 outage on July 30th. It was totally separate as far as we know from the CrowdStrike fault. And that second one hit a lot of organizations hard because I mean at this point, it's embarrassing not to be on Microsoft 365 or Google workspaces, which actually that might be the duopoly right there. I don't know if there is a third that I can reasonably think of that a serious business would use. You're either a Microsoft shop or a Google shop, which I mean right there, that's a lot of risk, right? There's two options. And when one, I guess AWS is another example, a lot of the internet lives on and operates on AWS.
So, between these three large cloud companies, if anything happens to them, it's like a mandatory non-optional holiday for everyone. And that is, I don't know if people have fully internalized that in terms of third-party risk.
Kip Boyle: Well, they don't go down that often, right? I mean-
Jake Bernstein: They don't.
Kip Boyle: ... that's one of the reasons why people I don't think are... I mean, ordinary business leaders are probably not laying awake thinking about it like a CISO is.
Jake Bernstein: But here's the thing is isn't this a little bit ironic? We invent the internet, DARPA net precisely to be incredibly multiply redundant in order to survive nuclear attack and everything could just route around the new radioactive craters. And the whole point was resilience.
Kip Boyle: Survivability. Yeah.
Jake Bernstein: Haven't we have in some ways undone that by basically relying on three companies to provide our services and basically the infrastructure? So, Dan, does anyone have good backup plans or are we just like, "Nope, guess we're just done for the day"?
Dan Bowden: Well, it's interesting, right? When it was your own data center, it was right there in front of you, all these natural thoughts occurred. You know if there was a thunderstorm coming in. Remember back in the days, you'd think about that, something that simple.
Kip Boyle: Or hurricane if you were in the area.
Dan Bowden: Yeah, we take everything for granted now. The cloud, it never goes down until it does. And I think that backup plans and business resilience plans are now, the smart companies are trying to figure out how to show they can we lose it. We still have a way to maintain business. Either we can recover quickly, or we know how to do this manually and that's where they've got to go. It's hard to do that.
Kip Boyle: Yeah, definitely. I visited India one time. I was there for a couple of weeks, and one of the things that really shocked me about how they do infrastructure in India is you have these little, at least what I saw was a little enclave where there was a company that was doing business process outsourcing for western companies or something like that, and they would build their facilities wherever, but the infrastructure around the facility wasn't generally good enough to give them 24/7 power, right? And so, they actually have their own miniature power plants in the form of diesel generators, or whatever right there in their compound.
And wow, my eyes were really opened when I went there because of course, I'm a spoiled American and I rarely deal with power outages because we've got a relatively good electrical grid here. It's got issues. And so, cloud computing sometimes makes me think about that, right? That we've gone from having our own power generation capabilities and now we're just relying on the big cloud in the sky to provide us with all this compute. And I remember when people talked about how cloud was going to be utility computing, or something like that. Anyway, does that resonate with you, Dan? I mean, do you think of it in the same way?
Dan Bowden: Well, it comes down to managing the agreement and the service, right? Did you read the contract? Did people actually do the math and understand the impact when there's some kind of an outage? Do you run things like tabletop exercises to understand what will happen, and what's this really costing us? And I think that when people actually go through that exercise, we don't have the staff service or whatever it is. It takes doing that to actually wrap your head around what is this going to cost? And then what does the agreement with that SaaS provider say, and are we even able to negotiate and do anything about it?
Because if it's a monster sized SaaS company and you're a medium-sized business, yeah, you're a little fish in a big pond, they're telling you what service you're going to get.
Kip Boyle: Right. Yeah. Or you can go to the other place.
Dan Bowden: If you're in that situation, you're going to have to plan accordingly.
Kip Boyle: Yeah, right. And I think that's another thing that CISOs really struggle with, especially ones that maybe have been around a little bit longer, is when you've outsourced something, you can't control it directly anymore, right? You can when it's on prem. You've got to go through contracts to do that. And so, for people, especially if you've come up through the system's organization, that can seem weird. And it's like there's nothing I can do, which isn't true, but it's just a different way of managing risk. For me, that was something that I had to learn and navigate when I was a CISO. What about you, Dan? Did you have to go through that or was that just not as difficult of a transition for you?
Dan Bowden: It was one problem, I think I'm older than you guys, so I think it was more difficult for me, right? Yeah, the old infrastructure. I knew how the data center was put together and I knew how everything was connected, and could guess when the weather changed, if there was going to be a problem. And now, I think it is just different. You're paying millions of dollars for SaaS providers on something up, and when it's down, you need to know, do I have any recourse? And how long will take? And is there a guarantee? And often, I think we find out that the payback or what that SaaS provider owes you isn't going to be commensurate with your losses in some cases.
They're going to have to figure out how to take care of things yourself, how to resume business, how to keep making money without that service if you have to.
Jake Bernstein: Well, and I mean to put it into industry terms and SLA is not business interruption insurance. Let's just state it that way simply and straightforwardly.
Kip Boyle: Well said.
Jake Bernstein: SLA is service level agreements. These are legal issues, right? These are the things that I deal with that I negotiate, that I help clients work through and figure out. And we speak in terms like 39s or 49s. What does that mean? 99.9% or 99.99%?
Kip Boyle: It sounds good on the surface, right?
Jake Bernstein: It sounds good. And the funny thing is each nine matters a lot, right? There's actually a substantial difference between 99.9, 39s and 99.99. There's a big difference in acceptable downtime. But you know what? Even if it was just 99% uptime, what an SLA does typically is say, if we don't make it, then here's a service credit of some percentage. And when I say that an SLA is not business interruption insurance, I mean that in every sense, the cost savings, sorry, the size of the credit is, I mean it's going to be commensurate with your size, obviously, right? It is a percentage typically.
Kip Boyle: Of your spend on that. Yeah.
Jake Bernstein: And it may be 5% to 10%. It could be even higher depending on how badly you miss the target uptime, basically. But first of all, when does it happen, right? Uptime or unscheduled downtime, let's just say you're a US centered e-commerce company, down time in the middle of the night, you might not ever notice, right? Down time on Black Friday could destroy your business, right? So, even it should just from that example alone, it should be obvious that a simple SLA service credit is not sufficient. So, Dan, I mean what do you do?
Dan Bowden: Look, I think I mean it's always good to try. Of course, they go read the contract, but sometimes there's always so much you can do, right? If you've got to use that provider, and I think about the change health from spring last year, right? In a way, it's a captive network. Those companies that are connected either didn't have another option, or didn't know about any other options. So, all the time change was down, their AR backed up. And so, a lot of real practice health systems were without revenue coming in because of that one outing.
And so, I think that there's just so much contingency planning that need to have and that's the only thing that you can... there's not a silver bullet to make the problem go away. You've got to figure out how to be resilient and then deal with the problem. And so, I think that you're doing tabletop exercises and those often are something you can get outside assistance from. If you've got a good fiber insurance policy, your broker will set those up for you and you can tell them, I need to understand what happens if our biggest revenue pipeline goes, what do we do? That's what we want a tabletop this time, but those are important things to do.
And then an insurance is possible, but you need to know what it covers and what it doesn't cover. And with mentions, it may not pick up any revenue that you lose in the event of an outage.
Kip Boyle: Yeah. And I think CISOs really struggle with this as well, right? And I see this all the time where they're only somewhat involved in the procurement of a cyber insurance policy. And then they often don't take the time to actually read the policy and integrate the services that come with that policy into their incident response plans. And I put it in the same bucket as, well, this is like a contractual you vehicle for managing cyber risk. But a lot of us are like, yeah, that's just too weird. I'm just going to let somebody else deal with that, which is an awful reaction because so much of the job now I think is about doing things through contracts. That's just the way things have gone.
And certainly with AI, I think that's just going to exacerbate the situation because very few of us are going to run our own AI, and yet it's really going to affect our risk profiles. Well anyway, so the regulatory landscape is really starting to catch up with this reality. What are you seeing, Dan?
Dan Bowden: I actually used to be skeptical. Different regulations that came out, they were more of a CYA for the regulator in a compliance sense, where now it feels like they are becoming more driven towards good business resilience and cybersecurity resilience and observe what happens with the UK. There's a new operational resilience effort underway there, where they ask you to identify your important business systems, assure that you're doing adequate testing to understand the impact those were to go away. And then DORA and the EU front is the same and even now has the reporting requirements.
And so, if your business is offline, you're going to be offline for 24 hours, or maybe you're downstream from a provider that you rely on something that you've got to understand, how do you recover from it? And then you're required to report what happened, why it happened, and what you're trying to do about it. So, they are becoming, I think, more, I like the direction. It feels like it's becoming more aligned with business resilience and not just necessarily a list of things to comply with. They seem like a good idea.
Kip Boyle: Right. Checkbox security. Jake, are you helping anybody with the UK resilience requirements or DORA?
Jake Bernstein: First of all, I just wanted to spell it out. DORA is the Digital Operational Resilience Act. Just to make it clear for folks, it's in the EU.
Kip Boyle: Swiper, no swiping.
Jake Bernstein: Swiper, no swiping. That's exactly what I think every single time I hear someone say DORA, just probably not what they intended. As Dan said, DORA is comprehensive. I don't know how effective it will be. I just read a really interesting article or a white paper honestly on... we don't really even have a good framework for measuring the effectiveness of GDPR, and people are already talking about a simplification of it. I think that in some ways, the EU is experiencing the pain caused by its, in my opinion, over-regulation, total opinion of my own, just to be clear and the economic consequences of that.
But it does seem premature to declare GDPR or any of these other frameworks. And there have been quite a few Digital Markets Act, Digital Services Act, DORA, the obviously GDPR E-Privacy Directive, which is supposed to become the E-Privacy Regulation, but it hasn't happened yet for almost a decade at this point. So, I think that while these things are important and can help in the US, what do we have? Well, we have CIRCIA, and I'm not even going to try to remember what that stands for, but it's something about critical infrastructure reporting, cyber risks, interruptions stop...
Kip Boyle: We did do a two-part episode on that.
Jake Bernstein: We did. I can never remember what CERCIA stands for
Kip Boyle: Or even exactly how to say it. That was part of the episode. How do we say this thing?
Jake Bernstein: Yes. So, Dan, what about in the US? I mean, Kip and I are well on record as just loving NIST.
Kip Boyle: Yeah, the cybersecurity framework.
Jake Bernstein: One cybersecurity framework and the 2.0. What are you seeing here in the US with... I mean no one's going to mistake NIST, I should say the NIST framework because I actually hate it when people just say, are you compliant with NIST? Well, that makes no sense. NIST is an agency. It does lots of stuff, right? In context, that usually means the cybersecurity framework, but they're not laws, they're not even regulations or rules. I mean, I suppose you could call them best practices. I mean maybe even elevate them above best practice to some degree, but they're no DORA.
Kip Boyle: Right.
Dan Bowden: Yeah, it's a good point. I think what it is, it's a good step for organizations into where it prompts for identifying who your key suppliers are, doing risk assessments, understanding what kind of supply chain management opportunities that you have. So, I think it's improved a lot. The challenge for everyone, especially if you're in a large organization, is you may have hundreds or thousands of suppliers. And so, there will always be that initial, whatever the new benchmark is that you're trying to use to manage your vendors and suppliers.
How do you get from zero, get the first one in through number 100 or 1000th in time enough base doing good, consistent follow-ups which then drives you to have to prioritize? Who are the most important ones? Let's do those first. And maybe those are done annually and maybe the others are done onboarding and contract renewal, and you have to make some decisions like that.
Jake Bernstein: God, I mean, doesn't it just seem horribly inefficient the way that we are trying to make this work? I mean, first of all, it really doesn't make any sense to expect every customer to perform their own audits of a business in some ways. I know we want responsibility and those things are important, but people ask me all the time, "Oh, do we really need to include these audit clauses? Because frankly, we're never going to use them. We're never going to audit anybody." And they're just being honest and pragmatic about it. And of course, the difficulty is that the second anything bad happens, it's like, "Well, did you do an audit?" "Well, I mean, no, I didn't." "Well then, why did you have it in there?"
And I mean, we're facing a real practicality problem with third-party risk management and it's very, very current to talk about TPRM and having a third-party risk management program. But what does it actually do? And I think this point is huge. I mean, Kip, you and I have a mutual client and that mutual client's, like the best I can do is basically send the same Excel-based questionnaire and get them back, which is also ridiculous because now in order to do business as a vendor, you're like, "Why do I have to fill out basically one of three?" And there's really not that many more that are all that common versions of this crazy long questionnaire for every customer.
I mean, are they even looking at it? Sometimes yes, sometimes no. This whole area is a mess.
Kip Boyle: I've both sent those questionnaires out on behalf of customers. I've responded to questionnaires being sent out on behalf of customers.
Jake Bernstein: By the way, if you guys didn't know this, your astrological sign has probably shifted. I used to be a Gemini, but it turns out that these signs based on when you were born over the last 2000 years, the stars have literally moved. They've shifted. So, apparently now I'm a Taurus, which anyway, why does this matter? It's because I feel I live that Gemini two-face concept, right? I will switch between the vendor and the buyer on a dime, because that's my job and I have to do that. But it's hard not to feel ridiculous at times because I see you were saying, Kip, we see both sides of this coin. And I mean it's just not efficient and I don't know that it's really...
Kip Boyle: But it's a struggle because I rack my brains. I'm like, there's got to be a better way, and I haven't come up with one. But Dan, please give us your perspective on this.
Jake Bernstein: Yeah. Please save us from this.
Dan Bowden: Oh, you're hoping have the silver bullet that...
Kip Boyle: Everybody wants you to have silver bullet.
Jake Bernstein: Yeah. Dan, that's why you were invited as a guest. If you don't have the answer, let us know now.
Dan Bowden: I was shooting for pretty good, right?
Jake Bernstein: Yeah, yeah, that's true.
Dan Bowden: This is a tough one to even hit pretty bad. The end of the day and I agree of everything you said about the questionnaire. I'm the same boat in looking both directions on answering and asking. But I think at the end of the day, it's about demonstrating to our customer, this is how we continue business. This is what you'll expect. If you can predict what they should expect when you're having an issue, I think that's a great thing for a customer to understand. But it's hard to get from organizations. Tell me what happens when your service is offline. And all we generally ask them is tell me you're never going to be offline. We want to hear, but we would be good I think in the future to have the conversation.
Okay, let's pretend maybe you're going to say there's a one in a million chance you go down. But if it goes down, what's it like? Tell me, what would you propose I do? What measure should I take, protect my business while you're down? And I think that's something that we should try to graduate to as well on the resilient side.
Jake Bernstein: Now, I'm going to just go way off script for a second at least. I think I'm going to go way off script. I haven't scrolled all the way down. Now, Marsh is one of the largest insurance brokers, unless I'm confused, and I guess this is hypothetical really, but do you think maybe a better solution long-term is for each company to just buy its own you basically its own third party resiliency, business interruption type insurance policy and your premium is going to be based upon each... Underwriters are good at this stuff, right?
Underwriters have all the data, or they will get all the data and maybe they can look at your third party risk and all of your software, all the SaaS, all the cloud, and actually come up with something that is reasonable here because we try to get... Think about just a cute little project management for a while. There were so many of them settled down a little bit, but just think back to the day when there were just dozens and dozens of these little project management SaaS companies out there, right? Every company was surviving without these things for centuries if you want to go back far enough. So, you could look at them and say, "Well, that's not a business critical infrastructure type of program there."
So, the underwriter might look at that and be like, "Eh, if it goes down, you ought to still be able to keep going." But aside from going through almost case by case, I don't know how else to do it. And there's this concept that I'm not sure we actually mentioned about cascading and cascade failures. I mean, think of it too, that little SaaS project management company itself is running on infrastructure as a service, or platform as a service. And it is not difficult to build up a seven layer dip of cascade failure possibility here. And I just think based on this, SLAs are not the answer, unless maybe the SLA is at the back end. But even then, think about what happened with CrowdStrike, right?
First of all, their contracts were protective of them in most cases. But if you're a big back end infrastructure company and you go completely offline, arguably not even the Microsoft Googles and Amazons could pay out the amount of money, I mean to really reimburse, right? The amount of money...
Kip Boyle: It's uninsurable.
Jake Bernstein: It's uninsurable, right?
Kip Boyle: Exposure.
Jake Bernstein: It's not possible. And I mean, I guess we might, I hate to say this, but the concept of utility might need to be used. Because if you think about it, when the power goes out, you don't get to sue the power company for power outage and your business loss, do you? As far as I know, you don't. And I know part of me is if I'm a big infrastructure as a service company, I might be pushing for that. I don't know. What do you think? I mean, I just totally...
Dan Bowden: No, I think you asked the question. I think you also answered it, but that's the truth, right? How do you insure it? Because let's just say you even wanted to try to have it insured. I'm sure someone could put some quantifying monetary numbers associated with an outage, but then a good underwriter broker is going to want to understand, well, where do you get all of your underlying abilities to provide that service? Because when you go to the hospital and you've fallen and broken your arm, but you get that little question, the insurer wants to ask, did somebody do this to you? Was this somebody else's fault?
Kip Boyle: Did it happen on the job, right?
Jake Bernstein: Yeah.
Dan Bowden: And it's a really simple analogy, but I think in these cases, it's going to be the same thing. Well, before we repay all of your losses, we want to know whose fault this was, and you're going to get in this circular echelon of lawsuit that may never get uncooked.
Jake Bernstein: One of my favorite...
Dan Bowden: Was it Delta, Microsoft, CrowdStrike that ruined the Spider-man mean pointing thing.
Jake Bernstein: Yes, yes.
Dan Bowden: And so, I think that's the challenge with it.
Jake Bernstein: And one of my favorite legal words, subrogation is what...
Kip Boyle: That's the word I was trying to remember.
Jake Bernstein: Is what happens all the time. That's an insurance industry specific term.
Kip Boyle: Yeah. It's a reinsurance for them, right? A little tactical insurance in a way.
Jake Bernstein: Well, no, reinsurance is different. Reinsurance...
Kip Boyle: Oh, no, no, no, I know it is, but it's just like reinsurance is how other people give you the insurance company money back on claims you've paid and subrogation, that's another form of an insurance company getting money from somebody else for claims that they've paid, right?
Jake Bernstein: Yeah. Usually, it's insurance company A getting money from insurance company B, and, yeah, that's essentially what that is.
Kip Boyle: Right. But we're just moving money around trying to make our loss ratios looked good.
Jake Bernstein: So, we are, right? No, that's actually really important, Kip, is we are just moving money around, and I think to some degree we're going to hit this point where I was just thinking to myself, I've lost power way more and way more often and for much longer than I lose any specific SaaS platform, right? Realistically, at least where I live. We had that big giant storm, I guess it was, yeah, almost the beginning of 2025 here in the Seattle area. We had no power for almost a week. And I've never known and I mean, think of the biggest downtime that makes the news, it's never that long. I don't even know if I can remember anything big, being down for a full day. Usually, it's a couple hours.
And this is such an interesting, timely and intractable problem, this whole concept of third-party risk management, third-party risk allocation insurance. I mean, I think right now, I think there are some best practices, Dan, and do you agree that it starts with your procurement team? If you're a big enough enterprise to have a procurement team, you got to get legal involved. You've got to understand that every standard SaaS contract in particular doesn't really provide adequate protection. It is worth understanding the difference between infrastructure as a service platform as a service and software as a service, and then whatever else people want to sell you as service these days.
Kip Boyle: And then also the function that's performing. Is it helping with sales? Is it helping with order fulfillments, right? Because...
Jake Bernstein: Well, and scrolling back up to a section of our pseudo script that I think I want to...
Kip Boyle: It's a pseudo script for you, Pal.
Jake Bernstein: Yeah. Well, and just to ask Dan, I think one thing that let's not let ourselves off the hook, the purchasers of these services, and it's really good point here, which is rather than just willy-nilly outsource and buy and have all this just creating all this massive TPRM, maybe start with your critical business processes and figure that out. What do you say? What's your advice, Dan, on that front? Yes, the contract is important, yes SLAs can be useful in insurance matters, but what about going back to the basics of what are your...
Dan Bowden: Governance is a really big deal, just who oversees procurement of whatever? Everything from staplers to the software as a service. And I think if we establish an effective governance where everyone understands these are our expectations and standards all the way through, it also will capture those shadow IT people paying for different services with the corporate credit card, things like that, where you're now funneling everything through a highly effective governance process. Then you can have conversations about contractual obligations, things that you might call a restrictive clause in a contract.
You can capture all of those and establish standards for if you want to have liability discussions or limits. But that's, I think where it starts is just getting that effective governance and telling everybody, there's one way to buy things here, one way to acquire things here. And then you've got all the way from whoever's in charge of sourcing, all the way down to the security and tech teams on standardization and cybersecurity.
Jake Bernstein: Yeah. And is there any real substitute for going through each, for identifying your critical business processes, and then for each dependency, asking yourself, what happens if this fails? How long can we survive without it? What is our backup plan? I mean I guess that's part of internal risk management, right? I mean, honestly, don't think you can do third party risk management without doing that first.
Dan Bowden: No. And if you can't do it for real intent, you pretend, and film teams have figured this out, like payroll goes down. Well, the CFO will call the bank and cut all the same paychecks we did last time, and there's going to be some level of error in there, and maybe some things that were missed, but at least your team is going to stay and work through whatever the problem is while it's happening, even though the payroll system may be offered an extended period, but that's a simple scenario to describe, but email, some companies only communicate with their clients over email. Do you have your client's phone number? Because some of us don't keep phone numbers anywhere anymore, our mobile phone.
And if we don't have our client's numbers there, how do you get a hold of them? And it's those simple conversations. How will you do even the simple things if email's offline, et cetera, what do you do? But you have to actually test it. Yeah.
Kip Boyle: Well, this has been an awesome conversation. We are coming up on time. Dan, as we wrap up here, we've covered so much, but is there anything that you wanted to say or do you have any final thoughts for any of our listeners who are struggling with this challenge of third-party risk management? Any final thoughts?
Dan Bowden: I'm not going to let anyone off the hook, but this is hard for everyone. And I think that the key thing is to identify those, even if you just identify, if you have a hundred vendors, but you know which five are the most important, start with them. Put them on the radar with your leadership. Let them know we're administering some standards for review and expectations. And whenever we replace one of these, the new vendor is going to be subject to a higher bar and then start to build on it based on risk. If you find out, well, five wasn't enough, we actually have 10 highly risky vendors. Add those and move so that you know what those critical business functions are and what supports them.
Because some people forget and they forget that maybe in healthcare, it's really interesting working. There are things that it may not seem like an important system, but maybe it affects patient safety, or maybe there's a security system. They're like, "Oh, well, fails open." Well, no, actually it fails closed and locks down all of the medication cabinets. And so, I think that the people need to play that out in your mind. If that fails and we can't get the medications, is that a big deal? And then...
Jake Bernstein: I mean according to medical TV dramas where they start taking crowbars to those medication dispensing machines, I imagine it is...
Kip Boyle: Did you guys watch the same episode that I didn't see?
Jake Bernstein: It is a problem.
Dan Bowden: And so, that's the thing. Start at this stuff that you know is a challenge. And then start asking questions. Well, what if and what if? That's where people start.
Kip Boyle: So, Dan, the way that I would characterize what you said, I don't disagree, but I want people to understand that you're saying top down, right? You're saying start at the top, figure out what's most important, and then dive into the details because I think our legacy as a profession is to do everything from the bottom up, is to start with the ones and zeros and then go up. It makes less sense to do that as every day goes by, especially in this world of contract, of trying to manage cyber risk through contracts.
Well, thank you, Dan, for being here. Really appreciate it. And I'm going to wrap up this episode of the Cyber Risk Management Podcast by summarizing that today, we explored third-party risk management and resilience with our friend Dan Bowden from the Marsh Mclennan organization. We learned about the realities of vendor outages, what actually is in those SaaS contracts and what's not. We've looked at some new regulations and how those are actually changing expectations around operational resilience in a way that we were concerned. Maybe it wouldn't. Dan, thanks for being here. All right, 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 cybersecurity 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.
Sign up to receive email updates
Enter your name and email address below and I'll send you periodic updates about the podcast.
YOUR 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.