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.

Perimeter

3/17/2010
08:00 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Database Dangers In The Cloud

Moving to a cloud-based database and virtual environment comes with plenty of benefits, but there's also a potential price to pay for security.

Moving to a cloud-based database and virtual environment comes with plenty of benefits, but there's also a potential price to pay for security.People are eager to take advantage of cheap storage in the cloud, but forget that many cloud vendors provide multitenant databases, archives, and audit trails. They want to enjoy the elasticity the cloud offers and be free of hardware constraints, but forget that their data backups are reliant on hardware-based encryption. They have established processes for patch, configuration, and vulnerability management, but they cannot audit the cloud vendor's environment to verify these same standards. They want to reduce administrative overhead, but vendors leverage super-user credentials that violate separation of duties and security practices.

If you're considering moving your database to the cloud, then here are some things to first consider:

Deployment: Many cloud providers do not allow common security technologies to be deployed at all. These technologies either violate your service contract or the infrastructure they provide doesn't accommodate them. For example, many providers don't support the use of penetration testing, while others can't deploy Web application firewalls. As is common, most databases are protected by SQL injection or buffer overflow attacks because the Web application screens for it, or a third-party tool detects and blocks the attack. If you are dependent on a WAF or if pen tests are part of your security strategy, then you need to verify that the cloud provider supports them.

Visibility: You may have in place evolved configuration, vulnerability, and patch management processes. So if you are moving to a database-as-a-service or pure SaaS model, make sure you have assessment and auditing options to verify that your provider is living up to your expectations. For platform-as-a-service, verify that the tools you use today will deploy and continue to function in the cloud, and that your provider does not have the ability to gain credentials to your database.

Co-Mingling Data: The recent example where Facebook users were unwittingly provided access to other users' accounts highlights how logic flaws or failures can expose data in multitenant environments. Look at application-layer encryption, removal of sensitive information, or a provider that can guarantee data segregation before adopting a solution. Expect additional costs for this, however. And if you have sensitive data, then the cloud may not be appropriate for you.

Service: Service-level agreements are a nifty way for vendors to give you the impression of security without always providing security. Ask for explanations on any service aspect that is unclear because what they offer is seldom what you expect to get. Make sure you have a way to verify vendor claims, that they will subject themselves to auditing, and that there are penalties for noncompliance. Prospective cloud customers often don't get a full understanding of the service -- don't fall into that trap.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15570
PUBLISHED: 2020-07-06
The parse_report() function in whoopsie.c in Whoopsie through 0.2.69 mishandles memory allocation failures, which allows an attacker to cause a denial of service via a malformed crash file.
CVE-2020-15569
PUBLISHED: 2020-07-06
PlayerGeneric.cpp in MilkyTracker through 1.02.00 has a use-after-free in the PlayerGeneric destructor.
CVE-2020-7690
PUBLISHED: 2020-07-06
It's possible to inject JavaScript code via the html method.
CVE-2020-7691
PUBLISHED: 2020-07-06
It's possible to use <<script>script> in order to go over the filtering regex.
CVE-2020-15562
PUBLISHED: 2020-07-06
An issue was discovered in Roundcube Webmail before 1.2.11, 1.3.x before 1.3.14, and 1.4.x before 1.4.7. It allows XSS via a crafted HTML e-mail message, as demonstrated by a JavaScript payload in the xmlns (aka XML namespace) attribute of a HEAD element when an SVG element exists.