IDaaS and the HIPAA Security Rule

Written by Zach DeMeyer on August 15, 2018

Share This Article

The changing landscape of IT is giving organizations new opportunities to address compliance. One area to consider is IDaaS and the HIPAA Security Rule. The core of any compliance initiative is controlling user access to maintain and secure an organization’s sensitive resources, among other areas, as evidenced by HIPAA’s Technical Safeguards 164.312. So, by having a strong IDaaS core, achieving HIPAA compliance can be made easier.

Managing the HIPAA Security Rule to Date

HIPAA security rule

For many years, IT organizations have been challenged to address HIPAA compliance. The landscape, of course, was dramatically different in the past. IT infrastructures used to be largely on-prem and Windows®-based. This homogeneity made it easier to leverage Microsoft® solutions such as Active Directory® to help control user access. With one unified (albeit Windows-based) identity, achieving HIPAA compliance was a relatively easy task.

With more IT infrastructure now moving to the cloud, however, maintaining HIPAA compliance becomes a much more complex duty This is especially true for organizations leveraging IaaS providers such as AWS®, GCP™, and Azure®. IT organizations subsequently struggle with controlling user access, because solutions such as Active Directory are designed to be run in on-prem, Windows-based environments. However, the modern day organization is leveraging more than just Windows systems and solutions.

This situation then forces IT organizations to create more infrastructure to manage their hybrid HIPAA environments, with solutions such as separate directory services, manual user management, or configuration management systems such as Chef, Puppet, Salt, or Ansible. All of these create significant issues for IT organizations, and ultimately end up adding more work to already complex compliance initiatives.

An IDaaS Solution for the HIPAA Security Rule

System Agent

Thankfully, a new generation of Identity-as-a-Service (IDaaS) solution called JumpCloud® Directory-as-a-Service® is addressing the HIPAA Security Rule authentication and identity security requirements. As a cloud directory service, this IDaaS platform securely connects users to systems (Windows®, Mac®, and Linux®), servers (on-prem, AWS, GCP, etc.), web and on-prem applications via LDAP and SAML, physical and virtual file servers (e.g. NAS appliances, Samba file servers, Box™, and more), and wired and WiFi networks through RADIUS.

Coalfire Systems, a leading independent auditor, recently conducted rigorous testing and validation of the compensating controls for HIPAA Security Rule requirements. In their whitepaper, Coalfire states that, “JumpCloud demonstrated a high level of flexibility for user management, customization of policies, policy enforcement, notifications, and configurations including logging.” Along with that, Coalfire notes, “After performing a review of business impacts and a technical assessment, Coalfire determined that the JumpCloud DaaS platform, as outlined in this document, can help organizations meet applicable technical requirements of the applicable controls of the Health Insurance Portability and Accountability Act Security Rule.”

Learn More About JumpCloud

To learn more about leveraging a new generation of IDaaS in your pursuit for compliance with the HIPAA Security Rule, feel free to contact us. Our expert support team will be happy to answer any questions about IDaaS and the HIPAA Security Rule you may have. To see the JumpCloud Directory-as-a-Service platform in action, please schedule a demo, or even give it a try for yourself. Signing up is free, and so are you first ten users.

Continue Learning with our Newsletter