Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud Security

12/26/2017
08:55 AM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

Cloud Security Is a Shared Responsibility

In the answer to a question from a recent webinar, editor Curtis Franklin looks at who's responsible for data security in the cloud.

Here at Security Now, webinars are interactive affairs. In our most recent webinar, we had some great questions, including a couple that we couldn't answer in the time allowed. Here's the first of the questions along with our answer for everyone in the community to see.

In our Look Forward to CyberSecurity in 2018, Gary asked:

If we are going to move more critical applications and the data accessed, produced and stored -- will encryption capabilities become critical? And would anyone really outsource this function to AWS? Many people think AWS and Azure are taking responsibility for your apps and data when you move them to the cloud -- are they really going to "add this" via their service offerings?

The question of who takes responsibility for your applications and data is a critical issue when moving to a cloud infrastructure. Cloud providers have tried to bring some discipline to the question of who's responsible for what through the shared responsibility model of security. Stated most succinctly, this states that the cloud provider is responsible for the security of the cloud infrastructure (including the services and applications they're contracted to provide) while the customer is responsible for the security of the data that runs through the infrastructure.

Amazon was the first major cloud provider to publish a formal statement of their policy on AWS. Their language draws a distinction between the security of the cloud and the security of what's in the cloud. It's a useful distinction that helps clarify the pieces that fall under each definition.

Of course, Amazon has not been alone in drawing the distinction: Microsoft has also released information on the shared security model as applied to Azure. Google also has a paper explaining their security model, though it goes into more detail on the tools they provide to help customers with their responsibilities.

When you strip away all the explanations and jargon, the lesson to be learned in all of these papers and posts is that going to the cloud doesn't mean that you can forget about security. No cloud provider is stepping up to assume responsibility for your data's security -- that's still your job.

The fact that it's your job means that you may need to bring new tools and strategies to bear on data that no longer lives within the cozy confines of your network boundary. These tools, which range from micro-segmentation to CASB, should be deployed in consultation with your cloud provider so that you're certain neither of you is stepping on the other's toes in the name of security.

If you're interested in the other questions and answers from the webinar, as well as the editors' takes on the stories we're likely to be talking about in 2018, it's not too late to listen to the webinar. You've got time to ask your own questions, too -- just leave them as comments to this article or the next article answering questions from the event. And keep your eyes open for our next editorial webinar, coming to Security Now in January 2018!

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...