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
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-26788
PUBLISHED: 2021-03-08
Oryx Embedded CycloneTCP 1.7.6 to 2.0.0, fixed in 2.0.2, is affected by incorrect input validation, which may cause a denial of service (DoS). To exploit the vulnerability, an attacker needs to have TCP connectivity to the target system. Receiving a maliciously crafted TCP packet from an unauthentic...
CVE-2021-23351
PUBLISHED: 2021-03-08
The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in ...
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.