EP 178: New HIPAA Security Rule
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
February 25, 2025
The US Government recently released a “notice of proposed rulemaking” to update the Security Standards for the Protection of Electronic Protected Health Information. Yes, this is HIPAA. But what will it mean for covered entities and their business associates? Let’s find out with your hosts Kip Boyle, CISO with Cyber Risk Opportunities, and Jake Bernstein, Partner with K&L Gates.
Show notes:
https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C
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 178 of the Cyber Risk Management Podcast?
Kip Boyle: We're going to talk about one of the oldest security related laws in the United States. And it's been very recently updated in a major way, which is why we thought it would, well you, thought it would make a great podcast episode and I agree. And this is the HIPAA Security Rule update from December 2024.
Jake Bernstein: Yeah. And just to give people some context on the timing, I mean, this thing was released at the very end of December, during the holidays, and this recording is early January. So we put this together pretty quick. And I think this is going to be an interesting episode because I think everyone in security these days is familiar, at least knows of, HIPAA and its security rule. And it's been around, Kip, since 2003. And that's the rule. I mean, the act, actually, it took a number of years for the rule to go through finalization of rulemaking, originally. But 2003 is when it was finalized. And when HITECH was passed around 2009, it had some more changes. But then in 2013, that's what we call the omnibus rulemaking, when OCR unified the security rule and the privacy rule and a bunch of other HIPAA rules into a more or less clear collection.
And for those of you who don't remember, HIPAA stands for Health Insurance Portability and Accountability Act. The cybersecurity really focuses on the accountability, that second A. and yeah, we're talking about a 330 plus page Notice of Proposed Rulemaking that covers a revamp of the HIPAA Security Rule, specifically Subpart C, which is about the security standards for the protection of electronic protected health information. That's the PHI that everyone knows and loves. And just as a reminder, it does indeed stand for protected health information, not personal health information or private health information, but protected.
And then as a caveat, let me say, of course, that this is the proposed rule. The public comment period doesn't even end until March 2025, and it could be years, although I hope it isn't, before we get a final rule. So in any event, nothing has officially changed yet, but it would be a mistake to think, ah, this is just a proposed rule. What's it going to do? This thing is going through. I don't think anyone has any doubts that this is going through-
Kip Boyle: It's a question of timing.
Jake Bernstein: It's a question of timing. And OCR has shown the ability to move quickly when it wants to. Curiously enough, it's limited by statute to only changing the rules once a year. So if it changes the rule for the security rule, then it can't change rules again until 2026.
Kip Boyle: Interesting.
Jake Bernstein: That could impact the timing, but we're not really sure.
Kip Boyle: So we haven't defined the term OCR yet.
Jake Bernstein: Oh, right. You're right. It does not stand for optical character recognition in this context. OCR is the Office of Civil Rights. It is the subcomponent of the Department of Health and Human Services, which is responsible for enforcing HIPAA. So it's OCR that does the investigations and will fine healthcare entities all those millions of dollars for violations of-
Kip Boyle: And don't they operate the Wall of Shame?
Jake Bernstein: I do believe they operate the, I don't think that's the official name, Kip, but it is certainly a no inaccurate name.
Kip Boyle: So when you have an entanglement with the OCR, they might publish the entanglement on a webpage.
Jake Bernstein: I mean, I think they do, for sure. Most of this is public. When you get investigated by a government agency in general, those circumstances are publicized. That's, I think, part of the penalty.
Kip Boyle: But I think OCR makes it particularly easy for people to find out what's going on.
Jake Bernstein: They do. I mean, they have a virtual Wall of Shame.
Kip Boyle: Yeah, okay. So let's take a moment to just appreciate the length of time here. You said they can't do it more than once a year, but they've, I don't know. My cynical voice says they've been on Siesta for many, many years, right? So you said that the original security rule was passed in 2003, when it would've been way ahead of its time. And it's most recently been updated in 2013. So it's like where have these guys been?
Jake Bernstein: Well, so interestingly enough, there have been updates to the various HIPAA rules over the years, but like I said, since they can only update it once per year, they have to decide. So as an example, last year they really rapidly pushed through some, or maybe it was a couple of years ago, but in reaction to the Dobbs decision about abortion, they pushed through some rules to protect pregnancy-related information. And because of that, that was the only rule change they could make that year.
Kip Boyle: That's a good point, because I'm so in-depth in the cybersecurity world that it's easy to forget that HIPAA covers way more.
Jake Bernstein: HIPAA covers way more. Right. It really does.
Kip Boyle: So when you say they can't change it more than once a year, you mean considering the totality of all-
Jake Bernstein: Yeah, so we talk like the HIPAA Security Rule is separate from the HIPAA privacy rule, and I suppose you could interpret it that they are separate, but in terms of the law about the rulemaking and the frequency with which they can make changes, it really is, it's the HIPAA regulations. It's one set. So if they change one thing to cover a privacy issue that comes up in the course of life, which is what happened previously, then they can't make any other changes. And in fact, there are proposed rules that just hang out for years. And it isn't necessarily because it's taking that long or any of that.
Kip Boyle: Yeah, they're not being lazy.
Jake Bernstein: They just get lost in the shuffle of history and they're not, because they can only do it once per year.
Kip Boyle: Right. And they got to be really careful. If you only have one shot, you want to make it a good one.
Jake Bernstein: Yeah. So sometimes, you can just see how this would happen. If you've been working on something and it's not really ready, but then some emergency happens and you need to update the rule. You're not going to try to package in the unready rules with the thing that you're doing on the emergency timeframe. So whatever wasn't ready just gets left behind. So we don't really know what this means. Again, they can move fast, but they have to do so very thoughtfully. So regardless, let's think about this. The HIPAA Security Rule has not been meaningfully updated since 2013. And honestly, even that 2013 update wasn't much of an update. It's consolidated changes from the 2009 HITECH Acts passage. So in some ways, 2009 was the last substantive update, and that is 15 years ago. 16 years or something like that.
Kip Boyle: And of course, the problem is that cyber is a dynamic risk.
Jake Bernstein: Really, yeah.
Kip Boyle: And so, it's been an issue.
Jake Bernstein: It has. And I mean, Kip, when you went to the doctor in 2009, even 2013, I don't know, I still remember seeing paper medical records that in that timeframe, right?
Kip Boyle: Yeah.
Jake Bernstein: Do you see those these days?
Kip Boyle: I was just in there for something nominal, but very few. Just a few. And where I really see it, though, is the doctor gives me access to my own records and my appointments through the MyChart application, the website. So I can go and look at things there. And if I've seen multiple providers at different medical systems, I can actually see a consolidated view-
Jake Bernstein: It will consolidate. Yeah.
Kip Boyle: Of all of my records. And I remember my doctor saying one time, I was going in for a checkup last year, and my doctor said, "Oh, tell me about this and that when you were down in Oregon and you went to the clinic." And I was like, "What? How do you know about that?"
Jake Bernstein: And this gets really complicated, and this is not a HIPAA podcast, but suffice to say that there have also been additional laws passed, the 21st Century Cures Act is one of them, that have really encouraged, and in some ways required, the electronification of healthcare keeping and the interoperability. Did you know that there is an Office of the National Coordinator of Healthcare IT? That is a specific thing and its function is to really promote data sharing portability with the goal of improving health. That's what it's all about. So regardless of how you look at it, cybersecurity is a much bigger part of the healthcare operations reality than it was even as recently, if you want to use that word, as 2013. So what does this mean? Well, I think everyone can agree that the HIPAA Security Rule was long overdue for an update, but how far did OCR go in this update? So let's find out.
Kip Boyle: Yeah, that's what we're going to do on this particular episode. Now, I do want to acknowledge that we haven't really talked about HIPAA a lot on this podcast. If you go back into the archive and you look at the previous 177 episodes, it just doesn't come up very often and we haven't had a lot of clients, shared ones anyway, I know I haven't, in the healthcare space. And I don't know, I guess I've wondered if the reason why I don't work with HIPAA covered entities very much is because maybe they already have cyber risk management in place because HIPAA has been around for so long. I don't know. What do you think? Is that fair? Is that a fair guess on my part?
Jake Bernstein: I mean, I think yes and no at the same time. We both know about the many, many, many hospital, healthcare-related data breaches. I mean, we've done several episodes about ransomware targeting hospitals, what do we call it? Killware, killerware, murderware?
Kip Boyle: Yeah, we did a killware. We did an episode, which you loved, on does ransomware kill sick people?
Jake Bernstein: So obviously, there's been a ton of data breaches, ransomware attacks, associated shitcannery over the last decade or more.
Kip Boyle: Only an attorney would use that word.
Jake Bernstein: I don't know. I put it in the script and I had to say it. Reminds me of Better Call Saul.
Kip Boyle: Keep going.
Jake Bernstein: Okay. But clearly we can all agree that whatever the healthcare industry is doing, it's certainly not perfect. I mean, and there's no such thing as perfect cybersecurity.
Kip Boyle: No.
Jake Bernstein: One could argue it's not necessarily even good enough. I mean, Change Healthcare is a huge, massive problem that was just this last calendar year. The question is, Kip, is that due to a failure of regulation or is it just because cybersecurity is hard?
Kip Boyle: Yeah, it's a little from A, a little from B. Maybe a lot from A and a lot from B. I think it's both. I mean, cyber risk management isn't easy. It is a dynamic thing. It's changing all the time. Just when you think you've got it dialed in, you find out you don't. And I guess, even though we've been talking a lot about ransomware in the healthcare industry, I know that the HIPAA security role really isn't about preparing healthcare entities to be ransomware resistant. I mean, that's just not what it's designed to do.
But okay, even though it predates the NIST Cybersecurity Framework, this HIPAA Security Rule, we've seen attempts by NIST and other people to crosswalk the Cybersecurity Framework with HIPAA. I got to tell you, the one that I downloaded first from NIST was pretty awful. I had to redo it. I actually had to do my own. But yeah. So why do you think these things are touching on each other or overlapping?
Jake Bernstein: Well, so I think a big part of the problem with the original, and frankly current, HIPAA Security Rule is that it has this concept of addressable requirements. And the new rulemaking document, this Notice of Proposed Rulemaking, that 330 page monstrosity, it goes to some length discussing why OCR believes that addressable doesn't, and never did mean, "optional," but there is a clear recognition, even from the Department of Health and Human Services in this rulemaking, that the reality over the last couple of decades is that many healthcare entities did see the word addressable and instead read optional. And to get an idea of what this means, let's direct our browsers to the glory that is the Electronic Code of Federal Regulations, Kip. You may think I'm joking, and other people may, but we're going to put this link in the show notes. And the eCFR, you guys, is like if there is a quintessential way to put boring regulations on the internet, it is this website.
Kip Boyle: They've perfected it.
Jake Bernstein: They really have. I mean, every single thing about it is amazing. You can link, every paragraph practically has, it's a paragraph tool where you can copy a URL or the citation. It's just really well done.
Kip Boyle: So wait a minute. So I did not expect you to say well done, considering what you had just said before, but okay.
Jake Bernstein: I'm sorry, if there was a hint that I was sarcastic about that, let me be clear, that was not sarcasm. I really think this is one of the greatest legal resources and websites out there, and it's publicly available. To me, given the functionality of this particular website, there's nobody who can really claim that, oh, I don't have access to the huge monstrosity of federal regulations. No, you do. You might not realize it, but it is incredibly well done.
Kip Boyle: And you may not be able to read it easily because, I mean, I'm looking at it now. It's thick, man. And most of us non-lawyers are going to probably struggle.
Jake Bernstein: It is thick. But if you dig around and look at the tools, you got a timeline, you can compare dates, you can get the published edition-
Kip Boyle: All right, well, I'm going to spin up-
Jake Bernstein: You can link to. Anyways ...
Kip Boyle: Yeah, I'm going to have to give all this over to Claude and make it tell me, explain it like I'm five years old.
Jake Bernstein: And that's a fair thing. It's a fair thing. So look, I admit it probably is a bit niche, but if we start looking through the HIPAA Security Rule, which also is known as 45 CFR Part 164 Subpart C, say that three times fast.
Kip Boyle: Yeah, bet you were waiting.
Jake Bernstein: Yeah. You immediately find that flexibility is this key concept. And back in the day, OCR was really nervous about being too prescriptive. Kip, what do you think about that, even now, this idea that flexibility and flexible approach to cyber risk management? Let's talk about that for a minute.
Kip Boyle: Yeah, I think it's a good thing. I think it's a net good thing because I have seen organizations firsthand struggle with highly prescriptive approaches like PCI DSS. There's a lot of heat there to comply with it because some of the things they ask you to do in certain contexts makes no sense. Or you might have tons of really amazing compensating controls that are tuned really well for your environment, but accomplishing the same thing that some check item in PCI DSS is looking for, but it's not exactly the same. So you have to fight with the auditors.
Now the other side of this flexible approach is, and I see this in my students and in our customers in the NIST Cybersecurity Framework, they just want a checklist. They don't want to have to do the hard work of figuring out, okay, you want me to do this, but you're not telling me how to do it. You're going to make me figure it out. I don't like that. What if I get it wrong? Plus it's a lot of work. Can you just give me the checklist? So it's like you're damned if you do, you're damned if you don't.
Jake Bernstein: It's a perfect distillation of the problem here is that checklists tend to be inflexible. Flexibility is generally good, but too much flexibility, particularly when, as the HIPAA Security Rule does, and you'll see this in a moment, it starts to make it seem optional and it's confusing. That's an even bigger problem because that inaudible-
Kip Boyle: People just fuzz out.
Jake Bernstein: People fuzz out. And look, I continue to say that humanity is not good at taking proactive, preventative measures. It just isn't, as a species. And that's what makes this hard.
Kip Boyle: That's why the dentists never put themselves out of business, even though they tell us exactly what to do so we don't have to go see them, we don't do it.
Jake Bernstein: It's true. I know. That's a really good analogy, really. Okay. So I think we both agree that flexibility is important. I think it can perhaps be made too important. And I think that's what OCR may have done back in 2003 and '09 and '13. So what you do is you look under the implementation standards. And by the way, it's funny given the discussion we just had, but one of the major criticisms over time of the HIPAA Security Rule, including from people like me, is that it's so vague and it doesn't say much. And that's interesting, because on the one hand, we're like, oh, we want flexibility. But then as you pointed out, people also just want to be told what to do. And then there's this confusion of, well, you'll see in a second. So okay, implementation standards, there's two different types, Kip. Required-
Kip Boyle: Now, this is in the 330-page behemoth proposal?
Jake Bernstein: No. This is old. This is in that Electronic Code of Federal Regulations.
Kip Boyle: Okay, I'm with it.
Jake Bernstein: It's been the rule forever. Yeah, you can find it. It's section 164 306D is where we are. inaudible-
Kip Boyle: I suppose I better put that in the show notes too, huh?
Jake Bernstein: Security. Yeah. And if you want to, you can click on that D and you'll get a link directly to it. I'm telling you, it's an amazing website.
Kip Boyle: Why do I hang out with you? Sometimes I just wonder.
Jake Bernstein: I don't know why anyone does, but look at this, okay. You've got two different implementation specification possibilities, required and addressable. Okay, now Kip, required is pretty obvious, but just layman's terms. If I give you two choices, one is required and one is anything but required, in this case addressable, is it really unreasonable to think that people have started to read addressable as optional?
Kip Boyle: I don't think it's unreasonable at all.
Jake Bernstein: I don't think it is either. And I think OCR, while nobody's going to admit that, I think they realize it too. So here's the thing, Kip, actually, I gave this to you. Why don't you read what the current rule says about an addressable implementation spec?
Kip Boyle: Yeah. Okay. So it requires the covered entity or the business associate, so a covered entity is like the medical center. A business associate is like somebody who is a third party that provides a service to the covered entity, but that somehow, that service involves the protected health information. Did I get that right?
Jake Bernstein: That's right. You got that exactly right. For someone who doesn't live in the HIPAA world, you got that 100% right.
Kip Boyle: Yay. Okay. So this is what you have to do. You have to assess whether each implementation specification is a reasonable and appropriate safeguard in its environment, when analyzed with reference to the likely contribution to protecting ePHI and implement the implementation specification if it is reasonable and appropriate. Or if implementing the implementation specification is not reasonable and appropriate, document why and implement an "equivalent measure if reasonable and appropriate."
Jake Bernstein: That's a lot of reasonable and appropriateness, which-
Kip Boyle: And implementing.
Jake Bernstein: And yes, a lot of implementing for sure. Okay, so look, we talk about cyber risk assessment and things like that all the time. That's great. But I don't know, if you were a typical healthcare company, whether a covered entity or business associate, and this is what the rule says, what are you thinking at this point?
Kip Boyle: I am pissed off.
Jake Bernstein: So we can make this a bit of a therapy session. Why are you upset, Kip?
Kip Boyle: Because I'm afraid that if I actually do this stuff, then the HIPAA auditor shows up, that they're going to use the fact that I didn't do it exactly the way that they're expecting to see it as a way to get me in trouble.
Jake Bernstein: That is a completely valid concern. But do you even know what they want?
Kip Boyle: No. And that's the issue, is that I don't know exactly what they're looking for and I'm concerned that I could be misunderstanding it or coming up with some mitigation measure, as they say, a reasonable and appropriate safeguard that they've seen before or that they think is amateurish or, I don't know. I mean, I'm just worried about getting judged.
Jake Bernstein: Yeah, I think that's fair. And to make this a little bit more concrete, I'm just going to scroll and read a couple things, give you an idea of what's required and what's addressable in the old current rule. So I scroll down and let's just look at, actually, because this is the Cyber Risk Management Podcast, let's just look at the technical safeguards for a second. We'll go back to the administrative ones, but let's look at the technical safeguards. So for those following along, it's section 164.312. And okay, standard, we have, this is a great example, standard one here, A1 access control, implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights as specified above, somewhere above. And there's four implementation specifications.
You've got unique user identification, you've got emergency access procedure, you have automatic log off and you have encryption and decryption. Now Kip, half of those are required and half of those are addressable. I'm going to tell you that the unique user identification and emergency access procedure are both required. And the automatic log-off and encryption and decryption sections are addressable. And I think this is the problem. This is the problem, is let's look a little bit more. Standard integrity, implementation specification, mechanism to authenticate electronic protected health information, addressable. And this just continues. This just continues. And I think what has confused the healthcare industry about the HIPAA Security Rule is that it is both weirdly specific in certain ways, but then completely and uselessly vague in many, many others. And-
Kip Boyle: I'm getting high just listening to you read this.
Jake Bernstein: I mean, it's a lot. So, okay, I think by now, if you've been paying attention, you might have guessed what the single biggest change between the current HIPAA Security Rule is and the new proposed version. And that is, I'm not going to hide the ball, the complete elimination of the addressable concept entirely. It's just gone, Kip. It's gone. Every security standard in the new HIPAA Security Rule is now simply required.
Kip Boyle: Well, that's nice, in the sense that we can eliminate all that confusion.
Jake Bernstein: It does. It is. And it's interesting because I've heard that this is going to really prevent, particularly the smaller covered entities from just getting by without really putting in place solid cyber risk management. So now that we know the major change, what else is here? And I've given you a non-comprehensive list, but let's just poke at some of these and see what we think.
Kip Boyle: Yeah, sure. So there's quite a bit here. The first one is, no surprise whatever to anyone, written documentation of the HIPAA Security Rule, policies, procedures, and evidence of compliance. I mean, that's not new. That is not the same as before?
Jake Bernstein: I mean, it is. You would think it is and it isn't. It's unclear exactly how different this should be. Certainly, there was a standard for a security management process. You had to implement policies and procedures to prevent, detect, and contain security violations. There was a risk analysis, there was risk management, there was a sanctions policy. But what's curious, Kip, is that it was not as explicit about all of these things having to be in writing with evidence of compliance.
Kip Boyle: Okay. So now it's just pinpoint sharp. It's just completely clear in terms of what it is that they want. They've brought it into focus. So here's another one. Time limits on removing a former workforce member's access to protected health information and restoring systems after incidents.
Jake Bernstein: So these are timing issues. These are basically saying you have to do it in a certain amount of time. And previously, there were no real time limits. It was all reasonable, appropriate and this vagueness. The next one.
Kip Boyle: Okay. Yeah, the next one really speaks to that. Vulnerability scanning at least every six months and a penetration test at least annually. So that's good.
Jake Bernstein: And that's new. There was no, I mean now let's be clear, you certainly could have, as a covered entity, at any point over the last couple of decades, decided that doing vulnerability scanning and a penetration test six months and annually or whatever you want, was a reasonable and appropriate control, but it wasn't required, Kip. Now it is.
Kip Boyle: Yep. Other things here, encryption of data at rest and in transit, multi-factor authentication, configuration management that requires anti-malware protection, removal of unneeded software, disabling unnecessary network ports, network segmentation, new backup and restoration testing requirements. What are those?
Jake Bernstein: So that is the relatively simple concept of test your recovery, test your backups.
Kip Boyle: Okay. Yeah. All right, well-
Jake Bernstein: Does it actually work?
Kip Boyle: Yeah, because a lot of people get in trouble because they turn it on and go, "All right, job done." And then they never test them. Testing the effectiveness of cyber security measures at least annually. I wonder how that's different from a penetration test at least annually.
Jake Bernstein: So a penetration test is a very specific thing. This bullet point you just read, the testing the effectiveness of cyber security measures is the whole thing. I view that as more of a complete tabletop exercise, integrated with the procedures and the policies and decision-making. It isn't just penetration test.
Kip Boyle: Got it. Okay. And then the last one here is strong contingency plans that are updated and tested. And when I mean last one, I just mean the last one in the list that we're looking at. Remember, this list is not comprehensive to what the proposed rule contains.
Jake Bernstein: Yeah, it's a bit of a summary, and there's lots of really interesting things. So let me tell you this about the 330 page, give or take, rulemaking. And by the way, I don't know why I said 330. It's 393. I don't know where I got 330 from. So this thing's almost 400 pages. Now what's fascinating, Kip, is that basically all, but ... I don't know, all but 50 of these things is background. The actual rule text, the actual new text of the rule doesn't even start until, what page is this? 355.
Kip Boyle: We see this recently with another proposed rule?
Jake Bernstein: Yep. On every proposed rulemaking over the last, I mean, forever as far as I'm aware, at least in the modern era, works like this. And they have to. It's a requirement to make the rule. But what is so fascinating about this is if you go and look at the table of contents, which itself doesn't even start till page, what? Four? I guess it's on three. And there's this part three, justification for this proposed rulemaking. This is a couple hundred pages of really analysis about why this is needed. And then in part four of the rulemaking document, they do a section by section description of the proposed amendments and why. And this is really helpful. So I like, again, just from the table of contents, we can look at section 164.304 definitions. And there's this whole list.
There's a list of basically 22 things that they have done in this. And listen to this, Kip, they've clarified the definitions of access, administrative safeguards, authentication, availability, confidentiality. They've added definitions for deploy, implement, MFA. They've added a definition of risk. There was no definition of risk earlier. They've added the definition of technical controls, technology asset, threat. Now you think about these, these are all really common terms in use these days. Oh, they added a definition for vulnerability. There previously was not a definition for vulnerability. So what this tells me, without even digging into the text, this is just the table of contents, is that OCR has really looked at cyber risk management and the advances in cyber risk management over the last couple of decades. They actually directly talked about cyber risk, the Cybersecurity Framework 2.0.
Kip Boyle: Yes, I saw that.
Jake Bernstein: 2.0 they mentioned in this document, and they take advantage of all of this to really thoughtfully build out a case for why this needs to be done, what needs to be changed. And if you start looking through the administrative, physical and technical safeguard sections and the organizational requirements, you learn a lot pretty quickly.
Kip Boyle: I remember now the last time we talked about the rulemaking process, it was when we did our episode on the SEC final rule on cybersecurity.
Jake Bernstein: And actually I think even more recently was we did the CIRCIA rulemaking.
Kip Boyle: Okay.
Jake Bernstein: So we've done this a couple of times, which is why you're starting to get used to these humongous rulemakings.
Kip Boyle: Yes.
Jake Bernstein: But what does that tell you, Kip? It tells me that cybersecurity rules are going to be a big part of the future.
Kip Boyle: Yeah. And it's interesting to see all these different regulatory entities promulgating their own-
Jake Bernstein: Yep, that's a good word.
Kip Boyle: Thank you.
Jake Bernstein: Good lawyer word there.
Kip Boyle: Their own security rules. And it makes me wonder if we're headed for a convergence. I don't know. But I mean, what I've noticed is that anytime somebody says, "Well, here's what I need you to do to keep your data safe or your system safe," I mean, they're all like 80% the same.
Jake Bernstein: Well, they are. I mean, okay, yes. No, I totally agree. I see what you're saying. Yes. The requirements, and because there's a lot of overlap.
Kip Boyle: Tons of overlap.
Jake Bernstein: One of the reasons, Kip, that our practice is not focused on an industry, we work with every industry, because-
Kip Boyle: We're an equal industry opportunist.
Jake Bernstein: It is the same. But one of the things, and I'm not expecting anyone to read every word of this 393 page document, but Kip, what's really interesting is that that whole section that is not the new rule is heavily footnoted. And what are they doing with all these footnotes? Well, they are really going through their records of stuff that's actually happened. And I think that's what's most interesting about this rulemaking, is that OCR didn't do this and just out of, they didn't theorycraft, as people say. What they did is they said, "Okay, we're looking at the many, many, many actual data breaches and incidences that have happened over the last 20 years. And we're incorporating that experience," which frankly, they didn't have in 2003 for sure, because not much had happened. They didn't really even have it in 2013 or 2009.
Kip Boyle: Right. And it's good and bad. I mean, it's good that they're learning from history. I mean, we all need to understand our history. The part that's disappointing, I suppose, is, because cyber is a dynamic risk, that history does not guarantee future situations.
Jake Bernstein: And what do they say about preparing for war, Kip? You always prepare for the war-
Kip Boyle: The last war.
Jake Bernstein: The last war because you can't really prepare for the one that hasn't-
Kip Boyle: That's all you know.
Jake Bernstein: That's all you know. I mean, look what has happened over the last two years plus in Ukraine. I mean-
Kip Boyle: That's right.
Jake Bernstein: We started off with, oh, we're just going to do the same mobile tank warfare that we saw in World War II. And where did they end up? They ended up back in trench warfare with artillery, but with drones, which changed everything. So it's a completely valid concern that if we are overly concerned with what has happened, that we're going to miss and we're going to be vulnerable to what will happen. But I still think that ...
Kip Boyle: This is an improvement.
Jake Bernstein: This is still an improvement. And I think that's really where things need to be. And I think for me, what's really different is that the entire healthcare industry now has to really engage in modern cyber security practices.
Kip Boyle: Yeah.
Jake Bernstein: The incredible vagueness of that original HIPAA Security Rule, I think really did tacitly permit subpar, if not completely ineffective, cybersecurity practices. And if this rule gets finalized, that era is over. And I think that is a good thing.
Kip Boyle: I think it's a good thing as well. I wish that, be careful what you wish for Kip, but this HIPAA Security Rule, this new proposed one, is really going to help healthcare entities become more resilient to cyber attacks like ransomware? I'm not so sure that they can say, "Well, I'm HIPAA-compliant, therefore I am cyber resilient and I don't have to really worry too much about ransomware." I still think that's probably going to be an issue.
Jake Bernstein: I mean, yes, but I think it's going to be a lot better than it has been. Because right now you can say, "I'm HIPAA-compliant." I hate that phrase because it doesn't really mean anything. There's no certification. There is no, what does that even mean?
Kip Boyle: I'm 800-53 compliant too.
Jake Bernstein: Oh, don't say that. Yeah. I'm SOC 2 certified, Kip.
Kip Boyle: Yes.
Jake Bernstein: Okay. But-
Kip Boyle: You're certified, all right.
Jake Bernstein: But it does mean that if you are actually doing what the new security rule requires, you can't help but be a little bit more resilient.
Kip Boyle: Yeah, I think it will be. And I think you'll be a little bit more of a difficult target. So that's all progressing in the right direction. But we'll see if the covered entities actually, how well they take this up. Because my observation from a distance is they're just like, "No, dammit Jim, I'm a doctor, not a cybersecurity expert. Get out of my inaudible."
Jake Bernstein: That's true. But Kip, what was one of the most interesting things we noticed about that SEC, and even the CIRCIA rulemaking? You commented on it several times. It was about assigning responsibility to specific executives and individuals. And guess what? That wasn't in your list, but that's a new one too. There is a new standard section-
Kip Boyle: You buried the lead.
Jake Bernstein: I did bury the lead. Section 164.308 A8 is a new standard, assigned security responsibility.
Kip Boyle: Oh. And so is there personal liability at risk here?
Jake Bernstein: I don't know that there's ever going to be, I mean, personal liability is an awful lot and it's different than a board member who isn't really an employee. But the fact that someone has to be designated-
Kip Boyle: That's good. That's a good inaudible.
Jake Bernstein: And this is not a completely new, they are moving it around, but they also, I mean, this is what it says. OCR's enforcement experience demonstrates that in practice, many regulated entities follow informal policies and procedures that are not documented and have not documented the identification of the security official in writing. And based on that enforcement experience, and consistent with existing guidance, they want to modify the standard to specify that the regulated entity must identify in writing the security official who's responsible for the establishment and implementation of those policies and procedures. And I don't know, Kip, one of the things that I've said is that if it's not in writing, it might as well not have happened. What was the mid-2000s saying? Pics or it didn't happen. And I think from a legal standpoint, get it to me in writing or it's not real, is inaudible-
Kip Boyle: I mean, if I learned anything from my Uncle Sam, I have to document what I do. So yeah, I get that.
Jake Bernstein: Yeah, true.
Kip Boyle: That makes sense. Okay.
Jake Bernstein: Okay. Well, what else we got before we wrap up this episode? Because I think, did we go in depth on the new security rule? No. No, we did not. We're not going to do that to you, particularly since a lot of it. I mean it is-
Kip Boyle: There was really no head slapping, oh my gosh moment for you. You read this.
Jake Bernstein: No. I do want to do this, though. I do want to quickly run through. So in my version of the PDF that I downloaded, I went and highlighted the new standards. So these aren't the implementation specs. That's actually a lot more in detail, but I'm going to quickly read just the highlights of the administrative safeguards standards. So here's the first one, technology asset inventory, and then it goes on. So that's one. Risk analysis. Another one. We have a standard about an evaluation. I'll just read this a little bit. This is perform a written technical and non-technical evaluation to determine whether a change in a covered entity's or business associate's environment or operations may affect the confidentiality, integrity or availability of electronic protected health information.
That's another change. Is a lot more use of the CIA triad to define security. And I think that's a good thing. People can argue about whether that's the end all, be all, but when you're just trying to be precise, it drives me nuts when someone just says, "Well protect the security of that." Well, what does that mean? What do you mean protect the security of it? Whereas at least if you say, protect against compromise of confidentiality, integrity or availability. And Kip, we talk about this every year with the Verizon DBIR and they've really focused on using the CIA triad to talk coherently about these issues. And that's so important. So important.
Kip Boyle: Now in the PDF, think you're somewhere around page 361, right?
Jake Bernstein: That's exactly where I am, yes.
Kip Boyle: Okay. I just wanted to give a pointer for folks who download this PDF to realize it's just what Jake said. There's all this front matter and the meat doesn't start until almost the end.
Jake Bernstein: Yeah, it's like 355 is where the rule actually starts.
Kip Boyle: Okay.
Jake Bernstein: But since you're there, Kip, you can see what I mean, right?
Kip Boyle: Yep.
Jake Bernstein: That under standard risk analysis, then you get implementation specs, assessment, and there's all this other stuff that you have to do.
Kip Boyle: Well, damn you, now I'm going to have to read it.
Jake Bernstein: Oh, I think you will. You have maintenance. So, okay, another standard, Kip, patch management. That's interesting. Yet another standard down here is risk management. This requires planning, obviously. A sanction policy, and by the way, many of these standards aren't new, but the specificity and the fact that none of them are addressable, because that's been deleted, is new. Information system activity review. That's a good one. Assigned security responsibility. This is interesting. There's a standard for security. I'm not 100% sure if that's new or not, but the wording is definitely on the newer side.
Information access management. This continues. Security awareness training, security incident procedures, the contingency plan, compliance audit, BA contracts, and other arrangements and I think then we get to the end. Oh, there's one more. Delegation to business associates. Then you get into physical safeguards, things like that. So it is a big deal, and I definitely don't want to underplay it. I think the fact that nothing is addressable, everything is required, is a huge deal in practice. And I think that the requirement for, because if you go back and look at the current security rule, it doesn't take a lot of squinting to think to yourself, I don't actually have to put a lot of this stuff in writing. I don't have to. I just have to have policies and procedures. Well, I've got those. Maybe they're in Bob, the IT guy's head, but they're there.
Kip Boyle: Bob, the IT guy, I love it.
Jake Bernstein: But you can't do that anymore. It's not enough. Okay. So with that, do you have any final thoughts? I guess you did give one, which is, dang it, Jake, I'm going to have to read this.
Kip Boyle: That's the final thought.
Jake Bernstein: And it is, and you should.
Kip Boyle: Yeah, I really do need to read this, but listen, thank you so much for pre-marking the areas of the PDF that I should put my attention on first. I very much appreciate that. And yeah, I guess we better end this episode so I can get busy and start to learn this.
Jake Bernstein: Yeah. All right, let's do it.
Kip Boyle: Okay. That wraps up this episode of the Cyber Risk Management Podcast. Today, we discussed the long overdue Notice of Proposed Rulemaking from the Office of Civil Rights that revamps the HIPAA Security Rule. And we think these rules could take a year or more to finalize, but they're absolutely on their way. So everybody needs to get ready and 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.
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.