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.

Partner Perspectives  Connecting marketers to our tech communities.
3/10/2016
01:50 PM
Jamie Tischart
Jamie Tischart
Partner Perspectives
100%
0%

Data In The Cloud: What Everyone Should Know

When vetting a cloud or SaaS provider, it is imperative that you find out how they handle data security and privacy. Here are some key questions to ask.

One of the most valuable assets in today’s virtual world is the data that is associated with your organization, whether it is customer lists, financial information, product telemetry, or intellectual property. As your data and applications migrate to and through the cloud, it is understandable to have a fair amount of fear and uncertainty about the process and the level of security. I know that the cloud community is focused on providing the best security and privacy for customers. But there are some important steps you can take that will reduce your anxiety and ensure the privacy and integrity of your data.

When vetting a cloud or SaaS provider, it is imperative that you do the groundwork and find out how they handle data security and privacy. The first recommendation is to fully review the terms and conditions of the service provider for each and every service that you plan to utilize. This may seem obvious, but people are sometimes intimidated by the small print and legalese, make assumptions about what is and is not covered, or quickly scroll through and click accept. However, this is a foundational step as the security and privacy policies for each service may be different. There may be minimal information, unclear disclosures, or a wealth of details about what the service does (and is allowed to do) with your data.

The next action is to ask questions about these policies, to clarify terms or expand vague conditions. I call this the data declaration disclosure. For each service you intend to use, ask the provider the following questions:

Security Questions:

  1. Who has access to my data, both physically and virtually?
  2. Do you outsource any of your data storage?
  3. How do you handle legal requests for data review?
  4. How and when is my data deleted?
  5. What is your data architecture, and how is my data isolated from your other customers?
  6. What certifications and/or third-party audits are performed on your service?

Privacy Questions:

  1. What data do you collect from my organization, and how is it kept private?
  2. What is that data used for?
  3. How long do you retain that data?
  4. Do you encrypt the data in any manner?
  5. Where is the data stored?
  6. Do you roll up data and transmit it to other internal or external entities, and if so, how is it transmitted and to where?

Operational Questions:

  1. What is your database and storage architecture redundancy model?
  2. What is your backup frequency?
  3. What is the recovery time from failure: minimum, average, and maximum?
  4. How can I access or download my data from your service?
  5. Do you provide any analytic tools for my data?
  6. In the event of data corruption, what is the maximum data loss that I can expect?

These are good questions to ask yourself, even if you are not leveraging cloud solutions yet. This is your data, and you have the right to fully understand what it is used for, how it is secured, how it is kept private, and how well it is going to be managed. We continue to see progress in this area, as technology, regulation, and cloud adoption evolve. I expect that as a group, cloud providers will be able to offer better security and privacy for data than individual organizations can for themselves.

Jamie Tischart is the CTO for Cloud/SaaS (Security as a Service) and is responsible for leading the creation of Intel Security's future generation cloud solutions and creating sustainable competitive advantage. He has been with Intel Security for more than 10 years in a wide ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MikeA360
50%
50%
MikeA360,
User Rank: Apprentice
3/16/2016 | 3:48:40 PM
Great Read - Good Advice
Very mice article covering very important subject that will protect a company. I'd say make sure the person(s) asking the questions have the background and experience to utilize the information properly.

Mike
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...