Watch Forrester's complimentary webinar with Chase Cunningham where he discusses how to implement and maintain Zero Trust with the Zero Trust eXtended Framework.
Hindsight is 20/20; it's easy to look back on past mistakes and identify ways to prevent them from reoccurring, especially when it comes to breaches reported on the Office for Civil Rights' (OCR) "wall of shame." To better serve our healthcare provider clients, we recently looked back at the past year of Health Insurance Portability and Accountability Act (HIPAA) settlements and identified what went wrong in 10 of the reported breaches, then pulled key takeaways for other healthcare providers to learn from.
Healthcare security teams have worked hard to improve their security fundamentals, prompting increasing security budgets and adoption of basic security tools. In the past, device loss and theft were top causes of HIPAA settlements, but this is no longer the case as healthcare providers mature their security practices. We now see hacking/IT incidents as the top cause of breaches leading to HIPAA investigations.
As hacking incidents and more sophisticated threats lead to more expensive HIPAA violations, healthcare providers must finally move beyond compliance guidelines provided by the OCR and opt instead to adopt industry best practices. We listed several in the report "Lessons Learned From The Latest HIPAA Security And Privacy Incidents" (behind paywall) that healthcare providers can follow to better ensure that the mistakes of the past aren't repeated.
Some practices, such as adopting a Zero Trust architecture for an organization's network, will require serious commitment and resources. However, there are also smaller steps, like better enforcement measures of security policies that have already been approved by the security team, that can be implemented today to better protect sensitive data. The best road maps will include a combination of these short- and long-term improvements to your organization's security posture.
This post was written by Senior Analyst Christopher Sherman, and originally appeared here.