Regulations and the cloud: HIPAA modification provides clarity
Changes to the regulations should make it easier for cloud clients and vendors to understand their responsibilities
Computerworld - Many regulatory requirements that impact cloud computing were enacted before cloud computing came into existence. As a result, they don't directly or effectively address issues that can arise because of the cloud, leaving both client organizations and cloud vendors without clear guidance on how to comply. While such laws are typically updated at a much slower pace than the cloud evolves, now that the cloud is becoming more established, some regulations are starting to catch up. A case in point is the Health Insurance Portability and Accountability Act (HIPAA).
HIPAA establishes national standards to protect people's electronic protected health information (PHI) and requires appropriate administrative, physical and technical safeguards to ensure the confidentiality, integrity and security of electronic PHI. Any organization in the U.S. contemplating moving a function involving PHI to the cloud needs to thoroughly understand HIPAA and comply with it.
HIPAA was initially enacted August 21, 1996, more than a year before the first known academic usage of the term "cloud computing" and more than a decade before most businesses were even considering the possibility of entrusting data to cloud vendors. A significant modification to the act was issued on January 25, 2013. While none of this modification's 138 pages specifically mentions cloud computing, the changes it contains are applicable and should be fully absorbed by your cloud-computing team.
To use the language of HIPAA, a client organization moving a function that involves PHI to the cloud would be what is identified as a "covered entity." A vendor that creates, receives, maintains or transmits PHI on behalf of a covered entity would be what is called a "business associate." While HIPAA doesn't specifically identify cloud computing vendors as business associates, they clearly fall within this scope.
Historically, covered entities have been directly responsible for HIPAA compliance, with business associates only indirectly responsible via a business associate agreement (BAA) between the two parties. According to HIPAA, a BAA needs to require the business associate to implement safeguards that reasonably and appropriately protect the confidentiality, integrity and availability of PHI, and to ensure that any subcontractor engaged by the business associate in this process agrees to implement similar safeguards.
Some of the largest reported HIPAA breaches to date have involved business associates, so it should come as no surprise that a number of changes in the recent modification clarify and increase the accountability of business associates. Specific elements of the modification that are pertinent to cloud computing include:
* Business associates are now separately and directly liable for compliance with, and violations of, HIPAA privacy, security and breach notification rules.
Other columns by Thomas Trappler
- NASA's cloud audit holds value for all
- Who can pry into your cloud-based data?
- Does your cloud vendor protect your rights?
- Software licensing in the cloud
- For credit card handlers, cloud computing guidelines just got clearer
- Regulations and the cloud: HIPAA modification provides clarity
- Certification programs are making it easier to know all about a cloud vendor
- The do's and don'ts of safeguarding cloud-based data with encryption
- For a good cloud contract, start with an RFP
- It takes a team to create a good cloud contract
- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
- Slideshow: 7 security mistakes people make with their mobile device
- iOS vs. Android: Which is more secure?
- 11 sure signs you've been hacked
- What Datapipe customers need to know about the new PCI DSS 3.0 compliance standard This handy quick reference outlines what PCI DSS 3.0 is, who needs to be compliant and how Alert Logic solutions address the new...
- The 12 PCI DSS 3.0 requirements addressed by Peer 1 Hosting This handy quick reference outlines the 12 PCI DSS 3.0 requirements, who needs to be compliant and how Alert Logic solutions address the...
- Defense Throughout the Vulnerability Life Cycle This whitepaper provides insight into how to leverage threat and log management technologies to protect your IT assets throughout their vulnerability life cycle.
- The Critical Role of Support in Your Enterprise Mobility Management Strategy Most business leaders underestimate the importance of tech support when they choose an EMM solution. Here's what to put on your checklist.
- Live Webcast Best Practices for the Hyperconverged Enterprise Network To the Age of Constant Connectivity and Information overload
- Live Webcast Unmasking the Differences between Consumer and Enterprise File Sync & Share The consumerization of IT combined with the rapid pace of the modern mobile workplace is forcing enterprise IT teams to evaluate file sync...
- Live Webcast Government Agency Webifies Outdated COBOL Applications Let this CTO tell you how his agency converted 1980s-era green screens into an e-filing portal for the 100,000 cases handled each year...
- The New Way to Work Knowledge Vault This Knowledge Vault focuses on how, in today's increasingly virtual world, it's more important than ever to engage deeply with employees, suppliers, partners,...
- Getting Ready for BlackBerry Enterprise Service 10.2 Find out how BlackBerry® Enterprise Service 10 helps organizations address the full spectrum of EMM challenges, while balancing the needs of both the... All Applications White Papers | Webcasts