Welcome Guest. | Log In | Register | Membership Benefits


Topics:   Database Security Tech Center : Security Views : Cloud Security Tech Center

Securing Databases In The Cloud

Cloud services are comprised of pools of compute, network, information, and storage pools, so focus on securing the information rather than the database

Feb 02, 2011 | 06:16 PM | 

By Adrian Lane
Dark Reading

I'm in the process of writing some training materials for the Cloud Security Alliance (CSA) certification exam. When coming up with recommendations that follow the CSA Security Guidance (PDF), you begin to realize that each of the different deployment models for "the cloud" change what you can do -- and what you need to do -- for security. Dramatically.

Depending on the model you select, some of the technologies we use today just don't work. Further, what's considered a database in the cloud commonly includes indexed flat files, horizontal, in memory, noSQL, and hybrid forms along with ubiquitous relational platforms, each with their own set of best practices. Finally, each cloud vendor provides slightly different security features, so you have to tweak your security model regardless.

Then it dawned on me. It would be a whole lot easier to recommend how to secure the data as opposed to the database and associated infrastructure. That is the goal, right? Keep your data safe?

During the next couple of weeks, my goal is to introduce an approach to securing structured data within different cloud deployments. I am calling it the Information Centric Security Life Cycle because it looks at how to protect data in use, in motion, and at rest. To frame the discussion I will need to outline the different cloud deployment models, namely platform-as-a-service (PaaS), infrastructure-as-a-service (IaaS), software-as-a-service (Saas), and public vs. private environments. Each model provides a different base set of security features out of the box, and requires you to fill in the gaps. That's really one of the biggest challenges with cloud security is determining what is available and then figuring out what you need to sufficiently protect data.

Most of you are familiar with SaaS, some of you hearing the term long before "the cloud" entered into your IT vocabulary. In essence, you rent software that is hosted on someone else's servers. Your store your data there, customize the Web interface to your liking, and have your employees use the Web portal to access the software as if it were your own.

Behind the scenes, all of the servers, routers, databases, and associated software are owned and operated by the service provider. What's more, you actually share that application with other customers in what is called a multitenant environment. The cost of these services goes down because you are sharing resources among many customers. The democratization of resources and elastic nature of the service does not get pushed in your face unless you look behind the curtain to see what's going on.

So what if you want to run different applications, or multiple applications, on the same model? When you peel back the layer of service, you get PaaS. PaaS is different from SaaS because you are responsible for the management of the software stack. You are being provided a platform, typically from the OS layer up, on top of which you install and manage your applications. You pay for each instance you create.

If we peel back one more layer off the stack, then we are left with raw infrastructure; processing power, disk storage, and Internet connectivity. When we subscribe at this level, we are buying IaaS. In this model we orchestrate the raw resources we need and install whatever operating systems, file systems, or network topologies we need.

The more abstract the service, the more security you are responsible for providing. When it comes down to it, cloud computing separates applications, information, and underlying infrastructure into logical pools of resources. But since we have abstracted computing resources into little bits, the security features available within traditional systems are usually neither present nor offered by your cloud provider. The pools of resources can be rapidly assigned, configured, and scaled as needed. The cloud is essentially a utility-like model for allocating computing resources; you use what you need and get charged for however much you use. The security model should follow the use model. It's for this reason -- because cloud services look at resources in a granular fashion -- that it makes sense to look at security at the component, or data, level.

Two additional distinctions need to be made to contrast different cloud models and the underlying deployment of the cloud resources. The first important distinction is that "virtualization" and "cloud" are not the same. Your cloud provider may or may not use virtualization technology. Virtual servers are talked about in the same breath as the cloud because they are a useful measurement of resources. It was Chris Hoff on the Rational Survivability blog who said it best: "Depending upon the type of Cloud, the de-facto atomic unit of the digital infrastructure is now the virtual machine ... virtualization is not required for Cloud Computing, but is an enabler."

The second distinction is public vs. private clouds. Given the gray areas around compliance objectives, and that separation of duties and data security in a multitenant environment don't meet compliance guidelines, we see cloud vendors and end users create "private clouds" where multitenancy and data co-mingling do not occur.

In my next blog post, I will outline some of the security issues with cloud environments and introduce the data centric security life cycle.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports