Die meisten Organisationen im Gesundheitswesen verfügen über einen Plan für Cyberkrisen. Nur wenige verfügen jedoch über einen Plan, der sich bewährt, wenn ein Angriff den Betrieb in großem Umfang lahmlegt.
Die Lücke liegt häufig in der Identitätsinfrastruktur, jener grundlegenden Ebene, die den Zugriff auf jedes kritische System regelt. Wird diese Ebene bei der Krisenplanung übersehen, kommen die Wiederherstellungsmaßnahmen ins Stocken. Die Gesundheitsversorgung leidet darunter. Und Organisationen, die glaubten, gut vorbereitet zu sein, müssen feststellen, dass dem nicht so ist.
In dieser Fortbildungsveranstaltung stützt sich Courtney Guss, AVP für Krisenmanagement bei Semperis, auf weltweite Forschungsergebnisse und direkte Erfahrungen im Bereich „ incident response “, um zu untersuchen, wie Organisationen im Gesundheitswesen mit dem Druck lebensbedrohlicher Störungen umgehen müssen, wo Cyber-Notfallpläne im Gesundheitswesen versagen und was erforderlich ist, um echte operative Resilienz aufzubauen.
Was Sie lernen werden:
- Warum viele etablierte Notfallpläne bei tatsächlichen Störungen versagen
- Wie der Einsatz von KI identitätsbezogene Sicherheitslücken vergrößert
- Warum die vorherige Festlegung klarer Rollen und Entscheidungsbefugnisse unerlässlich ist
- Was effektive Tabletop-Übungen für Sie leisten sollten
- Warum es unerlässlich ist, umsetzbare und nicht nur auf Prüfungen ausgerichtete Reaktionspläne zu erstellen
Sehen Sie sich das Video jetzt an und beginnen Sie damit, von der Planung für den Idealfall zur Vorbereitung auf den schlimmsten Fall überzugehen.
Right. Well, we will go ahead and get started as people trickle in. Thank you guys so much for joining us this afternoon. I’m excited to talk a little bit about cyber crisis in health care today, get some feedback from the group, and really understand what matters to all of you. For those of you that don’t know me, my name is Courtney Guss, and I’m the AVP of Crisis Management here at Semperis, and I am going to walk through a little bit about my experience in the cyber crisis healthcare space, as well as things we’re learning in the age of AI and how things unfold. If you have any questions, please feel free to throw them in the chat. I’m not sure if you have the ability to unmute or not, but please feel free to throw those in the chat, and I will answer those either during the session or at the end. There is a question in the chat right now around CPE credits, and I’m not 100% sure on that. We probably have to check with HISAC on that one. For those of you I haven’t worked with, I am based in Dallas, Texas, and I lead up our cyber crisis management practice at Semperis, where we’re really working toward managing severe incidents or crises in kind of an out of band tooling perspective. So my background is in emergency preparedness and disaster recovery. I actually spent twelve years in the insurance sector working in the National Flood Insurance Program, so boots on the ground emergency preparedness and disaster recovery. And I’ve been in the cybersecurity space for about ten years now, so business operation, business disruption, especially in the healthcare space, has been something I’ve been working on for quite some time and excited to walk you guys through this. For those of you that work in healthcare, a disruption like this isn’t something that’s new for you, right? So in the morning or in the afternoon, the evening, whatever time of day, you start to feel or notice that things aren’t working the way they’re supposed to. It says here, suspicious activity detected. You may not know that on the hospital floor. All you know are machines aren’t working, or you’re unable to log into your laptops, you can’t badge through systems, and it starts to create disruption throughout the organization. But it takes people a while to figure out what’s going on, what’s not working. Is this just an IT hiccup or an outage? Do we need to restart a machine? Or is this something more significant? And that escalation becomes really important as it starts to spread across the organization, because critical decisions around downtime procedures or lockdowns have to start to happen as soon as we realize what’s going on. For those of you that have been watching the news, there’s been a pretty significant outage with the University Hospital group up in Ohio actually from that area originally, and it took down patient facing systems like their MyChart system, and so it’s one of those things where it may not always impact internal operations, but your patients may feel the impact immediately. And what I think is so important about crisis management, whether it’s healthcare or not, is that having a plan isn’t the same as being prepared. Having a plan in place, having a plan on paper is very important, but practicing that plan, understanding what’s important to the business, what we’re trying to protect, but also having a plan that’s usable and easy to run through are all the things that make the difference when it comes to actually being and feeling prepared. So what we find in our Semperis annual survey is that most of our customers have a plan. Most organizations have some kind of a plan in place. It doesn’t change whether or not you’re going to be impacted or targeted, and it doesn’t change how prepared you actually are. Another thing we think about when we build plans are making sure we hit every regulatory or reporting milestone in that plan. So these plans end up being very, very long and cumbersome, and so how do we take some of that audit or compliance functionality out? Keeping critical things in, but making it far more actionable and faster for us to execute on. Because when you think about crisis management, 80% of crisis management is the same from industry to industry. There’s planning and preparation, there’s practice, there’s having critical documents, there’s having materials ready, having the right people in place. That’s not going to be different whether I’m talking about healthcare, or manufacturing, or retail, or financial services. But what’s so different about the healthcare industry are the people, the disruption. There’s no room for downtime. There’s no room for disruption when you’re talking about human care, patient care, or even operations for the hospital or healthcare facility. And so although we have a lot of the same principles across the industries, the stakes are different in the healthcare space. Priorities are obviously focused on human or patient care or hospital operations. Authority can be very different when you’re talking about clinical versus operational leadership. Decisions and timely decisions are very, very different when you’re talking about patient care again, and that coordinated execution across departments can become far more challenging. So although the concepts of crisis management are the same, the execution in the healthcare space is very unique. So what changes? What are those differences when you think about healthcare? Some of the things that might be weakness or a challenge to overcome are also your greatest strengths. When you think about disruption in the healthcare space, it’s hard. You feel it immediately, especially if technology goes down. We’re so heavily reliant on patient care technology, but hospitals and healthcare systems tend to have a very strong safety culture. Safety is woven into what we do every day, and so thankfully, the way we operate around patients and in these hospital or healthcare operations is heavily driven by safety measures and safety policies and processes. So we’re ready for those disruptions, probably more so than a lot of other industries. Time is probably one of our bigger challenges. We don’t have a lot of tolerance for downtime or disruption. It’s hard when you have people waiting on you and life saving care could be depending on you, and so working under pressure and the time constraint is probably one of the bigger challenges in the healthcare space, whereas a lot of other industries can tolerate some of those downtimes or disruptions, fluctuations. The systems piece is really interesting, and I think this is where innate tribal knowledge or industry knowledge becomes critical. We as a healthcare system have become more and more reliant on technology, just like every other industry. But when you have new clinical staff or operational staff entering the workforce, and they’ve never not taken care of a patient without the help of an iPad or a patient record keeping system. They often don’t necessarily know how to manage procedural or downtime procedures in a paper format. And so thinking about how we’re training or onboarding or enabling teams are super important, because if they’ve never worked offline, they’re going to struggle and these disruptions become amplified. Structure is really interesting. In healthcare, we’re very structured. We’ve got teams that carry out very specific tasks that can really help in these situations, but that can also hinder us. So how do these teams work together and share information becomes super important, and that’s where that practice comes in. And then the recovery piece. This can be drawn out a bit in healthcare, so it’s not just getting the system back online, but it’s getting all of our patient information updated, getting everybody back where they need to be, picking up for any lost care or missed appointments that may have happened. I worked with a hospital group up in the Northeast, and they were down for several weeks, and a lot of those surgeries, anything that was not mission critical, had to be rescheduled, and so it has a bit of a ripple effect. And so recovery, I think, takes a bit longer in the healthcare space. And when these systems are unavailable, like we said, if you’re not used to working with patient care in a paper format, it can really slow things down, and it could require, depending on regulation, an extra set of eyes. So not only do you now need additional paper policies or processes or prepared downtime procedures, but you might need additional support staff. You might have to call in help from other facilities or other resources, but you’re going have to work through things like patient intake and patient identification. How do we do that manually? How do we make sure we don’t duplicate efforts there? How do we manage medications? That’s an area where oftentimes you have to have a second set of eyes. Same with diagnostic results. How are we doing imaging if we’re unable to manage our technology? Are we scheduling transfers? Are we managing our schedule? Are we moving people to other facilities? And then how do we communicate internally? And these all become challenges across the organization when you’re out of your technology or outside of your normal technology operations, and you’ve got this significant disruption. And some of the areas that we can focus on making quick changes or really effective changes that can help us move the needle for the next time we have a disruption. Start to make plans that are built for action, not audit. I think that’s one of the things that we talk about a lot. It’s really important to make sure we cover all of our regulatory and compliance bases. We make sure we meet all of our reporting requirements. But if we’re trying to maintain patient care or operations in a mission critical moment, we want to make sure that our plans and our decisions are meant for action. Understanding what matters to the business and keeping all of our decisions aligned with that helps make sure that we meet those requirements. Now, we will have to go back and make sure we’ve met all of our compliance and audit requirements later, and there may be things that we miss, but as long as we’re making defensible decisions throughout that process, those are conversations we can have meaningfully after the event. Semperis is an identity company, and although clinical operations may not always understand what that means exactly, but how everybody authenticates and gets into the systems and tools and technology we use is very important, not only for security, but on the back end for accessibility. So we want to make sure that that’s an incorporated piece in your risk matrix so that people understand the threat landscape in the identity space, but then also how that ties to potential disruptions. Authority. This is probably one of the areas I see crisis management breakdown in an incident response process, first and foremost. Lack of authority or lack of clearly assigned authority. You could ask someone to do something, or it could be in a playbook that it’s my responsibility to carry out an action. But if I don’t feel like I have the authority to make that decision, I’m going to freeze, and you’re going get that analysis paralysis. And I’m going to start running around trying to figure out who has the authority to make that decision so that I can move on. So make sure that as you create these fast action packed playbooks, things that are quick and easy to run through, that you’re calling out who has the authority to say yes or no to that decision point. And then make sure that downtime and clinical continuity are really built into these plans. We want to make sure that critical operations are prioritized, and we’re working through how we maintain those, and anything not mission critical, we have a communication plan to manage that as well. And then we want to make sure that any restoration we do is trusted. We see this often in the cybersecurity space. We’ll restore systems, the threat actor’s still in there, and they just take us right back offline. So if your team’s working to restore systems and you’re frustrated with how long it’s taking, or your business leadership is harping on you, they’re frustrated with how long it’s taking, just remember that getting it right the first time will probably save you time in the long run, as well as additional disruptions. But all of that becomes really important communication for your Incident Response Team as they’re working through that situation. Please, if you have questions, throw them in the chat. Happy to hop off and answer those. So one thing we talk a lot about, we talked about building plans that are meant for action and not for audit. But we also need to think about how we build plans that aren’t designed to be played out in ideal state or for our calmest versions of ourselves. When we run tabletop exercises, or really any kind of disruption or downtime exercise, we’re typically doing it in what I refer to as ideal state. We’ve got Wi Fi, the power’s on, everyone’s rested, they’ve had coffee, they have their systems, everything’s running, and we even have some of our cheat sheets. We knew this day was coming. That unfortunately is not how these situations tend to play out. We may not have Wi Fi, we may not have access to our normal downtime procedures and documentation, We may not even be able to contact each other. So how do we manage these situations or build plans and access plans on that worst day? Take that 100 line item playbook, trim it down to 10 or 15 lines that matter for those first four to six hours. Make sure that you’ve got critical contact information. One of the things we overlook most often are phone books. They’re on our normal systems, they’re on our phones, but they’re not complete, and sometimes they’re not even accessible. So make sure we’ve got that downtime documentation and tooling available. Make sure those documents are easy to run through and they’re action oriented, and really start to siphon that tribal knowledge from those veteran team members, so that you understand how to run through paper procedures. Do we have a paper printout of our prescription? Do we have an example of what a good patient file looks like, or a patient intake census form? All of these templates help us execute much, much faster, and reduce that analysis paralysis stage. And again, it all comes back to how quickly we can respond. Recovery at the end of the day is how fast I can get back on my feet after taking a punch, and that immediately. Now, depending on which cyber regulator you talk to, the clock starts at a different time, so that’s its own challenge. But just remember, we want to make sure that we’re recovering and we’re responding quickly and decisively. Also something to consider is the onset of AI, and I’d be remiss if I didn’t mention it here today. I know we’re probably all sick of talking about it. But what AI does is speed up that attack path. It’s going to speed up how quickly that attack escalates across the business. Our response has to speed up in the same way, whether that’s slimming down our response and recovery plan, making decisive, defensible decisions, making sure we’re aligning to business priorities, we’re going to have to get better at reacting much faster. And identity for us at Semperis is super important. It’s the critical layer under all of this. So if you have somebody talking to you internally about identity security or the importance of identity across the business, I’d be remiss if we didn’t talk about it today. This is the core foundation of your cybersecurity systems, your operating systems. It’s super important for everything that you authenticate into within the hospital or your healthcare system. And if you ever say, I can’t authenticate into my laptop, I can’t sign in, we’ve heard that, I can’t get logged into this system, there’s something going on with your identity system. And it’s not what we talk about a lot in the cybersecurity space, but it’s in every single system we have. So it’s super important to make sure that it gets recognition from a risk perspective so that we’re making sure we have plans for when it goes down. You want to make sure that your disruption plans account for an outage caused by an identity situation, because if you can’t log into anything, if you can’t get into your critical systems, you have to have backups for everything from ways to communicate with each other, ways to pull critical documentation, and ways to orchestrate your response and recovery. So it’s basically taking everything offline and saying, Okay, what do we do now? And I think what’s been interesting in the news recently is that disruptions in the healthcare space don’t necessarily have to be because our patient record systems go offline. I think oftentimes when we run scenarios, when we run and we look at cybersecurity risk, we think about taking these major systems like an EPIC offline. What would happen if it went offline? And that would be a significant business impact. But I think it’s important to remember that the impact or disruption can be felt even if that system is not offline. It could be a significant power outage or weather event. It could be everything from a strike or a patient care issue. It could be other systems go offline, and it doesn’t even impact your patient care system, but you can’t even get to it. So I think it’s important to remember that although these systems, these patient care systems, do kind of become the backbone of our operation, there’s lots of other really significant disruptions that we’re seeing across the world that aren’t necessarily tied to just that system being offline. So when you think about prioritizing response and recovery, I know I said earlier, sometimes we get frustrated on the business side when we feel like the IT recovery isn’t happening as fast as we want it to. But it is really important to make sure that those critical foundation layers are restored first and restored cleanly, that we can trust that we’re the only ones in there, and that they’re working the way that they’re supposed to be. So making sure that the communication from that IT recovery group and that IR recovery group and the business remain open is super important. How long can I expect to be down? Is there a plan for which order we’re going to bring systems back online? Have we all agreed on that order? We should try to agree on those things beforehand, just food for thought. But making sure that those things are communicated so that we’re setting the right expectations with our teams, and we’re setting the right expectations with our patients. If we know that patient scheduling systems or outpatient systems are going to be one of the later things restored, we need to start managing communications to those patient groups differently so that we’re setting the right expectations. We can really plan ahead based on that response and recovery prioritization on how we manage how long our internal downtime procedures have to run, as well as how we start to communicate with our stakeholders. And so really thinking outside the box here in terms of I’ve got this plan one step ahead really changes your response and recovery game. So how do we really pull this authority piece together when you’ve got patient care at the other end of that decision? It’s really different. It’s different than kind of your standard revenue stream, right? You’ve got health and human safety, you’ve got people’s livelihoods, you’ve got people sitting at the other end of this very big decision. One of the things that I hear from hospital groups all the time is, We weren’t sure when to go straight to downtime procedures. We weren’t sure exactly when to escalate things to that point or start diverting patient care. These clinical decisions are really something you’d ideally want to iron out during your practice exercises, meaning how long are we willing to be offline or tolerate downtime before we need to start coming up with alternative action plans, rerouting people, delaying patient care? How long can we operate under standard downtime procedures with the materials we have here, or do we have enough staff? And then who has the authority to make that decision? In other industries, it’s the same as cutting off the internet or cutting off all networks. These are critical decisions that impact a large group of people, and you want to understand what those top decisions are and who owns them, ideally beforehand. If not, you’re really going to have to have your senior management on deck to answer some of these critical questions, especially in the first twenty four to forty eight hours as you’re trying to manage this information. So how do we manage all of these pieces and actually run through kind of a coordinated cyber response and recovery. How do we connect this to the organization? And I think that’s probably one of the biggest areas where we struggle as groups. How do we connect our IT and IR cyber teams with our clinical leadership teams, and make sure that everyone is aligned on what matters, and everyone’s driving to the same priorities. And that can be really challenging. I think it’s important to share a common language. What matters to the business? If these systems go down, what impact does that have on our daily operations, on our patient, on our revenue streams? Those are conversations where we take the technology out and we talk about the impact, And then you start to bring together or bridge the gap around what matters to both of us, and I think that’s super important. I think the other piece here, we’ve got it called out on the left, are the teams that should be part of this process. Obviously teams like emergency management and incident command, but patient safety and culture is very important, as well as clinical handoffs. Do you have escalation paths or points of handoff predefined as best that you can? There’s going to be a lot of nuance in these scenarios or situations, so just make sure that you know who the right experts are to ask these questions to. If you don’t have it ironed out ahead of time, you want to make sure that they’re available during the actual response and recovery time. Now, there is obviously a trade off there. You don’t need 100 people in the room to make decisions, or you’ll never make a decision, but you do want to know who the critical decision makers are across key parts of your organization. Well, there’s a question in the chat. What are the critical identity components that should be written in an incident response playbook which can help in a crisis situation? That’s a great question. So when we look at Active Directory Recovery or Entra Recovery or any of the other identity systems recovery, one of the first things that we look to understand is where the disruption or compromise started. If we believe it’s a cyber attack, then we need to ensure that we’ve eradicated that threat before we restore any systems into a trusted state. And so we have some information I’m happy to share after this call in terms of what those steps are, and there’s a few things from a forensics perspective and an analysis perspective right out of the gate that can really help save you time down the road. We obviously also have a tool that helps you recover Active Directory in a much shorter period of time, but really understanding what critical applications are tied to that identity as well is super important, because we want to make sure that even after you’ve got the identities restored in a trusted state, that you then are working through the applications that are mission critical as well. So I’m happy to share our identity recovery playbook with the group afterwards. We can send it out to HISAC for all of you. You can also find it on our Semperis website. So great question, but there are definitely some critical steps or things you want to think about in that first couple of hours that help not only with cyber law or legal issues afterwards, but the recovery. And you’re welcome! Think about how we can really change the game on managing or building downtime procedures, and a great way to do this is to take an incident you’ve had internally or maybe one of your peers have had and reverse engineer it. If we could do this incident all over again, what do we wish we had our fingers on? What information would have made a difference? What template would have changed the game? What document would have helped me execute faster or align the teams faster? And build out your downtime procedures from there. You don’t have to recreate everything, and you don’t have to solve every problem, but you want to make sure they’re accessible first and foremost. You want to get them into an out of band system, so when your normal systems are down, you can have access to it. You want to make sure that you’ve got both your IT and IR, but also your clinical workflows in there. What’s mission critical for those critical operations? Communication is super important, so how do we communicate internally as well as externally to our stakeholders? This becomes great. Also given in the healthcare space, our tremendous supply chain, who are our mission critical vendors? Pharmacies, suppliers, medical devices, etcetera, that are the game changers for us when we’re looking for support. And then when we’re thinking about staffing, this has been such an interesting space in the healthcare world. When we’re in significant downtime, there are specific roles, depending on where you’re located, that require a second set of eyes, Oftentimes distributing medications or prescriptions or reading imaging, where you have to have a second set of eyes if normal technology is offline. Think about those staffing requirements ahead of time and work with your peers as you practice to see how you can share staffing in critical situations as well. And the other thing too is oftentimes our downtime procedures assume we’ll only be offline for six to eight hours, or maybe a day. Some of these downtimes go on for weeks, unfortunately, especially if we’re not prepared or we don’t know what’s happening. So really think about what extended disruption looks like for you. If it’s after four or five days and you can no longer bring on more patients because you don’t have the resources or capacity, what is that next plan B or plan C to start rerouting patients to other facilities, and have you had any of that planned out ahead of time? Remember that restoring systems is not the same as recovery, and like I mentioned before, recovery tends to lag in the healthcare space because we’ve got to now kind of recalibrate all of the patient information and all of the work that we’ve done offline in paper format and manually back into our patient care systems. This goes all the way down to billing, so we’ve got to make sure that as we’re running through paper for patients and paper charts for prescriptions and all the other things that we do, we want to make sure that all of that ties back to billing, and so that all takes time after the event. So just remember that just because our systems are up and running does not mean that our facility is going to be operating at full recovery or full normal capacity the way it would have been before. Also think about those things as you’re building out your downtime procedures. If there is a billing checklist that you can create and add to that good patient file example for your downtime procedures, those are all really important things that can help save you time down the road. And practice, practice, practice. One of those things that we talk a lot about are tabletops, but we feel cumbersome to get everybody in the room once a year, take everybody offline. It can be very time consuming, and again we’re kind of practicing in that ideal state, and sometimes we’re not really practicing for scenarios that make sense. So I would challenge the group to think about the types of scenarios you build into your own books and playbooks. I bring it way down to the basics: an outage, so availability, a data breach or a confidentiality issue, and an integrity issue. Something’s up, something’s not right in our systems, data’s impacted. Those are the CIA triad in the cybersecurity space, and a great starting point if you don’t have anything built today. Plan for an outage, plan for a breach, and plan for a system integrity issue. From there, it’s a lot of nuance. That outage impacted X systems or X operations, and that’s where that nuance becomes super important. Also becomes a lot easier to practice, because an outage is an outage when you look at the business, when you think about things being disrupted and out. On the IT side and IR side, that recovery could be slightly different. So we just wanna make sure that we’re we’re managing the number of runbooks and playbooks that we’re building. And with AI, granted it it makes our lives a little bit harder from a cyber responsive recovery perspective because these attacks happen quickly, we’re more vulnerable. But leverage it to our advantage. If we’re behind on getting runbooks or playbooks updated, leverage your AI tool to help you clean those up, streamline them, pull out what matters and is important. Run those runbooks and playbooks up against your regulatory and reporting requirements, and make sure you’re just not missing the most important pieces. And also run those runbooks through and come up with a quick scenario to practice. I challenge us all to move away from six hour tabletops to practicing monthly, but maybe keep it to an hour and start to think about what Plan B looks like and Plan C looks like, because I promise you Plan A will not always work. And then of course here, you know, things like having the authority planned out, understanding your thresholds for patient care impacts, and then who executes and communicates are all super important, often overlooked or fumbled areas in recovery. So if you walk away with anything today, hopefully it’s a couple of quick hitting action items that everyone here can think about. The first is center on what matters. If you all and your leadership teams are aligned with what matters to the business, your North Star, then all the decisions you make during that response and recovery need to align to that business critical North Star. And if they do, they’re defensible. There are things that you can manage and work through. So think about that. Make sure that you have that alignment meeting, and we’re all in agreement on what we care about and what matters. And then from there, who owns the decision and the authority in that situation? Because from there we can really start to execute and make really decisive movements throughout that response and recovery. Make sure that we’re working through the clock, the board, and making sure we’ve got out of band tooling to support us. We have to assume that our systems are either unavailable or we can’t trust them. We may not be the only ones in there, so have a backup plan. How are we getting to critical phone books? How are we getting to critical downtime procedures, and how are we communicating with each other? And then from there, really rethink the way we practice. We don’t need all day tabletop exercises. They’re great, we should keep doing them, but there’s a lot of advantages and value from running small team exercises as well, especially when you’re talking about fast coordination or response and recovery across teams. And so what happens when all this comes together? Well, our patients reap the benefits of us managing a disruption. I always say that resilience, true resilience, is the ability to take a punch and remain standing, or keep walking, keep moving. The goal is that even during our worst day, even during our worst disruption, we’re able to maintain some kind of minimum viable operations. So what does that look like for you? If that’s patient care as minimum viable, then what are the minimum things I need to be successful in that situation? And start training your teams on that. And again, rethink how and when we train our teams. If I’m new and I’m part of that response and recovery plan, if I’m on the patient floor, I should probably be aware of how these things work in the event that there’s a disruption, so I’m not hearing about it for the first time at that time. So think about enablement, think about new hire onboarding, think about ongoing training to make all of this a bit easier. And I have now talked at you guys for about thirty five minutes. Does anyone have any questions or feedback or thoughts, stories they want to share? It’s such an interesting industry, and there’s news every day around new healthcare disruptions and attacks, and so there’s no shortage of examples. I’ll leave it for a second, and I will, I’m happy to share the deck, and I’m happy to share that runbook I mentioned as well with HISAC after the event, if anyone would like to run through that. Questions? I’ll give it another minute. Alright. And it looks like we’ll be able to send some some follow-up emails as well. Oh great question. Is there a shared resource you can recommend? That’s a great question. There are some really phenomenal resources online. I’m happy to share some things with the group, Robert, around streamlining response and recovery plans tied to healthcare, as well as managing or prioritizing critical operations, and some of the information on that reverse tabletop I talked about as well. I can share some best practices on that. I refer back to FEMA and some of the emergency management guidelines and frameworks. I will say, just being forthcoming, a lot of the cybersecurity frameworks don’t directly address the response and recovery piece. So if you look at NIST, you’ve got identify, protect, detect, respond, recover. Or if you look at ISO, the respond and recovery piece or the attributes that we look at are often significantly smaller than the rest of the framework, meaning we spend a lot of time trying to prevent the bad thing from happening. I don’t think we spend enough time and effort and resources in preparing for a real response and recovery. So I will say there is not a true crisis management framework on the market. There are a lot of pieces, you know, BCIDR, there’s some international frameworks, but it’s kind of a combination of cyber, physical, and disaster recovery emergency management combined. So I’ll share some, you know, some information with you guys after the session for sure. Great question. All right. Frameworks of the Department of Health and Human Services are specific. Yeah, so I think there are some great HICS frameworks. There’s some frameworks on the Department of Health and Human Services. The question is, are they good enough for guidance? And I think the answer is yes. I think any of these frameworks are helpful when it comes to guidance or guardrails. I think what’s important is to run those against what matters for your business, and understanding what do these guardrails or frameworks align with what we do and what matter to us, versus what are things that maybe aren’t as relevant to what we do, or things that we could deprioritize. I would caution with any of these frameworks is don’t overcompliance or overframework yourself. Pull out what matters. If we’re in an outage, or if we’re in a breach, or if we’ve got a significant natural disaster, what are the pieces of these frameworks that are useful and that can help us build a plan versus what are the things that we could deprioritize for sure. But thank you. Awesome. I love all the questions. Any other thoughts or questions, feedback? Anybody use anything that they liked or worked or worked well with kind of cross communication across the teams? That’s always an interesting one. All right. Well, if there’s no other thoughts, I’ll kind of slow play it. I will dismiss the group for the afternoon. It has absolutely been a pleasure speaking with all of you. Thank you for the feedback and questions. If you have anything afterwards, please feel free to email me. Tabletop training, where to find it? So I’m going to answer this two ways. The question is tabletop training, where to find it? I think if you’re asking where can you find guidance resources on tabletop training, there’s quite a bit of information online. I know we’ve got some information on our site as well. There’s some best practices around how often and who should be included in tabletops, and I think the healthcare guidance provides some of that as well, but I think it again has to do with the type of scenario you’re planning for and then who should be involved in that. So let me see if I can find some direct links outside of just following up and we can have a conversation on that one too. Tabletops are important because you want to think about them a couple different ways. There’s executive level tabletops, meaning what are the critical decisions my executive leadership are going to have to make in a significant incident? Then there are execution level tabletops, meaning how do I carry out that decision once it’s been made? So if someone gives me something I have to go do, how do I do that? Are there materials or tools that I need? Do I need authority? Does something need approval? So you want to make sure that we’re not only making critical decisions at that level of a tabletop, we want to make sure that the team carrying out those decisions knows how to do that too. We call those drills. So there’s kind of executive level tabletops and drilling. So there’s a couple different ways you can look at that for sure. Drilling would be super important in the healthcare space when you’re thinking about pulling and using downtime procedures as well. Yeah, absolutely. I love all the questions. Thank you. All right, I can’t tell if anyone’s typing or not, so I don’t want to cut anybody off, but I’m happy to hang on for a minute. Thank you guys so much for your time today. I’ll hang on for a couple minutes if anybody has anything otherwise. We will send out lots of information after this session, and hopefully I will see you all again soon. And please email me or reach out on LinkedIn if you have anything you’d like to chat about. Alright, thank you everyone, I appreciate it.
