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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-2319
PUBLISHED: 2019-12-12
HLOS could corrupt CPZ page table memory for S1 managed VMs in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in MDM9205, QCS404, QCS605, SDA845, SDM670, SDM710, SDM84...
CVE-2019-2320
PUBLISHED: 2019-12-12
Possible out of bounds write in a MT SMS/SS scenario due to improper validation of array index in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ805...
CVE-2019-2321
PUBLISHED: 2019-12-12
Incorrect length used while validating the qsee log buffer sent from HLOS which could then lead to remap conflict in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdra...
CVE-2019-2337
PUBLISHED: 2019-12-12
While Skipping unknown IES, EMM is reading the buffer even if the no of bytes to read are more than message length which may cause device to shutdown in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8053, APQ809...
CVE-2019-2338
PUBLISHED: 2019-12-12
Crafted image that has a valid signature from a non-QC entity can be loaded which can read/write memory that belongs to the secure world in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastruc...