How is Encryption Used to Protect Protected Health Information (PHI)?
Townsend Security recently hosted a webinar titled “Protecting PHI and Managing Risk – HIPAA/HITECH Compliance” that focused on how members of the healthcare industry can achieve a breach notification safe harbor if they are properly encrypting their Protected Health Information (PHI). PHI can be stored in many different places – from Electronic Medical Records (EMR) in a database to healthcare claims stored on a laptop by a health insurance company. With fines for data breaches averaging into the millions of dollars, it is more important than ever to protect your PHI. We received some great questions during the webinar that we would like to share with our blog readers.
How is encryption used to protect PHI?
Encryption solutions are used in a variety of places. Basically those of us that are encryption vendors tend to think of encryption in two ways. The first is encryption of data in motion. For example, if you open a web browser and go to a website that uses HTTPS and the “lock” comes on, you are encrypting your data as it is “in motion.” Typically, SSL or TLS encryption is being used. These technologies protect any information that flows between your web browser and that endpoint – making it safe to send PHI like a social security number or medical records online.
Second, we think about securing data at rest. This typically means data that is in a database. When you go to the doctor and he interviews you and puts his results into the computer, that data is landing in a database and it needs to be protected. AES encryption and proper key management are necessary to protect this data.
Our database software has encryption options. Why would we need a third party software?
Lets start with an example. Encryption is part of the package when you purchase Microsoft SQL Server 2008 Enterprise Edition or Oracle 11g with Advanced Security. So you might say to yourself, “Why do I need something else if Microsoft offers encryption?” In these cases, you are sitting in a good place for the cryptographic portion, but still need encryption key management to meet any compliance regulation.
To line up with industry standards for encryption best practices, you need to have dual control and separation of duties. To do this you need to physically separate the encryption keys from where the protected data lives (Your SQL Server or Oracle database). It is great when a vendor provides encryption as part of their database software, but it only gets you halfway to where you need to be. An encryption key management Hardware Security Module (HSM) will bring you in line with best practices for dual control and separation of duties, allow you to pass your audit, and achieve safe harbor status in the event of a breach.
View our webcast “Protecting PHI and Managing Risk – HIPAA/HITECH Compliance” to learn how your organization can manage their risk of a data breach and achieve breach notification safe harbor status.