Heartbleed and HIPAA
April 14, 2014
On April 7th, the news hit the wire that there is a serious bug in the OpenSSL program – one of the most popular cryptography programs out there. This bug allowed information normally protected by an SSL/TLS license (a type of encryption) to be compromised. The scary thing about this bug is that it appears to have been around as far back as December 2011 What does this mean for your website? As of right now, we don’t know if or what information was breached. The first thing you should do is look at your website host and see if they were using OpenSSL. If so, have they patched it?
There are a couple of free resources that have popped up to help test to see if your site is safe:
Before you rush to change all your passwords, make sure that your site(s), and providers, have all applied the patch to their servers. At this point, most servers should be patched, but a quick call to your web host is strongly recommended. Now, let’s talk about your personal information. This is a great time to go through all your financial, email and social media passwords and change them. Here is a list of major sites that may have been affected:
Some of the sites that use OpenSSL are Dropbox, Yahoo Mail, Facebook, and Gmail (Google says that there is no reason to change your password, but it’s probably a good idea just to be safe.) All of these sites appear to have been patched, but any older passwords could be vulnerable. Here is a post from a few weeks back where we talk about updating your passwords.
Now, how does Heartbleed affect your HIPAA compliance? Does this mean you need to send a breach notice to all your clients? As of right now, we don’t know if anyone actually has been grabbing information. We don’t think there is a need to send out breach notifications to your clients, but it might be nice to post a statement on your website or send out an email to your clients that says something like:
We here at (your company name) take your privacy very seriously. Your personal information may be vulnerable if your web hosting company used OpenSSL We recommend that you contacted your web providers, inquire if they used OpenSSL and whether they have patched their systems if they have used that encryption. Once the system is patched we recommend that you update any passwords you have at this time, and report any suspicious activity that you find with your personal information to us and the proper authorities so we can help you address this as quickly as possible.
And in case you were wondering… Yes, we’ve done those things too in order protect our clients, and to protect our own personal information. It’s always better to be safe, and we take that responsibility very seriously when it comes to the information we have and keep on you. We at Total HIPAA have patched all our systems and changed all our passwords, and we are recommending that you do the same for any passwords that protect sensitive information. If nothing else, it’s a good business practice. Remember, this action needs to be documented in your Risk Analysis and possibly addressed in your security policies and procedures.
By Jason Karn
August 3, 2020
In October 2017, the National Association of Insurance Commissioners (NAIC) established an Insurance Data Security Model Law and released it to states for legislative consideration. They used New York’s Cybersecurity… Read More ›Read More