Security in the cloud planning guide

SEPTEMBER 2011

Planning Guide
Cloud Security

Seven Steps for Building Security in the Cloud from
the Ground Up
Why you should read this document:
This guide provides practical information to help you integrate
security planning into your cloud computing initiatives and:
• Makes suggestions and recommendations for strengthening
data and platform protection in cloud implementations.
• Provides guidance on encryption to protect data.
• Describes the importance of a trusted foundation to secure
platform and infrastructure.
• Explains how to build higher assurance into auditing to
strengthen compliance.
• Discusses extending trust across federated clouds.

Planning Guide
Cloud Security
Seven Steps for Building Security in the Cloud
from the Ground Up SEPTEMBER 2011

Sponsors of Tomorrow.™

Contents 3 Security in the Cloud:
What It Is (and What It Isn’t)

5 Security Challenges for Cloud Environments

6 Step 1: Start Security Planning Early

10 Step 2: Identify Vulnerabilities for Your
Selected Service(s)

12 Step 3: Four Things an IT Manager Can Do
To Mitigate Security Vulnerabilities

13 Step 4: Protect Data—in Motion, in Process,
and at Rest

15 Step 5: Secure Your Platform

16 Step 6: Extend Trust across Federated Clouds

17 Step 7: Choose the Right Cloud Service Provider

19 Intel Resources for Learning More

2 Intel IT Center Planning Guide | Cloud Security

Cloud Security:
What It Is (and What It Isn’t)
The cloud seems to be on everyone’s mind these days. If you’ve Security challenges in the cloud are familiar to any IT manager—loss
been considering how to make the leap to cloud computing, you’ve of data, threats to the infrastructure, and compliance risk. What’s
also had to start thinking about how to extend security to this new new is the way these threats play out in a cloud environment.
technology environment. Despite potential savings in infrastructure
costs and improved business flexibility, security is still the number-
one barrier to implementing cloud initiatives for many companies.

Cloud Security Is ... Cloud Security Isn’t …
• The response to a familiar set of security challenges that manifest • A one-size-fits-all solution that can protect all your IT assets. In
differently in the cloud. New technologies and fuzzier boundaries addition to different cloud delivery models, the cloud services you
surrounding the data center require a different approach. deploy will most likely require more than one approach to security.
• A set of policies, technologies, and controls designed to • A closed-perimeter approach or a “fill-the-gap” measure.
protect data and infrastructure from attack and enable Organizations can no longer rely on firewalls as a single point
regulatory compliance. of control, and cobbling together security solutions to protect
a single vulnerability may leave you open in places you
• Layered technologies that create a durable security net or grid.
don’t suspect.
Security is more effective when layered at each level of the stack
and integrated into a common management framework. • Something you can assume is provided at the level you require
by your cloud service providers. Make sure you spell out and can
• The joint responsibility of your organization and its cloud provider(s).
verify what you require.
Depending on the cloud delivery model and services you deploy,
responsibility for security comes from both parties.

Cloud computing security is a broad topic with hundreds of recommendations for strengthening data and platform protection in
considerations—from protecting hardware and platform technologies your cloud implementations. The remainder of this guide walks you
in the data center to enabling regulatory compliance and defending through seven key steps that will help you plan your cloud security
cloud access through different end-point devices. The focus from the ground up.
of this planning guide is to provide you with suggestions and


Intel Experience with Cloud Security

Much of the information in this document comes from our
experience working with cloud providers, virtualization and Three Major Trends That Impact
security solution vendors, OEMs, and large enterprise customers— Cloud Security
as well as the experience of our own Intel IT building and deploying To manage cloud security in today’s world, you need a
cloud technology. solution that helps you address threats to enterprise
data and infrastructure, including the major trends
Intel IT has embarked on a radical five-year redesign of the Intel you are up against.
information security architecture. This redesign moves us away from
a traditional binary trust model to a multitiered trust model with a • Changing attackers and threats:
particular emphasis on data and people as the new perimeter. This Threats are no longer the purview of isolated hackers
new architecture is designed to support key initiatives such as cloud looking for personal fame. More and more, organized
computing as well as IT consumerization. crime is driving well-resourced, sophisticated, targeted
attacks for financial gain.
Our Intel Cloud Builders1 program continues to yield in-depth • Evolving architecture technologies:
guidance that you can use, including reference architectures, With the growth of virtualization, perimeters and
education, and a forum for discussion of technical issues. In addition, their controls within the data center are in flux, and
Intel’s strategic partnership with McAfee2 provides the foundation data is no longer easily constrained or physically
for a holistic security and compliance management platform to isolated and protected.
ensure overall integrity of the cloud infrastructure.
• Dynamic and challenging regulatory environment:
Organizations—and their IT departments—face
ongoing burdens of legal and regulatory compliance
with increasingly prescriptive demands and the high
penalties for noncompliance or breaches. Examples of
regulations include Sarbanes-Oxley (SOX), Payment
Card Industry (PCI), and the Health Insurance Portability
and Accountability Act (HIPAA).

1 Intel Cloud Builders is a cross-industry initiative to help enterprises, telecommunications companies, and service providers build, enhance, and operate secure cloud infrastructures.

2 McAfee is a wholly owned subsidiary of Intel.


Security Challenges
for Cloud Environments
The Cloud Security Alliance, an industry group promoting cloud Unknown risk. Releasing control of your data to a cloud service
computing security best practices and standards, has identified provider has important security ramifications. Without clearly
seven areas of security risk.3 Three of these apply directly to our understanding the service provider’s security practices, your
focus on protecting data and platform: multitenancy, data loss, and company may be open to hidden vulnerabilities and risks. Also,
unknown risk. the complexity of cloud environments may make it tempting for
IT managers to cobble together security measures. Unfortunately,
Multitenancy and shared technology issues. Clouds deliver scalable that same complexity and the relatively new concept of cloud
services that provide computing power for multiple tenants, computing and related technologies make it difficult to consider the
whether those tenants are business groups from the same company full ramifications of any change, and you may be leaving your cloud
or independent organizations. That means shared infrastructure— open to new or still undiscovered vulnerabilities.
CPU caches, graphics processing units (GPUs), disk partitions,
memory, and other components—that was never designed for
strong compartmentalization. Even with a virtualization hypervisor Intel and Best Practices in
to mediate access between guest operating systems and physical Cloud Security
resources, there is concern that attackers can gain unauthorized
Intel is a member of several industry groups that develop
access and control of your underlying platform with software-only
standards and best practices for security and cloud
isolation mechanisms. Potential compromise of the hypervisor layer
computing, such as the Cloud Security Alliance (CSA). For
can in turn lead to a potential compromise of all the shared physical
example, Intel is the nonvoting technical advisor to the
resources of the server that it controls, including memory and data
Open Data Center Alliance (ODCA), an independent IT
as well as other virtual machines (VMs) on that server.
consortium comprised of global IT leaders who have come
together to provide a unified customer vision for long-
Experience at Intel found that virtualization brings with it an
term data center requirements represented by more than
aggregation of risks to the enterprise when consolidating
280 member companies. ODCA released a roadmap of
application components and services of varying risk profiles onto
hardware and software requirements in June 20114 with
a single physical server platform. This is a key limiter faced by
the goal of promoting more open and interoperable cloud
most IT organizations in achieving their virtualization goals—and
and data center solutions. Intel is also an active participant
subsequently in moving workloads to the cloud.
in the Trusted Computing Group (TCG), formed to develop
and promote open, vendor-neutral standards for trusted
Data loss or leakage. Protecting data can be a headache because of
computing building blocks; and the Distributed Management
the number of ways it can be compromised. Some data—customer,
Task Force (DMTF), a global organization leading the
employee, or financial data, for example—should be protected
development, adoption, and promotion of interoperable
from unauthorized users. But data can also be maliciously deleted,
management initiatives and standards.
altered, or unlinked from its larger context. Loss of data can damage
your company’s brand and reputation, affect customer and employee
4 Information about the Open Data Center Alliance roadmap can be found at
trust, and have regulatory compliance or competitive consequences. opendatacenteralliance.org/publications.

3 Top Threats to Cloud Computing, v1.0. Cloud Security Alliance (2010). https://cloudsecurityalliance.org/topthreats/csathreats.v1.0.pdf (PDF)


Step 1:
Start Security Planning Early
Your security profile in the cloud is defined by what your As you embark on your own cloud initiatives, here are a few of the
organization needs and the workloads you plan to move to the considerations that will affect your risk profile in the cloud.
cloud. The best way to approach cloud security is to integrate it • Are your physical compute resources located
with your overall cloud planning early in the process. That way you on-premises or off-premises?
can use a threat-based approach to planning for deployments of • What types of assets, resources, and information will
your specific workload(s), the security requirements, and the specific be managed?
cloud delivery model and architecture. • Who manages them and how?
• Which controls are selected, and how are they integrated into
the overall cloud architecture?
• What compliance issues do you face?

The Fundamentals
The first step in planning security for your proposed cloud environment is to think about the fundamentals: data and platform. Use the
following as a checklist for what you need to know (at least at a high level) about the specific deployment you’re planning. The idea
is to understand your risk tolerance, identify the best deployment models for your specific needs based on security and compliance
considerations, and detect potential exposure points for sensitive data and processes. With this information, you will be in a better position
to understand what your organization really needs.

Task Purpose Additional Considerations

Identify the business priorities You can more effectively weigh security • What drivers make cloud technology a good
for moving the specific concerns once you’ve defined the business option for this workload?
workload(s) to the cloud. context for what you hope to achieve by • Do you need to:
oo Reduce operational costs?
moving workloads to the cloud.
oo Scale seasonally?

oo Support remote or mobile workers?

Evaluate the sensitivity This helps you understand the importance of • What harm would result if the asset
of the asset(s). the data or function. You can make this was compromised?
evaluation as a rough assessment or follow a
specific valuation process.


Task Purpose Additional Considerations

Map the security workload Now that you understand the importance • Are you considering a private, public, or hybrid cloud
to the appropriate cloud of your asset, you can evaluate the risks delivery model?
delivery model and associated with various deployment models. • For a private cloud, will your deployment be:
oo On-premises?
hosting models under
oo Off-premises with a dedicated or
consideration.
shared infrastructure?
• For hybrid models, where will the various
components, functions, and data reside?
• How will you mitigate risk within the cloud
delivery model?

Determine whether the At this point, you need to understand your risk • What are the specific requirements for handling
available services are tolerance for the workload. If you have a cloud regulated data?
capable of meeting your service provider in mind, you can conduct a
requirements for handling more detailed risk assessment.
data, especially for
compliance purposes.

Map the data flow, You need to know how data moves in and out • Can the provider continue to deliver protection as
especially for public or of the cloud. For specific deployment options, the workload continues to evolve?
hybrid cloud providers. you should understand how data will flow
between your organization, the cloud services,
and any customers (or other areas).


Cloud Delivery Models at a Glance
Cloud delivery models used by enterprise organizations generally fall into three types, each with its own unique advantages and
disadvantages in terms of security.

Model Description Advantages and Disadvantages

Private • An internal infrastructure that leverages virtualization • Most control over data and platform
technology for the sole use of an enterprise behind • Potential for multitenancy of business units to cause
the firewall compliance and security risk
• Can be managed by the organization or by a third party • May lack bursting capabilities when additional performance or
• Located on-premises or off-premises on shared or capacity is required
dedicated infrastructure

Public • Resources dynamically provisioned over the Internet, via • Potential for greater cost savings if infrastructure owned and
web services, or from a third-party provider managed by public provider
• Located off-premises, typically on a shared • Loss of control of data and platform
(multitenancy) infrastructure • Potential for multitenancy with other organizations to cause
• May offer dedicated infrastructure as a response to security risk
growing security concerns • Third-party security controls possibly not transparent (and
may cause unknown risks)

Hybrid • A combination of private and public cloud services • Often a compromise:
oo Retention of control over the most mission-critical data, but
• Organizations that often maintain mission-critical
services privately with the ability to cloud burst for relinquishing that control when additional capacity or scale
additional capacity or add selective cloud services for is required during peak or seasonal periods
oo May involve retention of control for mission-critical data at
specific purposes
• Located on-premises and off-premises depending on all times while taking advantage of public cloud provider
the architecture and specific services services for less sensitive areas
• Potential for complexity to cause unknown vulnerabilities
(and unknown risks)


Intel Vision for Cloud Security

One key element of the Intel vision for cloud security is to build Intel IT uses a hybrid approach that leads with a private cloud as
in balanced controls instead of designing an environment based the core strategy. In part based on security concerns, we selectively
primarily on preventive controls. For example, the architecture is use a public cloud for nondifferentiated IT services such as staffing,
designed to dynamically adjust a user’s access privilege as the benefits, expense, stock, and travel. We host the vast majority of
level of risk changes, taking into account factors such as location our applications in our private cloud, such as enterprise, user
and type of device. This new approach is both proactive to profile management, productivity, and collaboration applications.
minimize occurrences and reactive to minimize damage if a We expect that more of our applications could burst to public
breach occurs. clouds over time as security and vendor service level agreements
(SLAs) improve and overall costs, including transition costs, become
more favorable.


Step 2: Identify Vulnerabilities
for Your Selected Service(s)
Cloud computing, which depends heavily on virtualization to realize architecture models. It’s also important to understand that while a
operational savings and efficiencies, has elastic boundaries, and fill-the-gap approach may seem to work on a particular vulnerability,
potentially pushes out the perimeter of the enterprise and security it may expose unknown vulnerabilities in other areas.
controls far beyond the data center.
Regardless of the cloud delivery model you choose, your best
It’s important to recognize that the traditional border behind which approach is to review the specific service architecture, and then
data and platform are constrained and protected—typically physical layer technologies to develop a strong security net that protects
separation and isolation—is no longer viable for dynamic cloud data, applications and platform, and network at all levels.

Spotlight on Cloud
Service Architecture5
There are three types of cloud services: infrastructure
as a service (IaaS), platform as a service (PaaS), and
software as a service (SaaS).
IaaS
• Delivers computer infrastructure as a utility service,
typically in a virtualized environment
• Provides enormous potential for extensibility and scale
PaaS
• Delivers a platform or solution stack on a cloud
infrastructure
• Sits on top of the IaaS architecture and integrates with
development and middleware capabilities as well as
database, messaging, and queuing functions
SaaS
• Delivers applications over the Internet or intranet via
a cloud infrastructure
• Built on underlying IaaS and PaaS layers

5 Security Guidance for Critical Areas of Focus in Cloud Computing, v2.1. Cloud Security Alliance (2009). https://cloudsecurityalliance.org/csaguide.pdf (PDF)


The Cloud Security Net—Build It from the Ground Up

Because the model for your cloud services may be very The following illustration shows how protection at the hardware
different from other organizations—and indeed may evolve and level can enable security deeper in the data center. Compute
change over time—Intel recommends that, in addition to security resources complement your perimeter controls, enable more
software solutions and application features, you should strengthen advanced security and compliance capabilities in existing
your security net by protecting data and platform at the most basic solutions, and provide needed protection even below the
level—the system hardware. This best practice is built into Intel’s hypervisor—an area of emerging threat.
own private cloud infrastructure.6

Physical Layers at
Risk in the Enterprise
Edge &
The dynamic perimeter of cloud Client Departmental Back-End
computing can expose edge systems Systems Systems Systems
to people and applications more
than most other elements of the
data center architectures—offering
more opportunities for compromise.
Attacks of server infrastructure at
the deepest levels are an emerging
area of risk and increasingly target
Data Center
the hypervisor, firmware, and BIOS.
The attackers are professionals—
more sophisticated, determined, and Traditional attack target Growing attack target Emerging attack target
Personal computing Departmental and other Isolated back-end servers
better resourced. The potential for
systems used to run systems that interact used for virtualization,
harm from a single attack in either of software locally or on inside and outside the database management,
these two areas can be devastating. a cloud infrastructure organization (web servers, and storage.
(desktops, laptops, and portal servers, e-mail
other mobile devices). servers, bridges, and routers).

6 An Enterprise Private Cloud Architecture and Implementation Roadmap. IT@Intel (2010). intel.com/content/www/us/en/cloud-computing/cloud-computing-private-cloud-
roadmap-paper.html (PDF)


Step 3: Four Things an IT Manager
Can Do To Mitigate Security Vulnerabilities
With protection at the hardware level, you can build trust and Intel recommends prioritizing your security investment through a
compliance into your data center. This means you can: risk assessment to determine the order and timing for building this
level of trust and compliance into your data center in four areas.
• Provide the foundation for a more powerful layered security net
of solutions and software features • Encrypt to protect data.
• Put more granular controls closer to where your data lives and
• Establish a trusted foundation to secure the platform and
critical platform services
the infrastructure.
• Trust that the physical and virtual infrastructure provisioning
your workloads is reliable • Build higher assurance into auditing to strengthen compliance.

• Trust where your servers are located • Establish and verify identities before you federate by controlling
access to trusted clients from trusted systems.
• Control where the VMs are distributed
• Complement your audit and compliance requirements (for the The remainder of this planning guide will look at how advanced
business unit tenants in your private cloud or as a tenant in a server technologies—in particular, Intel® technologies—can help
public cloud) you build trust and compliance into your data center and set the
• Protect confidential data and meet compliance requirements foundation for cloud security.

Intel IT is enabling new ways to provide the foundation for cloud
controls that can secure data and workloads. We are adding new
levels of visibility into what is running and who is running it so
you can trust that the infrastructure is reliable and can support
compliance. As Intel continues to move to the cloud, we are starting
to increase the security level of our environment through greater
understanding of what is running in the environment; what it should
look like when it is “normal”—not compromised; strengthened data
protection; and secure access.


Step 4: Protect Data—
in Motion, in Process, and at Rest
Encryption is an effective, well-established way to protect sensitive There are a number of ways to perform encryption, but typically it
data because even if information is lost, it remains unusable. comes with a cost—what is often referred to as a performance tax.
Encryption is critically important for protecting data covered by As an IT manager, you must to be able to justify the trade-off in
regulations and standards such as the Health Insurance Portability performance with the requirement for secure data.
and Accountability Act (HIPAA), Sarbanes-Oxley (SOX), and Payment
Card Industry (PCI). Increasingly, these and other regulations are
encouraging—and specifying—encryption in certain usage scenarios.
And the penalties for noncompliance are stiffer than ever.

What Types of Data Should
You Encrypt?
Data in motion
• Data in flight over networks (Internet, e-commerce, mobile
devices, automated teller machines, and so on)
• Data that uses protocols such as Secure Sockets Layer
(SSL), Transport Layer Security (TLS), Internet Protocol
Security (IPsec), Hypertext Transfer Protocol Secure
(HTTPS), FTP, and Secure Shell (SSH)
Data in process
• Transactional data in real time, such as encrypted fields,
records, rows, or column data in a database
Data at rest
• Files on computers, servers, and removable media
• Data stored using full disk encryption (FDE) and application-
level models


Encrypt without the Performance Tax

What if you didn’t have to make a performance trade-off? Intel • Improved security. The new instructions help address recently
Advanced Encryption Standard7 New Instructions (Intel AES-NI) is discovered side-channel attacks on AES. Intel AES-NI instructions
a set of seven new instructions in the Intel Xeon® processor 5600 perform the decryption and encryption more completely at the
series that eliminate the performance tax by speeding up parts hardware level without the need for software lookup tables that
of the AES algorithm encryption/decryption execution. It makes could be susceptible to snooping. Therefore using AES-NI can
encryption practical, stronger, and more efficient for data in motion, lower the risk of side-channel attacks.
in process, and at rest. • Multiple usage scenarios. Intel AES-NI can be used in any
application that uses AES, including network, disk, and file
Benefits of these hardware-based instruction set extensions encryption solutions.
include the following:
• Improved performance. Intel AES-NI can accelerate performance
3 to 10 times faster than a software-only AES solution.

7 The Advanced Encryption Standard (AES) is a popular encryption standard first adopted by the U.S. government in 2001. It is generally displacing the older, less secure
Data Encryption Standard (DES) encryption algorithm and is now widely used to protect network traffic, personal data, and corporate IT infrastructures.


Step 5:
Secure Your Platform
Rootkit attacks are increasing. They are difficult to detect with • Prove host software is good. Although the chain of trust is a
traditional antivirus products and use various methods to remain hardware-based mechanism, you can use the integrity-checking
undetected. Rootkit attacks infect system components such as data with Governance, Risk Management, and Compliance (GRC)
hypervisors and operating systems, and the malware can operate or security information and event manager (SIEM) dashboards for
in the background and spread throughout a cloud environment, audit purposes.
causing increasing damage over time.
• Respond quickly to attack and minimize damage. Detect
attacks more quickly, contain the spread of malware, and reduce
The best way to secure your platform is to enable a trusted
the need to rebuild hypervisors if a compromise is detected.
foundation—starting with a root of trust at the platform level and
extending the chain of trust through measured firmware, BIOS, and
hypervisor virtualization layers. A root of trust hardens the platform
against attack and is extremely difficult to defeat or subvert About Intel® TXT
and substantially reduces the security risks of using a remote or Intel® Trusted Execution Technology (Intel TXT) protects
virtualized infrastructure. It enables a more secure platform for against malware, key stealth attacks, and other threats by:
adding tenants and workloads. Essentially you build protection into
• Establishing a root of trust
your hardware to protect your software.
• Providing a launch environment signature to enable
trusted software launch and execution
A root of trust helps ensure system integrity within each system.
• Providing the trust foundation so that policy engines
Integrity checking is considered a key capability for software,
can restrict or allow virtual machine (VM) and data
platform, and infrastructure security.8 Intel Trusted Execution
migration based on platform security profiles
Technology (Intel TXT) checks hypervisor integrity at start-up by
• Providing the trust foundation to enable environment
measuring the code of the hypervisor and comparing it to a known
monitoring for auditing function tied to a root of trust
good value. Launch is blocked if the measurements do not match.
• Enabling an IT manager to verify that the specific
physical machine in the cloud is running the expected
The root of trust enables a trusted foundation within your cloud
operating system or hypervisor
environment so you can:
• Specify trusted server pools. You can make decisions about
how much to expose your data and workload based on whether a
trusted pool is established. The most sensitive workloads should
always use a trusted pool.

8 Evolution of Integrity Checking with Intel® Trusted Execution Technology: An Intel Perspective. IT@Intel (2010). intel.com/content/www/us/en/pc-security/intel-it-security-
trusted-execution-technology-paper.html


Step 6: Extend Trust
across Federated Clouds
As cloud computing evolves, the vision of federated clouds—across The gateway can operate as a virtualized instance and can run
which communications, data, and services can move easily within either on-premises or at a third-party hosted or managed service
and across several cloud infrastructures—adds another layer of provider. The gateway can also function as a proxy, where it
complexity to your security equation. Intel is working toward performs as a secure token service and point of policy enforcement,
providing solutions that extend trust across federated clouds via or in look-aside mode, where it passes on the identity logic to a third
secure gateways between the service provider and the service party to perform the transformations.
consumer with policy enforcement for centrally defined policies.
Intel’s partnership with McAfee delivers a coordinated security
Intel Expressway Cloud Access 360 (Intel ECA 360) is a software approach that spans network, servers, databases, storage, and data,
solution designed to control the entire life cycle of secure access as well as connecting policies and controls across physical, virtual,
for enterprises connecting to cloud environments. It serves as a and cloud infrastructures. The McAfee infrastructure proactively
gateway to broker single sign-on (SSO) access from the enterprise identifies and blocks attacks by communicating with McAfee* Global
into various clouds by authenticating employees against internal Threat Intelligence technology. The foundation of the McAfee
systems such as Active Directory* or other identity management security management platform, McAfee ePolicy Orchestrator*, is an
systems. It records the user activity against these systems, and the open, scalable platform that connects third-party security solutions
metrics can be used for audit reporting and monitoring through an to the infrastructure, strengthening protection and providing
administrative console. In addition to providing SSO, Intel ECA 360 visibility into security, compliance, and risk management activities.
creates virtual identities built from data in enterprise systems—such
as human resource applications and the telephone system—that
establish user identity and verify the trusted systems where a user
comes from.

About Intel® ECA 360
Intel® Expressway Cloud Access 360 (Intel ECA 360) provides
secure access for enterprises connecting to and across cloud
applications by:
• Account deprovisioning and account identity
data synchronization
• Enforced context-aware authorization with seamless single
sign-on (SSO) from multiple devices
• Monitoring user, administrative, and API access activity
• Soft/hard one-time password (OTP) authentication
• Activity reporting for compliance and correlation of cloud user
activity with on-premises logs for end-to-end compliance


Step 7: Choose the Right
Cloud Service Provider
Choosing a cloud service provider is complicated on many At the highest level, you need to know if the cloud provider can
levels—from the cloud delivery model and architecture to specific provide evidence of data and platform protections for the services
applications. Add to that the countless interdependencies and they provide. Once you are comfortable that your criteria can be
relationships, both technological and business-related, among met, you can establish measurable, enforceable SLAs to provide
vendors. To complicate matters, some companies offer not only ongoing verification.
software, but also hardware and services. Nevertheless, you must
be vigilant about making sure the security you need to protect your The following is a list9 of additional security considerations to think
data and platform are part of the offering. about when choosing a cloud service provider.

Security Selection Considerations
Criteria

Data center risk management • What are the patch management policies and procedures?
and security practices • How does technology architecture and infrastructure impact the cloud service provider’s ability to
meet SLAs?

Hardware-based security • Can the cloud service provider offer trusted pools for your most sensitive workloads?
• Is encryption a software-only solution?

Technology segmentation • How are systems, data, networks, management, provisioning, and personnel segmented?
• Are the controls segregating each layer of the infrastructure properly integrated so they do not
interfere with each other? For example, investigate whether the storage compartmentalization can
easily be bypassed by management tools or poor key management.
• What cloud access and identity protocols are used?

Attack response and recovery • How are attacks monitored and documented?
• How quickly can the cloud service provider respond?
• What recovery methods are used?

System availability • How does the cloud service provider handle resource democratization and dynamism to best predict
and performance proper levels of system availability and performance through normal business fluctuations?
• How does the cloud service provider measure performance?

Vendor financial stability • Is the cloud service provider financially stable?
• How long has the vendor been in business? What is their current financial standing?

9 Adapted and expanded from How to Choose a Cloud Computing Vendor. Inc.com (November 29, 2010).
inc.com/guides/2010/11/how-to-choose-a-cloud-computing-vendor.html


Security Selection Considerations
Criteria

Product long-term strategy • What is the vision for the service provider’s cloud offering?
• Does the cloud service provider have a product roadmap for their offering? Cloud service providers
seeking to provide mission-critical services should embrace the ISO/IEC 27001 standard for information
security management systems. If the provider has not achieved ISO/IEC 27001 certification, they
should demonstrate alignment with ISO 27002 practices.

Limits of responsibility • What is the limit of the cloud service provider’s responsibility for security?
• What security responsibilities are expected of the enterprise?
• What is the legal accountability in a breach?

Compliance capabilities • Does the cloud service provider have the ability to comply with regulatory requirements that you face?
• Is the cloud service provider able to provide you with full visibility into compliance-related activities?
• Can you perform your own audit?

As you and other IT managers continue to explore options for moving workloads to the cloud, security considerations will continue to
influence your buying decisions. As a result, cloud service providers are becoming more aware of the need for transparency into their
security practices.


Intel Resources for Learning More
Intel Technologies Evolution of Integrity Checking with Intel® Trusted Execution Technology: An
Intel Perspective
for Cloud Security In 2010, Intel began transitioning to a private cloud environment to improve efficiency and agility.
The highly virtualized multitenant environment creates new security challenges, including those
presented by emerging threats such as rootkit attacks. Intel evaluated Intel TXT as part of its analysis of
technologies that can potentially address these issues.
intel.com/content/www/us/en/pc-security/intel-it-security-trusted-execution-technology-paper.html

Securing the Enterprise with Intel® AES-NI
This white paper describes AES usage scenarios, performance implications, and the cryptographic
libraries that ISVs can use to replace basic AES routines with the Intel AES-NI optimizations.
intel.com/content/www/us/en/enterprise-security/enterprise-security-aes-ni-white-paper.html

Intel® Advanced Encryption Standard Instructions (AES-NI)
This article by Intel expert Jeffrey Rott is an in-depth look at using Intel AES-NI, with specific focus on
the 2010 Intel Core™ processor family and its performance and security benefits.
http://edc.intel.com/Link.aspx?id=5093

Taking Control of the Cloud for Your Enterprise: Addressing Security, Visibility, and
Governance Challenges
This white paper is for enterprise security architects and executives who need to quickly understand
the risks of moving mission-critical data, systems, and applications to external cloud providers. The
concept of a dynamic security perimeter is presented to help explain how to address insecure APIs,
multitenancy, data protection, and tiered access control for the cloud.
dynamicperimeter.com/download/Taking_Control_of_the_Cloud/?partnerref=intelsoaesite

Intel Cloud Take advantage of proven guidance for building and optimizing cloud infrastructure. Each reference
architecture is based on real-world IT requirements and gives detailed instructions on how to install and
Builders Reference configure a particular cloud solution using Intel Xeon processor–based servers and technologies.
Architectures
Intel® Cloud Builders Guide: Enhancing Server Platform Security with VMware
intel.com/content/www/us/en/cloud-computing/cloud-computing-xeon-server-platform-security-
vmware-guide.html


Intel® Cloud Builders Guide: Enhanced Cloud Security with HyTrust• and VMware•
intel.com/content/www/us/en/cloud-computing/cloud-computing-security/cloud-computing-enhanced-
cloud-security-hytrust-vmware-architecture.html

Intel® Cloud Builders Guide: Trusted Compute Pools with Parallels*
intel.com/en_US/Assets/PDF/general/icb_ra_cloud_computing_Parallels_TCP.pdf

Intel Cloud Intel® Cloud Builders—An Ecosystem of Cloud Computing Companies
A list with information about leading Intel ISV and OEM partners who perform joint, hands-on
Computing
engineering and testing to deliver proven cloud solutions and cloud services on Intel Xeon processor–
Ecosystem based servers.
intel.com/content/www/us/en/cloud-computing/cloud-builders-ecosystem-works-together.html

Additional The New Reality of Stealth Crimeware
This white paper discusses how stealth technology from sophisticated attackers, such as Stuxnet and
Resources Zeus, enables malware to launch rootkit attacks to gain intelligence or take over systems and data. The
authors describe their vision of how to fend off rootkit-style attacks: monitor operations from a vantage
point closer to and integral with the hardware.
mcafee.com/us/resources/white-papers/wp-reality-of-stealth-crimeware.pdf

Security Guidance for Critical Areas of Focus in Cloud Computing, v2.1
This Cloud Security Alliance (CSA) guide contains in-depth information to help you conduct a risk
assessment of initial cloud risks and make informed decisions about how you can adopt cloud
computing services and technologies. In addition to general guidance, the document covers 13
critical domains, including cloud computing architecture; governance and enterprise risk management;
legal and electronic discovery; compliance and audit; information life cycle management; portability
and interoperability; traditional security, business continuity, and disaster recovery; data center
operations; application security; encryption and key management; identity and access management;
and virtualization.
https://cloudsecurityalliance.org/csaguide.pdf

Top Threats to Cloud Computing, v1.0
This CSA 2010 report catalogs best practices for managing seven threats in the cloud environment.
It is designed to provide organizations with needed context to assist them in making informed risk
management decisions based on their specific cloud deployment strategies.
https://cloudsecurityalliance.org/topthreats/csathreats.v1.0.pdf


Share with Colleagues
Intel AES-NI requires a computer system with an AES-NI-enabled processor, as well as non-Intel software to execute the instructions in the correct
sequence. AES-NI is available on select Intel processors. For availability, consult your reseller or system manufacturer. For more information, see
http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/.

No computer system can provide absolute security under all conditions. Intel Trusted Execution Technology (Intel TXT) requires a computer system
with Intel Virtualization Technology, an Intel TXT–enabled processor, a chipset, a BIOS, Authenticated Code Modules, and an Intel TXT–compatible
measured launched environment (MLE). Intel TXT also requires the system to contain a TPM v1.s. For more information, visit intel.com/content/
www/us/en/data-security/security-overview-general-technology.html.

This paper is for informational purposes only. THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY
WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING
OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE. Intel disclaims all liability, including liability for infringement of any property rights, relating to
use of this information. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted herein.

Copyright © 2011 Intel Corporation. All rights reserved.

Intel, the Intel logo, Core, Xeon, Intel Sponsors of Tomorrow., and the Intel Sponsors of Tomorrow. logo are trademarks of Intel Corporation in the
U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Active Directory is a registered trademark of Microsoft Corporation in the United States and/or other countries.

0911/JM/ME/PDF-USA 325966-001 Sponsors of Tomorrow.™

Security in the cloud planning guide

More Related Content

What's hot

Viewers also liked

Similar to Security in the cloud planning guide

More from Yury Chemerkin

Security in the cloud planning guide