Amazon Web Services (AWS) has pioneered the Shared Responsibility Model in the cloud. Basically, this model outlines how cloud service providers and consumers of these cloud-based services should share responsibilities when it comes to ensuring security in the cloud. AWS and other cloud service providers (CSPs) are responsible for ensuring that cloud infrastructure is secure. Meanwhile, companies (those using the cloud services) are responsible for their data, networks, applications, and operating systems — anything they own that lives in the cloud.
We’ve been talking a lot about compliance lately. That’s because, as more businesses are moving to the cloud and storing internal and customer data there, the means to achieving compliance change significantly. But it’s not the approach to compliance that changes in the cloud, it’s the tooling, as we explained in our post How Does Compliance Differ In The Cloud Versus On-Premise? So as more businesses move to the cloud or operate hybrid environments, we want to help them become clear about what they need to do and, for the purpose of this post, when they need to do it.
The Office of Civil Rights (OCR) has been alluding to a large-scale HIPAA audit for quite some time now — and it looks like that threat will soon come to pass.
Compliance would be challenging even if it were a black and white issue. The reality is that compliance regulations, such as PCI DSS and HIPAA, are really just a string of requirements open to interpretation. The definitions of each requirement can vary, sometimes quite a bit, from auditor to auditor or from company to company. Today, even the auditors are getting audited in an effort to ensure that the application of compliance regulations is as uniform as possible.
As a business, whether you’re storing patient records or processing customer credit card data, chances are the government or your customers (or, many times, both) require you to meet some sort of compliance standards. And it ain’t easy.
Often companies think of compliance as an annoying imposition — something to grin and bear. And while achieving compliance is not always a cakewalk, the upside of doing so can be huge. Whether you are interested in starting a company, entering a new market, or winning new customers, achieving compliance can be a major business driver. Here’s why it’s beneficial to your bottom line to think about compliance in this way.
An increasing number of healthcare organizations are transitioning from data centers to cloud computing today. Healthcare CIOs are, like those in many other industries, turning to the cloud to realize benefits that include efficiency, flexibility, and cost savings. Some experts argue that this increased use of the cloud opens them up to more security challenges, but in fact the cloud isn’t necessarily any less secure than traditional computing — and in many cases, it is more secure. It’s a matter of using it intelligently and building a complete and appropriate security strategy.
PCI DSS. HIPAA. SOC 2. SOX 404. Compliance can be a complicated and confusing beast, with plenty of acronyms and layers of regulations — not to mention expenses and stress. But achieving compliance in the cloud can also be the key to unlocking new sources of revenue, winning business, and achieving success in today’s competitive business environment.
How many times have you finished a 1,000-piece puzzle? How about a serious game of Monopoly? Both of these activities have parallels with the process of meeting compliance regulations.
You don’t have to look far to see that data breaches are running rampant among healthcare organizations. In 2015, three of the highest-profile cases – Community Health Systems, Anthem and Premera – resulted in the breach of over 96 million personal health records.