cloud bound

16
Featuring research from Issue 1 Cloud Bound Journey to the Private Cloud

Upload: emc-forum-india

Post on 22-Jan-2015

1.056 views

Category:

Business


1 download

DESCRIPTION

This white paper is the first in a series describing EMC IT’s initiative to move towards a private cloud-based infrastructure. It describes EMC’s IT computing strategy, how the strategy evolved, and the three steps in transitioning to the cloud. Happy reading!!!

TRANSCRIPT

Page 1: Cloud Bound

Featuring research from

Issue 1

Cloud Bound Journey to the Private Cloud

2 2

Cloud Bound

2Cloud Bound EMC WhitepaperEMC ITrsquos Journey to the Private Cloud A Practitionerrsquos Guide

12Gartner Research From Secure Virtualization to Secure Private Clouds

Executive summaryEMC is transforming its IT operations to improve its customer focus create business transformation and deliver operational efficiencies To achieve these goals EMC IT has embraced the private cloud approach to IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

By transitioning to a private cloud-based IT infrastructure and using the advanced capabilities that such an infrastructure provides EMC ITrsquos ultimate goal is to enable end-to-end on-demand self-service provisioning of IT services to its customers ndash the business units at EMC

EMC IT has been concentrating first on its internal infrastructure to prepare for the transition to the cloud ndash and virtualization is at the core of this effort in shaping the new infrastructure EMC IT has defined six key programs introduced in this white paper that are focused on the various components of the enterprise data center Each initiativersquos goal is to move EMC further along on its vision to build integrated infrastructures for virtualization at scale Separate papers describing each initiative in detail are currently being developed to provide more information on EMC ITrsquos respective strategies in moving toward a cloud-based IT infrastructure

In parallel EMC IT is developing policies and governance mechanisms for managing the new IT services paradigm EMC IT has also designed frameworks for preparing the organization at various levels to achieve the transition to the private cloud

EMC ITrsquos structured approach helps accelerate its journey to the private cloud by enabling the organization to get started with cloud initiatives versus waiting for complete solutions to emerge By building solutions using existing technologies ndash in line with global trends ndash EMC IT hopes to adapt them to new technologies when they become available

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million of operating cost reduction due to increased data center power cooling and space efficiency

In addition EMC expects to increase its storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

Cloud Bound is published by EMC Editorial supplied by EMC is independent of Gartner analysis All Gartner research is copy 2011 by Gartner Inc All rights reserved All Gartner materials are used with Gartnerrsquos permission The use or publication of Gartner research does not indicate Gartnerrsquos endorsement of EMCrsquos products andor strategies Reproduction or distribution of this publication in any form without prior written permission is forbidden The information contained herein has been obtained from sources believed to be reliable Gartner disclaims all warranties as to the accuracy completeness or adequacy of such information Gartner shall have no liability for errors omissions or inadequacies in the information contained herein or for interpretations thereof The opinions expressed herein are subject to change without notice Although Gartner research may include a discussion of related legal issues Gartner does not provide legal advice or services and its research should not be construed or used as such Gartner is a public company and its shareholders may include firms and funds that have financial interests in entities covered in Gartner research Gartnerrsquos Board of Directors may include senior managers of these firms or funds Gartner research is produced independently by its research organization without input or influence from these firms funds or their managers For further information on the independence and integrity of Gartner research see ldquoGuiding Principles on Independence and Objectivityrdquo on its website httpwwwgartnercomtechnologyaboutombudsmanomb_guide2jsp

3

3

Curabitur at nibh

Consectetuer adipiscing elit tortor lacus nonummy purus

IntroductionThis white paper includes the following sections

bull ldquoAnintroductiontoEMCITrdquoonpage3

bull ldquoEMCITrsquoscloudcomputingstrategyakeyto realizing IT prioritiesrdquo on page 4

bull ldquoMakingthetransitiontotheprivatecloudrdquoon page 4

This white paper is the first in a series describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure It describes EMC ITrsquos cloud computing strategy how the strategy evolved and the three steps in transitioning to the cloud

The paper also introduces the six key programs and the use case that helped EMC move toward an integrated infrastructure for virtualization

Audience

This white paper is intended for IT program managers IT architects and IT management

An introduction to EMC IT EMC the worldrsquos leading developer and provider of information infrastructure technology and solutions has a large internal IT organization that supports the business operations of its global workforce EMC IT supports nearly 50000 users across over 80 countries and in excess of 400 business applications Like all IT organizations EMC IT faces the challenge of balancing cost risk and agility in its operations The functionality interoperability and performance requirements of its internal customers must be satisfied ndash without compromising the security and manageability of IT systems and processes EMC IT must also justify all of its investments with strong metrics-based business cases that demonstrate return on investment (ROI) and total cost of ownership (TCO) before receiving management approvals

Principles and priorities

EMC ITrsquos vision is based on three guiding principles operational efficiency business

transformation and customer focus Making that vision a reality requires attention to the following priorities

bull Reduce operational costs ndash Helping business units lower the overall cost of operations by reducing IT operational costs

bull Improve agility of IT delivery ndash Increasing the flexibility of IT systems and processes to meet the changing needs of business units in the shortest possible time

bull Drive workforce productivity ndash Increasing global employee productivity through innovative applications and investing in communication and collaboration technologies such as social computing and telepresence

bull Architect for the future ndash Making IT investments toward architecting the desired future state ndash as well as future-proofing solutions so they accommodate future requirements and changes

bull Implement IT-proven solutions ndash Enabling the development of the highest-quality EMC products by serving as a live production testbed for EMC technology and driving customer orientation through use of the technology being developed EMC IT also publishes documents internally that describe the challenges faced in using new EMC technology and how users have overcome these challenges

EMC IT believes a key component of satisfying its priorities is the private cloud

Source EMC

FIguRE 1EMCrsquos guiding principles and top IT priorities

Operational Efficiency

Business Transformation

Customer Focus

Reduce operational costs 1

Improve agility of IT delivery 2

Drive workforce productivity 3

Architect for the future 4

Implement EMC ldquoIT Provenrdquo solutions 5

Guiding Principles

In line with its Vision of Enabling Customerrsquos Journey to the Private Cloud EMC has launched the Industryrsquos first Cloud Architect Certification Program

It is ideal to address cloud requirements when planning extensive virtualized environment to avoid potentially costly rework For that reason forming a team of experienced architects is a priority on the Journey to the Cloud

You can now build your team of trusted advisors with Certified Cloud Architects (EMCCA) and Data Center Arhictects (EMCDCA) certification program

Please find more information on httpeducationemccom

4

EMC ITrsquos cloud computing strategy a key to realizing IT prioritiesEMC IT has embarked on a bold mission to move to a private cloud-based infrastructure EMC defines the private cloud as the next-generation IT infrastructure that provides all of the benefits of cloud-based IT systems (for example quality of service (QoS) performance scalability security and management) even as it retains complete control of the IT infrastructure A private cloud may use internal resources (internal cloud) external resources (external cloud delivered via service providers in the public cloud) or a combination of both as shown in Figure 2

Cloud computing enables EMC to create an elastic agile environment that provides business units with the ability to scale their IT resource requirements based on actual needs Resource utilization is improved by provisioning the infrastructure for normal rather than peak loads with greater agility By using the services of external cloud service providers and third parties cloud-based IT can transform fixed costs into variable costs This model also offers the benefits

of increased choice self-provisioning and utility-based chargeback models as well as the benefits of next-generation security compliance and service delivery management

EMC IT believes cloud computing has a few differentiating characteristics

bull IT is built differently using pooled architectures with defined service catalogs for each IT service and the ability to partitionmove workloads to where they can best run

bull IT is run differently by using low- and zero-touch modes for IT operations provisioning and management

bull IT is consumed differently where end consumers of IT services can benefit from on-demand provisioning of IT based on immediate requirements and from multiple IT service providers

bull IT is governed differently from QoS for services to security as new sets of rules and roles emerge

Transitioning to a cloud-based model provides the IT organization with the benefits of flexibility efficiency and dynamic on-demand resource allocation However the IT organization may need to divest some of the control and choice of IT components to a third-party provider of cloud services if external service providers are involved It is in this context that EMCrsquos governance model in the cloud environment becomes more significant

EMC believes that the capabilities of the private cloud will first evolve in the internal cloud and then federate out into the external and partner clouds The private cloud has to integrate with the public cloud (for example Salesforcecom) and thereby EMC ITrsquos cloud strategy includes private as well as public cloud

EMC ITrsquos evolution in the journey to the private cloudThe internal data center is at the core of EMCrsquos vision of the private cloud Virtualization is a key enabling technology of the private cloud Virtualization is the ability to increase the utilization of physical resources through techniques such as pooling and multiplexing The evolution to the cloud begins by using virtualization effectively across all components of the data center infrastructure namely systems storage network security monitoring and management the application stack ndash all the way up to the desktop

Figure 3 illustrates this evolution which involves redefining the IT organizationrsquos mandate from being a provider of stand-alone components to being a provider of fully integrated tested validated and ready-to-grow infrastructure and application packages that contain best-in-class components for a data center The platform adopted by EMC IT is based on the x86 architecture with 100 percent virtualization leveraging VMware vSpheretrade

The end goal of EMC ITrsquos transition to the private cloud is to achieve the ability to offer IT as a service to internal customers ndash the business units at EMC ndash with options for self-provisioning through a portal interface Source EMC

FIguRE 2EMC ITrsquos cloud strategy

5

5

Source EMC

FIguRE 3EMC ITrsquos evolution in the journey to the private cloud

In this model IT is more than a supplier ndash IT becomes a business partner ndash and both IT and the business benefit With access to IT as a service the business benefits from the following

bull Simplicityofself-serviceaccess

bull Alignmentofcostswithutilitywithapay-for-use utility model

bull Agilityforfastertime-to-marketandtheflexibility to change

bull Auser-centricoutcome-basedapproachto supporting business goals

The benefits for IT include efficiency through automation of tasks to do more faster elasticity to acquire deploy change or release on-demand greater visibility into costs and control over service levels for better responsiveness and greater control over the IT environment

EMC IT is starting to offer services at various levels

bull Infrastructure as a Service (IaaS) offers EMC business units the ability to provision infrastructure components such as network storage compute and operating systems as a service

bull Platform as a Service (PaaS) provides the application and information frameworks on top of application server web server and database components as a service to business units from which to develop solutions

bull Software as a Service (SaaS) provides applications and tools in a services model for business enablement

The next step in the journey is the ability to achieve federation of data and resources between data centers beginning with internal virtual data centers and going on to federation between internal and external clouds The aim is to equip the IT organization with the capabilities to move data and resources between internal and third-party data centers to achieve the real benefits of elastic IT provisioning EMC IT recommends that to manage the progression shown in

the previous figure it is necessary to set up a roadmap as shown in Figure 4 that further develops the components of the ecosystem

EMC ITrsquos roadmap of the transition to the private cloud

Planning the transition to the cloud

EMC believes that in order to transform the IT organization it isnrsquot enough to just concentrate on changing the technology aspects An IT transformation initiative must address five perspectives

bull Technology

bull Businesscapabilitiesandexperience

bull People

bull Operations

bull ITpoliciesprocessgovernance

Moreover it is essential not to just consider these elements in isolation but to assess and plan for the complex interactions among them In line with the components of an IT transformation initiative EMC believes there are essentially three stages of adoption for organizations that are considering a private cloud strategy at the enterprise level and are at various stages They are as follows

bull TheITProductionstagewhichtargetsdevtestIT applications for virtualization to achieve cost efficiencies Key capabilities leveraged include shared resource pools and elastic capacity

bull TheBusinessProductionstagewhichenables business applications including mission-critical applications with an emphasis on high QoS Key capabilities leveraged include a zero-touch infrastructure and increased control combined with service assurance

bull TheIT-as-a-Servicestagewhichemphasizes business agility Key capabilities include service definition service catalog self-service and chargeback

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 2: Cloud Bound

2 2

Cloud Bound

2Cloud Bound EMC WhitepaperEMC ITrsquos Journey to the Private Cloud A Practitionerrsquos Guide

12Gartner Research From Secure Virtualization to Secure Private Clouds

Executive summaryEMC is transforming its IT operations to improve its customer focus create business transformation and deliver operational efficiencies To achieve these goals EMC IT has embraced the private cloud approach to IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

By transitioning to a private cloud-based IT infrastructure and using the advanced capabilities that such an infrastructure provides EMC ITrsquos ultimate goal is to enable end-to-end on-demand self-service provisioning of IT services to its customers ndash the business units at EMC

EMC IT has been concentrating first on its internal infrastructure to prepare for the transition to the cloud ndash and virtualization is at the core of this effort in shaping the new infrastructure EMC IT has defined six key programs introduced in this white paper that are focused on the various components of the enterprise data center Each initiativersquos goal is to move EMC further along on its vision to build integrated infrastructures for virtualization at scale Separate papers describing each initiative in detail are currently being developed to provide more information on EMC ITrsquos respective strategies in moving toward a cloud-based IT infrastructure

In parallel EMC IT is developing policies and governance mechanisms for managing the new IT services paradigm EMC IT has also designed frameworks for preparing the organization at various levels to achieve the transition to the private cloud

EMC ITrsquos structured approach helps accelerate its journey to the private cloud by enabling the organization to get started with cloud initiatives versus waiting for complete solutions to emerge By building solutions using existing technologies ndash in line with global trends ndash EMC IT hopes to adapt them to new technologies when they become available

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million of operating cost reduction due to increased data center power cooling and space efficiency

In addition EMC expects to increase its storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

Cloud Bound is published by EMC Editorial supplied by EMC is independent of Gartner analysis All Gartner research is copy 2011 by Gartner Inc All rights reserved All Gartner materials are used with Gartnerrsquos permission The use or publication of Gartner research does not indicate Gartnerrsquos endorsement of EMCrsquos products andor strategies Reproduction or distribution of this publication in any form without prior written permission is forbidden The information contained herein has been obtained from sources believed to be reliable Gartner disclaims all warranties as to the accuracy completeness or adequacy of such information Gartner shall have no liability for errors omissions or inadequacies in the information contained herein or for interpretations thereof The opinions expressed herein are subject to change without notice Although Gartner research may include a discussion of related legal issues Gartner does not provide legal advice or services and its research should not be construed or used as such Gartner is a public company and its shareholders may include firms and funds that have financial interests in entities covered in Gartner research Gartnerrsquos Board of Directors may include senior managers of these firms or funds Gartner research is produced independently by its research organization without input or influence from these firms funds or their managers For further information on the independence and integrity of Gartner research see ldquoGuiding Principles on Independence and Objectivityrdquo on its website httpwwwgartnercomtechnologyaboutombudsmanomb_guide2jsp

3

3

Curabitur at nibh

Consectetuer adipiscing elit tortor lacus nonummy purus

IntroductionThis white paper includes the following sections

bull ldquoAnintroductiontoEMCITrdquoonpage3

bull ldquoEMCITrsquoscloudcomputingstrategyakeyto realizing IT prioritiesrdquo on page 4

bull ldquoMakingthetransitiontotheprivatecloudrdquoon page 4

This white paper is the first in a series describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure It describes EMC ITrsquos cloud computing strategy how the strategy evolved and the three steps in transitioning to the cloud

The paper also introduces the six key programs and the use case that helped EMC move toward an integrated infrastructure for virtualization

Audience

This white paper is intended for IT program managers IT architects and IT management

An introduction to EMC IT EMC the worldrsquos leading developer and provider of information infrastructure technology and solutions has a large internal IT organization that supports the business operations of its global workforce EMC IT supports nearly 50000 users across over 80 countries and in excess of 400 business applications Like all IT organizations EMC IT faces the challenge of balancing cost risk and agility in its operations The functionality interoperability and performance requirements of its internal customers must be satisfied ndash without compromising the security and manageability of IT systems and processes EMC IT must also justify all of its investments with strong metrics-based business cases that demonstrate return on investment (ROI) and total cost of ownership (TCO) before receiving management approvals

Principles and priorities

EMC ITrsquos vision is based on three guiding principles operational efficiency business

transformation and customer focus Making that vision a reality requires attention to the following priorities

bull Reduce operational costs ndash Helping business units lower the overall cost of operations by reducing IT operational costs

bull Improve agility of IT delivery ndash Increasing the flexibility of IT systems and processes to meet the changing needs of business units in the shortest possible time

bull Drive workforce productivity ndash Increasing global employee productivity through innovative applications and investing in communication and collaboration technologies such as social computing and telepresence

bull Architect for the future ndash Making IT investments toward architecting the desired future state ndash as well as future-proofing solutions so they accommodate future requirements and changes

bull Implement IT-proven solutions ndash Enabling the development of the highest-quality EMC products by serving as a live production testbed for EMC technology and driving customer orientation through use of the technology being developed EMC IT also publishes documents internally that describe the challenges faced in using new EMC technology and how users have overcome these challenges

EMC IT believes a key component of satisfying its priorities is the private cloud

Source EMC

FIguRE 1EMCrsquos guiding principles and top IT priorities

Operational Efficiency

Business Transformation

Customer Focus

Reduce operational costs 1

Improve agility of IT delivery 2

Drive workforce productivity 3

Architect for the future 4

Implement EMC ldquoIT Provenrdquo solutions 5

Guiding Principles

In line with its Vision of Enabling Customerrsquos Journey to the Private Cloud EMC has launched the Industryrsquos first Cloud Architect Certification Program

It is ideal to address cloud requirements when planning extensive virtualized environment to avoid potentially costly rework For that reason forming a team of experienced architects is a priority on the Journey to the Cloud

You can now build your team of trusted advisors with Certified Cloud Architects (EMCCA) and Data Center Arhictects (EMCDCA) certification program

Please find more information on httpeducationemccom

4

EMC ITrsquos cloud computing strategy a key to realizing IT prioritiesEMC IT has embarked on a bold mission to move to a private cloud-based infrastructure EMC defines the private cloud as the next-generation IT infrastructure that provides all of the benefits of cloud-based IT systems (for example quality of service (QoS) performance scalability security and management) even as it retains complete control of the IT infrastructure A private cloud may use internal resources (internal cloud) external resources (external cloud delivered via service providers in the public cloud) or a combination of both as shown in Figure 2

Cloud computing enables EMC to create an elastic agile environment that provides business units with the ability to scale their IT resource requirements based on actual needs Resource utilization is improved by provisioning the infrastructure for normal rather than peak loads with greater agility By using the services of external cloud service providers and third parties cloud-based IT can transform fixed costs into variable costs This model also offers the benefits

of increased choice self-provisioning and utility-based chargeback models as well as the benefits of next-generation security compliance and service delivery management

EMC IT believes cloud computing has a few differentiating characteristics

bull IT is built differently using pooled architectures with defined service catalogs for each IT service and the ability to partitionmove workloads to where they can best run

bull IT is run differently by using low- and zero-touch modes for IT operations provisioning and management

bull IT is consumed differently where end consumers of IT services can benefit from on-demand provisioning of IT based on immediate requirements and from multiple IT service providers

bull IT is governed differently from QoS for services to security as new sets of rules and roles emerge

Transitioning to a cloud-based model provides the IT organization with the benefits of flexibility efficiency and dynamic on-demand resource allocation However the IT organization may need to divest some of the control and choice of IT components to a third-party provider of cloud services if external service providers are involved It is in this context that EMCrsquos governance model in the cloud environment becomes more significant

EMC believes that the capabilities of the private cloud will first evolve in the internal cloud and then federate out into the external and partner clouds The private cloud has to integrate with the public cloud (for example Salesforcecom) and thereby EMC ITrsquos cloud strategy includes private as well as public cloud

EMC ITrsquos evolution in the journey to the private cloudThe internal data center is at the core of EMCrsquos vision of the private cloud Virtualization is a key enabling technology of the private cloud Virtualization is the ability to increase the utilization of physical resources through techniques such as pooling and multiplexing The evolution to the cloud begins by using virtualization effectively across all components of the data center infrastructure namely systems storage network security monitoring and management the application stack ndash all the way up to the desktop

Figure 3 illustrates this evolution which involves redefining the IT organizationrsquos mandate from being a provider of stand-alone components to being a provider of fully integrated tested validated and ready-to-grow infrastructure and application packages that contain best-in-class components for a data center The platform adopted by EMC IT is based on the x86 architecture with 100 percent virtualization leveraging VMware vSpheretrade

The end goal of EMC ITrsquos transition to the private cloud is to achieve the ability to offer IT as a service to internal customers ndash the business units at EMC ndash with options for self-provisioning through a portal interface Source EMC

FIguRE 2EMC ITrsquos cloud strategy

5

5

Source EMC

FIguRE 3EMC ITrsquos evolution in the journey to the private cloud

In this model IT is more than a supplier ndash IT becomes a business partner ndash and both IT and the business benefit With access to IT as a service the business benefits from the following

bull Simplicityofself-serviceaccess

bull Alignmentofcostswithutilitywithapay-for-use utility model

bull Agilityforfastertime-to-marketandtheflexibility to change

bull Auser-centricoutcome-basedapproachto supporting business goals

The benefits for IT include efficiency through automation of tasks to do more faster elasticity to acquire deploy change or release on-demand greater visibility into costs and control over service levels for better responsiveness and greater control over the IT environment

EMC IT is starting to offer services at various levels

bull Infrastructure as a Service (IaaS) offers EMC business units the ability to provision infrastructure components such as network storage compute and operating systems as a service

bull Platform as a Service (PaaS) provides the application and information frameworks on top of application server web server and database components as a service to business units from which to develop solutions

bull Software as a Service (SaaS) provides applications and tools in a services model for business enablement

The next step in the journey is the ability to achieve federation of data and resources between data centers beginning with internal virtual data centers and going on to federation between internal and external clouds The aim is to equip the IT organization with the capabilities to move data and resources between internal and third-party data centers to achieve the real benefits of elastic IT provisioning EMC IT recommends that to manage the progression shown in

the previous figure it is necessary to set up a roadmap as shown in Figure 4 that further develops the components of the ecosystem

EMC ITrsquos roadmap of the transition to the private cloud

Planning the transition to the cloud

EMC believes that in order to transform the IT organization it isnrsquot enough to just concentrate on changing the technology aspects An IT transformation initiative must address five perspectives

bull Technology

bull Businesscapabilitiesandexperience

bull People

bull Operations

bull ITpoliciesprocessgovernance

Moreover it is essential not to just consider these elements in isolation but to assess and plan for the complex interactions among them In line with the components of an IT transformation initiative EMC believes there are essentially three stages of adoption for organizations that are considering a private cloud strategy at the enterprise level and are at various stages They are as follows

bull TheITProductionstagewhichtargetsdevtestIT applications for virtualization to achieve cost efficiencies Key capabilities leveraged include shared resource pools and elastic capacity

bull TheBusinessProductionstagewhichenables business applications including mission-critical applications with an emphasis on high QoS Key capabilities leveraged include a zero-touch infrastructure and increased control combined with service assurance

bull TheIT-as-a-Servicestagewhichemphasizes business agility Key capabilities include service definition service catalog self-service and chargeback

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 3: Cloud Bound

3

3

Curabitur at nibh

Consectetuer adipiscing elit tortor lacus nonummy purus

IntroductionThis white paper includes the following sections

bull ldquoAnintroductiontoEMCITrdquoonpage3

bull ldquoEMCITrsquoscloudcomputingstrategyakeyto realizing IT prioritiesrdquo on page 4

bull ldquoMakingthetransitiontotheprivatecloudrdquoon page 4

This white paper is the first in a series describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure It describes EMC ITrsquos cloud computing strategy how the strategy evolved and the three steps in transitioning to the cloud

The paper also introduces the six key programs and the use case that helped EMC move toward an integrated infrastructure for virtualization

Audience

This white paper is intended for IT program managers IT architects and IT management

An introduction to EMC IT EMC the worldrsquos leading developer and provider of information infrastructure technology and solutions has a large internal IT organization that supports the business operations of its global workforce EMC IT supports nearly 50000 users across over 80 countries and in excess of 400 business applications Like all IT organizations EMC IT faces the challenge of balancing cost risk and agility in its operations The functionality interoperability and performance requirements of its internal customers must be satisfied ndash without compromising the security and manageability of IT systems and processes EMC IT must also justify all of its investments with strong metrics-based business cases that demonstrate return on investment (ROI) and total cost of ownership (TCO) before receiving management approvals

Principles and priorities

EMC ITrsquos vision is based on three guiding principles operational efficiency business

transformation and customer focus Making that vision a reality requires attention to the following priorities

bull Reduce operational costs ndash Helping business units lower the overall cost of operations by reducing IT operational costs

bull Improve agility of IT delivery ndash Increasing the flexibility of IT systems and processes to meet the changing needs of business units in the shortest possible time

bull Drive workforce productivity ndash Increasing global employee productivity through innovative applications and investing in communication and collaboration technologies such as social computing and telepresence

bull Architect for the future ndash Making IT investments toward architecting the desired future state ndash as well as future-proofing solutions so they accommodate future requirements and changes

bull Implement IT-proven solutions ndash Enabling the development of the highest-quality EMC products by serving as a live production testbed for EMC technology and driving customer orientation through use of the technology being developed EMC IT also publishes documents internally that describe the challenges faced in using new EMC technology and how users have overcome these challenges

EMC IT believes a key component of satisfying its priorities is the private cloud

Source EMC

FIguRE 1EMCrsquos guiding principles and top IT priorities

Operational Efficiency

Business Transformation

Customer Focus

Reduce operational costs 1

Improve agility of IT delivery 2

Drive workforce productivity 3

Architect for the future 4

Implement EMC ldquoIT Provenrdquo solutions 5

Guiding Principles

In line with its Vision of Enabling Customerrsquos Journey to the Private Cloud EMC has launched the Industryrsquos first Cloud Architect Certification Program

It is ideal to address cloud requirements when planning extensive virtualized environment to avoid potentially costly rework For that reason forming a team of experienced architects is a priority on the Journey to the Cloud

You can now build your team of trusted advisors with Certified Cloud Architects (EMCCA) and Data Center Arhictects (EMCDCA) certification program

Please find more information on httpeducationemccom

4

EMC ITrsquos cloud computing strategy a key to realizing IT prioritiesEMC IT has embarked on a bold mission to move to a private cloud-based infrastructure EMC defines the private cloud as the next-generation IT infrastructure that provides all of the benefits of cloud-based IT systems (for example quality of service (QoS) performance scalability security and management) even as it retains complete control of the IT infrastructure A private cloud may use internal resources (internal cloud) external resources (external cloud delivered via service providers in the public cloud) or a combination of both as shown in Figure 2

Cloud computing enables EMC to create an elastic agile environment that provides business units with the ability to scale their IT resource requirements based on actual needs Resource utilization is improved by provisioning the infrastructure for normal rather than peak loads with greater agility By using the services of external cloud service providers and third parties cloud-based IT can transform fixed costs into variable costs This model also offers the benefits

of increased choice self-provisioning and utility-based chargeback models as well as the benefits of next-generation security compliance and service delivery management

EMC IT believes cloud computing has a few differentiating characteristics

bull IT is built differently using pooled architectures with defined service catalogs for each IT service and the ability to partitionmove workloads to where they can best run

bull IT is run differently by using low- and zero-touch modes for IT operations provisioning and management

bull IT is consumed differently where end consumers of IT services can benefit from on-demand provisioning of IT based on immediate requirements and from multiple IT service providers

bull IT is governed differently from QoS for services to security as new sets of rules and roles emerge

Transitioning to a cloud-based model provides the IT organization with the benefits of flexibility efficiency and dynamic on-demand resource allocation However the IT organization may need to divest some of the control and choice of IT components to a third-party provider of cloud services if external service providers are involved It is in this context that EMCrsquos governance model in the cloud environment becomes more significant

EMC believes that the capabilities of the private cloud will first evolve in the internal cloud and then federate out into the external and partner clouds The private cloud has to integrate with the public cloud (for example Salesforcecom) and thereby EMC ITrsquos cloud strategy includes private as well as public cloud

EMC ITrsquos evolution in the journey to the private cloudThe internal data center is at the core of EMCrsquos vision of the private cloud Virtualization is a key enabling technology of the private cloud Virtualization is the ability to increase the utilization of physical resources through techniques such as pooling and multiplexing The evolution to the cloud begins by using virtualization effectively across all components of the data center infrastructure namely systems storage network security monitoring and management the application stack ndash all the way up to the desktop

Figure 3 illustrates this evolution which involves redefining the IT organizationrsquos mandate from being a provider of stand-alone components to being a provider of fully integrated tested validated and ready-to-grow infrastructure and application packages that contain best-in-class components for a data center The platform adopted by EMC IT is based on the x86 architecture with 100 percent virtualization leveraging VMware vSpheretrade

The end goal of EMC ITrsquos transition to the private cloud is to achieve the ability to offer IT as a service to internal customers ndash the business units at EMC ndash with options for self-provisioning through a portal interface Source EMC

FIguRE 2EMC ITrsquos cloud strategy

5

5

Source EMC

FIguRE 3EMC ITrsquos evolution in the journey to the private cloud

In this model IT is more than a supplier ndash IT becomes a business partner ndash and both IT and the business benefit With access to IT as a service the business benefits from the following

bull Simplicityofself-serviceaccess

bull Alignmentofcostswithutilitywithapay-for-use utility model

bull Agilityforfastertime-to-marketandtheflexibility to change

bull Auser-centricoutcome-basedapproachto supporting business goals

The benefits for IT include efficiency through automation of tasks to do more faster elasticity to acquire deploy change or release on-demand greater visibility into costs and control over service levels for better responsiveness and greater control over the IT environment

EMC IT is starting to offer services at various levels

bull Infrastructure as a Service (IaaS) offers EMC business units the ability to provision infrastructure components such as network storage compute and operating systems as a service

bull Platform as a Service (PaaS) provides the application and information frameworks on top of application server web server and database components as a service to business units from which to develop solutions

bull Software as a Service (SaaS) provides applications and tools in a services model for business enablement

The next step in the journey is the ability to achieve federation of data and resources between data centers beginning with internal virtual data centers and going on to federation between internal and external clouds The aim is to equip the IT organization with the capabilities to move data and resources between internal and third-party data centers to achieve the real benefits of elastic IT provisioning EMC IT recommends that to manage the progression shown in

the previous figure it is necessary to set up a roadmap as shown in Figure 4 that further develops the components of the ecosystem

EMC ITrsquos roadmap of the transition to the private cloud

Planning the transition to the cloud

EMC believes that in order to transform the IT organization it isnrsquot enough to just concentrate on changing the technology aspects An IT transformation initiative must address five perspectives

bull Technology

bull Businesscapabilitiesandexperience

bull People

bull Operations

bull ITpoliciesprocessgovernance

Moreover it is essential not to just consider these elements in isolation but to assess and plan for the complex interactions among them In line with the components of an IT transformation initiative EMC believes there are essentially three stages of adoption for organizations that are considering a private cloud strategy at the enterprise level and are at various stages They are as follows

bull TheITProductionstagewhichtargetsdevtestIT applications for virtualization to achieve cost efficiencies Key capabilities leveraged include shared resource pools and elastic capacity

bull TheBusinessProductionstagewhichenables business applications including mission-critical applications with an emphasis on high QoS Key capabilities leveraged include a zero-touch infrastructure and increased control combined with service assurance

bull TheIT-as-a-Servicestagewhichemphasizes business agility Key capabilities include service definition service catalog self-service and chargeback

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 4: Cloud Bound

4

EMC ITrsquos cloud computing strategy a key to realizing IT prioritiesEMC IT has embarked on a bold mission to move to a private cloud-based infrastructure EMC defines the private cloud as the next-generation IT infrastructure that provides all of the benefits of cloud-based IT systems (for example quality of service (QoS) performance scalability security and management) even as it retains complete control of the IT infrastructure A private cloud may use internal resources (internal cloud) external resources (external cloud delivered via service providers in the public cloud) or a combination of both as shown in Figure 2

Cloud computing enables EMC to create an elastic agile environment that provides business units with the ability to scale their IT resource requirements based on actual needs Resource utilization is improved by provisioning the infrastructure for normal rather than peak loads with greater agility By using the services of external cloud service providers and third parties cloud-based IT can transform fixed costs into variable costs This model also offers the benefits

of increased choice self-provisioning and utility-based chargeback models as well as the benefits of next-generation security compliance and service delivery management

EMC IT believes cloud computing has a few differentiating characteristics

bull IT is built differently using pooled architectures with defined service catalogs for each IT service and the ability to partitionmove workloads to where they can best run

bull IT is run differently by using low- and zero-touch modes for IT operations provisioning and management

bull IT is consumed differently where end consumers of IT services can benefit from on-demand provisioning of IT based on immediate requirements and from multiple IT service providers

bull IT is governed differently from QoS for services to security as new sets of rules and roles emerge

Transitioning to a cloud-based model provides the IT organization with the benefits of flexibility efficiency and dynamic on-demand resource allocation However the IT organization may need to divest some of the control and choice of IT components to a third-party provider of cloud services if external service providers are involved It is in this context that EMCrsquos governance model in the cloud environment becomes more significant

EMC believes that the capabilities of the private cloud will first evolve in the internal cloud and then federate out into the external and partner clouds The private cloud has to integrate with the public cloud (for example Salesforcecom) and thereby EMC ITrsquos cloud strategy includes private as well as public cloud

EMC ITrsquos evolution in the journey to the private cloudThe internal data center is at the core of EMCrsquos vision of the private cloud Virtualization is a key enabling technology of the private cloud Virtualization is the ability to increase the utilization of physical resources through techniques such as pooling and multiplexing The evolution to the cloud begins by using virtualization effectively across all components of the data center infrastructure namely systems storage network security monitoring and management the application stack ndash all the way up to the desktop

Figure 3 illustrates this evolution which involves redefining the IT organizationrsquos mandate from being a provider of stand-alone components to being a provider of fully integrated tested validated and ready-to-grow infrastructure and application packages that contain best-in-class components for a data center The platform adopted by EMC IT is based on the x86 architecture with 100 percent virtualization leveraging VMware vSpheretrade

The end goal of EMC ITrsquos transition to the private cloud is to achieve the ability to offer IT as a service to internal customers ndash the business units at EMC ndash with options for self-provisioning through a portal interface Source EMC

FIguRE 2EMC ITrsquos cloud strategy

5

5

Source EMC

FIguRE 3EMC ITrsquos evolution in the journey to the private cloud

In this model IT is more than a supplier ndash IT becomes a business partner ndash and both IT and the business benefit With access to IT as a service the business benefits from the following

bull Simplicityofself-serviceaccess

bull Alignmentofcostswithutilitywithapay-for-use utility model

bull Agilityforfastertime-to-marketandtheflexibility to change

bull Auser-centricoutcome-basedapproachto supporting business goals

The benefits for IT include efficiency through automation of tasks to do more faster elasticity to acquire deploy change or release on-demand greater visibility into costs and control over service levels for better responsiveness and greater control over the IT environment

EMC IT is starting to offer services at various levels

bull Infrastructure as a Service (IaaS) offers EMC business units the ability to provision infrastructure components such as network storage compute and operating systems as a service

bull Platform as a Service (PaaS) provides the application and information frameworks on top of application server web server and database components as a service to business units from which to develop solutions

bull Software as a Service (SaaS) provides applications and tools in a services model for business enablement

The next step in the journey is the ability to achieve federation of data and resources between data centers beginning with internal virtual data centers and going on to federation between internal and external clouds The aim is to equip the IT organization with the capabilities to move data and resources between internal and third-party data centers to achieve the real benefits of elastic IT provisioning EMC IT recommends that to manage the progression shown in

the previous figure it is necessary to set up a roadmap as shown in Figure 4 that further develops the components of the ecosystem

EMC ITrsquos roadmap of the transition to the private cloud

Planning the transition to the cloud

EMC believes that in order to transform the IT organization it isnrsquot enough to just concentrate on changing the technology aspects An IT transformation initiative must address five perspectives

bull Technology

bull Businesscapabilitiesandexperience

bull People

bull Operations

bull ITpoliciesprocessgovernance

Moreover it is essential not to just consider these elements in isolation but to assess and plan for the complex interactions among them In line with the components of an IT transformation initiative EMC believes there are essentially three stages of adoption for organizations that are considering a private cloud strategy at the enterprise level and are at various stages They are as follows

bull TheITProductionstagewhichtargetsdevtestIT applications for virtualization to achieve cost efficiencies Key capabilities leveraged include shared resource pools and elastic capacity

bull TheBusinessProductionstagewhichenables business applications including mission-critical applications with an emphasis on high QoS Key capabilities leveraged include a zero-touch infrastructure and increased control combined with service assurance

bull TheIT-as-a-Servicestagewhichemphasizes business agility Key capabilities include service definition service catalog self-service and chargeback

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 5: Cloud Bound

5

5

Source EMC

FIguRE 3EMC ITrsquos evolution in the journey to the private cloud

In this model IT is more than a supplier ndash IT becomes a business partner ndash and both IT and the business benefit With access to IT as a service the business benefits from the following

bull Simplicityofself-serviceaccess

bull Alignmentofcostswithutilitywithapay-for-use utility model

bull Agilityforfastertime-to-marketandtheflexibility to change

bull Auser-centricoutcome-basedapproachto supporting business goals

The benefits for IT include efficiency through automation of tasks to do more faster elasticity to acquire deploy change or release on-demand greater visibility into costs and control over service levels for better responsiveness and greater control over the IT environment

EMC IT is starting to offer services at various levels

bull Infrastructure as a Service (IaaS) offers EMC business units the ability to provision infrastructure components such as network storage compute and operating systems as a service

bull Platform as a Service (PaaS) provides the application and information frameworks on top of application server web server and database components as a service to business units from which to develop solutions

bull Software as a Service (SaaS) provides applications and tools in a services model for business enablement

The next step in the journey is the ability to achieve federation of data and resources between data centers beginning with internal virtual data centers and going on to federation between internal and external clouds The aim is to equip the IT organization with the capabilities to move data and resources between internal and third-party data centers to achieve the real benefits of elastic IT provisioning EMC IT recommends that to manage the progression shown in

the previous figure it is necessary to set up a roadmap as shown in Figure 4 that further develops the components of the ecosystem

EMC ITrsquos roadmap of the transition to the private cloud

Planning the transition to the cloud

EMC believes that in order to transform the IT organization it isnrsquot enough to just concentrate on changing the technology aspects An IT transformation initiative must address five perspectives

bull Technology

bull Businesscapabilitiesandexperience

bull People

bull Operations

bull ITpoliciesprocessgovernance

Moreover it is essential not to just consider these elements in isolation but to assess and plan for the complex interactions among them In line with the components of an IT transformation initiative EMC believes there are essentially three stages of adoption for organizations that are considering a private cloud strategy at the enterprise level and are at various stages They are as follows

bull TheITProductionstagewhichtargetsdevtestIT applications for virtualization to achieve cost efficiencies Key capabilities leveraged include shared resource pools and elastic capacity

bull TheBusinessProductionstagewhichenables business applications including mission-critical applications with an emphasis on high QoS Key capabilities leveraged include a zero-touch infrastructure and increased control combined with service assurance

bull TheIT-as-a-Servicestagewhichemphasizes business agility Key capabilities include service definition service catalog self-service and chargeback

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 6: Cloud Bound

6

Each stage is characterized by business drivers and triggers level of sponsorship for virtualization types of applications virtualized percentage of the x86 server infrastructure virtualized and the IT competencies acquired along the journey Success is measured by tracking business value realized (the value path) Examples include the areas of ongoing financial and productivity results achieved along the journey to the cloud such as Capex and Opex savings and improved business agility

When considering these three stages of adoption it is important to plan the transition in measured steps as follows

Step 1 Build the foundation

As a first step EMC has been working on building the foundations at the technical level This involves reaching out to technology practitioners in the IT organization to

share information on basic cloud enabling technologies their operations and their integration methodologies As virtualization is a key enabler of the transition to a cloud-based infrastructure it is critical that IT practitioners learn and understand the impact of applying virtualization Given the rapid pace of technology developments and extensions in the areas of virtualization and cloud computing it is important that these discussions cover the current state of technology as well as trends scenarios and alternatives that might emerge in this vibrant segment of the IT landscape

It is also critical to encourage technologists to look beyond individual pieces of the technology and look toward an integrated view of how the various components work together This involves a number of domain-crossing discussions that bring together experts from different fields such as storage network backup and server among others

This requires investments in hiring and cultivating specialists who can provide an overall solution view of cloud-based IT offerings and ensure the dissemination of information reference architectures and product and solution documentation to the technology audience

Step 2 Accelerate change

The next step in this process from EMC ITrsquos experience consists of bringing discussions to the operations level with the delivery audience ndash those people focused on delivering IT services to the business These discussions should focus on the two clear agendas of IT operations personnel

bull Leveragingnewtechnologiestobettermeet key performance indicators used to measure IT effectiveness

Source EMC

FIguRE 4EMC ITrsquos roadmap of the transition to the private cloud

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 7: Cloud Bound

7

7

bull Makingorganizationalandprocesschanges including the policy and governance mechanisms needed to fully leverage the capabilities of the new technologies

Changes in technology can provide only limited benefits to businesses unless accompanied by process and organizational change Therefore challenging standard operating procedures default assumptions around service levels and IT provisioning and even the way IT is accounted and paid for are essential to these discussions These conversations may also result in the development of new operational roles metrics and service delivery models patterned around the concept of delivering IT as a service However during discussions at this level EMC has found that it is critical to recognize the close links between people and processes and pay careful attention to the complex interplays between operations processes and organizational change

Step 3 Focus on the advantages of service management

Business units may not fully understand the advantages in migrating to a private cloud-based IT infrastructure beyond IT cost reduction Therefore EMC IT discovered that it is critical to educate businesses leaders about the additional value that EMC IT can create for them by leveraging the benefits of the cloud infrastructure Discussions with business units must focus on the enhanced service management benefits the new infrastructure offers such as

bull Introducingnewservicesthatcandrivevalue to business units (for example truly elastic IT provisioning choice of service providers and utility chargeback models)

bull Reducingthecycletimeforbusinessesthrough self-service IT provisioning choice of multiple providers and service level agreement-based IT service delivery

bull Providingcustomersclientsandemployees with better user experiences through optimized IT infrastructures

EMC IT recognizes that an important transformational initiative of this nature brings with it the need for organizational change as well as a change in behavior from its employees Continuous education and communication are crucial to getting the organization ready for this journey

Building EMCrsquos private cloud infrastructureAt the heart of EMCrsquos transition to the private cloud is EMC ITrsquos ldquoVirtualize Everythingrdquo strategy which focuses on virtualizing all elements of a data center systems storage network security monitoring and management application stack (applications databases middleware) and even the desktop

EMC IT identified six key programs along with a use case (virtual desktop) referenced in Figure 5 and described next to make the transition to a private cloud-based IT organization

1 Server virtualization and consolidation

With the goals of improving the utilization of IT resources in data centers and reducing the footprint of physical machines EMC IT embarked on a server virtualization and consolidation exercise across all of its enterprise data centers By 2008 EMC had consolidated 1250 servers into just 250 machines a transition that has reduced space requirements by 60 percent and power and cooling costs by 70 percent By ensuring that all new solutions are VMware-compliant and by following an aggressive plan to consolidate 1600 additional servers to 40 servers over 2009-2010 EMC expects to save $13 million in costs and save an additional $10 million over the next five years as well as dramatically reduce its carbon footprint and improve CPU and memory utilization rates EMCrsquos vision is also in line with its commitment to the Virtual Computing Environment (VCE) coalitionrsquos Vblocktrade vision for building integrated infrastructures for virtualization at scale

Source EMC

FIguRE 5Key programs leading to private cloud

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 8: Cloud Bound

8

2 Optimized storage and network

EMC is a world leader in information infrastructure By leveraging EMCrsquos own experience and comprehensive product portfolio in the storage and information lifecycle management (ILM) space EMC IT is working on further optimizing information storage for a cloud-based storage design With technologies such as Fully Automated Storage Tiering (FAST) Virtual Provisioningtrade and tiering EMC IT separates information based on its criticality to the business EMC IT has moved to a five-tier configuration from a two-tier storage model and has also increased the utilization of its storage infrastructure by 19 percent

EMC expects to increase its storage utilization rate from 68 percent to 80 percent thereby avoiding the purchase of more than 15 petabytes of storage over five years EMC expects to achieve the goal of 100 percent virtualized storage by 2011 EMC VPLEXtrade is a key enabling technology that will enable EMC IT to virtualize and move workloads and associated information around data centers and across internal and external clouds

On the network side EMC is leveraging its alliances with VMware and Cisco in achieving network virtualization Using technologies like IP-based storage and Fibre Channel over Ethernet (FCoE) EMC is focused on reducing cabling while increasing the speed and efficiency of data transfer

3 Backup recovery and archiving

By using best-in-class EMC solutions such as Avamarreg Data Domainreg and NetWorkerreg for replication backup recovery and archiving EMC facilitates complete and highly effective information management from a virtual cloud-based infrastructure In addition data deduplication capabilities increase the efficiency of EMCrsquos growing backup-to-disk policy Key benefits include reducing overall backup by 50 percent decreasing backup time by 75 percent using Avamar data deduplication capabilities to back up remote users and increasing remote backup and recovery success rates from 38 percent to 98 percent

4 Security

EMCrsquos private cloud vision involves the ability for IT managers to freely move and federate data and resources across internal and external clouds Therefore it is critical to enhance security to support multi-tenancy data leakage protection governance risk and compliance (GRC) and carrier security requirements EMC collaborates with divisions such as RSA and Archer to virtualize security components and develop governance risk and compliance tools to monitor and manage the challenges related to transitioning IT to a private cloud-based infrastructure

5 Management and automation

As private cloud-based IT management becomes a reality it is imperative to track IT resources and information using an integrated tool suite EMCrsquos Ionixtrade suite of IT management software provides a single-pane-of-glass view of all of the IT resources across the virtualized data center Using the advanced integrated IT management capabilities of Ionix tools such as Ionix Unified Infrastructure Manager (UIM) and Server Configuration Manager (SCM) and virtualization management tools from the VMware family such as VMware vCentertrade and vCloudtrade EMC IT is working on solutions to accelerate self-provisioning of IT services reduce time-to-market and support innovative chargeback models

6 Applications and cloud experience

EMCrsquos vision for the virtualized data center and the transition to the private cloud is to enable its IT organization to offer platforms and applications as services (for example IaaS SaaS and PaaS) EMC is moving application servers databases and middleware to a virtualized platform with the goal to provide them as on-demand infrastructure services to business units for their development activities And EMC IT has been on the path to providing database grids on Oracle and Microsoft SQL Server to enable virtualized functionality EMC IT also views the cloud model as a mechanism to support the movement of currently business-supported applications such as vApps into a controlled IT-supported model EMC is working on enabling infrastructures based on vCloud

to provide IT in a self-service model to its business units In addition EMC IT is looking to leverage Atmosreg as an internal platform for offering compute and storage solutions as a public cloud service to its customers

Virtual desktop infrastructure ndash an implementation use case

Using the power of VMwarersquos Virtual Desktop Infrastructure (VDI) EMC is working on desktop virtualization approaches to simplify and lower the cost of IT management increase IT security optimize information storage and provision IT resources based on the needs requirements and profiles of its workers The goal of EMC IT is to provision the user and not the device hence the implementation of VDI will provide the ability for IT to enable different devices used by the end user This would include the usual company-issued desktop or laptop but extend to a bring-your-own-device (BYOPC or BYOD) model in addition to thin clients and mobile devices

EMC plans to have 100 percent virtualized desktops by 2012 resulting in improved and simplified security lower client TCO rapid deployment reduced support costs and user-based provisioning

Making the transition to the private cloudBefore transitioning existing IT resources to a private cloud-based infrastructure EMC IT performs the following key activities

Ensure basic enabling technologies work The first activity is to ensure that the basic enabling technologies work as advertised in EMCrsquos own IT environment This requires rigorous testing of all infrastructure components within the virtualized data center ndash compute storage network and orchestration ndash to ensure that their performance is in line with requirements and established benchmarks Next EMC IT configures and tests all software components for the required performance levels Focused attention on security requirements and issues

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 9: Cloud Bound

9

9

relating to federation between locations is critical during this phase

Create use cases and assess capabilities across requirements The second general activity involves creating a high-level framework of use cases within the business and assessing the current capabilities across those requirements The objective of identifying the use cases is to match the business needs to the appropriate cloud model for providing IT services The high-level use cases are based on parameters such as time-to-market demand predictability and IT elasticity integration needs network bandwidth and latency security risk and compliance and business impact The requirements across each of these parameters are dynamic and vary significantly across applications affecting the choice of internal and external cloud resources required

Define policy and governance mechanisms The third activity is to define policy and governance mechanisms to manage and operate the private cloud-enabled IT organization It is essential to define robust mechanisms to handle critical issues around technical characteristics such as security bandwidth and integration followed by performance which encompasses service delivery aspects such as IT management

EMC ITrsquos private cloud policy and governance framework The transition of IT to the private cloud directly impacts the revenue operational and business costs and risks faced by the organization as described next

bull Impact to revenue ndash The transition to the private cloud helps IT organizations provide improved services to business units These IT services help business units find new customers enhance quality while lowering the cost of goods and services delivered and sell more successfully to existing customers

bull Impact to costs ndash Transitioning the entire IT infrastructure to the private cloud calls for large organizational investments upfront

resulting in significant savings at the end of the transition Therefore it is essential to make adequate budgetary provisions initially to receive rewards later

bull Impact to risks ndash A private cloud infrastructure uses both internal and external cloud infrastructures This calls for new approaches to manage the business and information risks for the organization

Therefore it is essential to establish a governance body (involving people from business finance legal and IT disciplines from within the company) for evaluating the migration of IT to a private cloud-based infrastructure

EMC IT has developed a high-level policy and governance framework to move applications platforms and infrastructures to the external and public cloud EMC has defined lead criteria that decide the policies and governance frameworks for an application

bull Application classification ndash Classifying applications as mission-critical (directly affecting customer service delivery or affecting EMCrsquos revenue or its reputation) business-critical (critical to the operations of a business unit) or business supporting (a supporting application)

bull Security ndash The information security requirements necessary for the application

bull Risk and compliance ndash A profile of the risks of incidents from outages to information leaks and the required compliance requirements

bull Connectivity ndash Bandwidth and performance requirements for globally distributed applications and users

bull Integration ndash The requirements to ensure that tightly coupled applications can work together

bull Performance ndash Service delivery requirements such as availability service level agreements and IT service management

bull Time-to-market ndash Rapid provisioning requirements

bull Demand elasticity ndash Ability to deal with changes in the requirements of business units as well as scale-up and scale-down needs

EMC IT has created a set of business use cases such as those mentioned in Figure 6 for various profiles of services requested by business units with policies and small-scale governance functions for each use case

The transition to the private cloud will enable EMC IT with a transparent method for tracking the usage of IT resources by business unit This empowers EMC IT with the capability of constructing new chargeback models

ConclusionEMCrsquos cloud computing strategy is designed to completely transform its IT organization and operations Such a transformation means making changes in the way IT is built run consumed and governed at the company The goal of this strategic initiative is to make EMC IT a customer-centric provider of end-to-end IT solutions to meet the business needs of EMC business units

Leveraging the power of the private cloud EMC IT is introducing innovative services such as on-demand IT infrastructure provisioning and self-service options for IT service enablement To facilitate this transition EMC IT has concentrated its efforts on the definition of a clear strategy for internal cloud implemented through six programs which focus on transitioning its IT infrastructure to the virtualized data center model This initiative is in line with EMCrsquos vision for the Virtual Computing Environment which it shares with its partners VMware and Cisco

To prepare the organization for a new paradigm of IT operations EMC IT is also educating stakeholders at various levels on the new IT service paradigms as well as developing a strong policy and governance framework for managing the new IT infrastructure Working closely with partners and product divisions EMC IT is concentrating

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 10: Cloud Bound

10

on maximizing the business benefits of technology that can move its existing IT infrastructure to the private cloud

EMCrsquos structured approach helps accelerate its journey to the private cloud It provides the company with the opportunity to begin cloud initiatives without waiting for complete solutions to emerge even as it moves from the Business Production stage to the IT-as-a-Service stage (Figure 7) This enables EMC IT to more easily leverage these solutions as technologies evolve

Looking forward EMC expects to increase the storage utilization rate from 68 percent to 80 percent and avoid the purchase of more than 15 petabytes of storage over five years

All told EMCrsquos journey from 2004 through 2009 resulted in savings of $1045 million including an estimated $883 million in capital equipment cost avoidance and $162 million

bull ThefollowingcanbefoundonChuckrsquosBlog an EMC insiderrsquos perspective on information technology and customer challenges

bull ldquoNot All Clouds Are Private Cloudsrdquo

bull ldquoPrivate Clouds and the Fixed Vs Variable Discussionrdquo

bull ldquoPrivate Cloud ndash The TOS Modelrdquo

bull ldquoPrivate Cloud Adoption Modelsrdquo

bull ldquoGood Governance Equals Good ITrdquo

bull Announcement of the VCE coalition

bull Vblock Infrastructure Packages

bull EMC IT A Blueprint for Data Center Efficiency white paper

of operating cost reduction due to increased data center power cooling and space efficiency

By having ldquorisk versus rewardrdquo conversations with stakeholders at each level EMC IT has been successful in accelerating the adoption of private cloud-based technologies within the company This approach enables EMC to better structure discussions with partners and external IT cloud service providers EMC IT is able to provide vendors with the granular details of candidate workloads and the solution requirements they seek

ReferencesRead the following for more information

bull EMCITrsquosJourneytothePrivateCloudblogat httpwwwemccomemcit

FIguRE 6A high-level abstraction of EMC ITrsquos policy and governance model for external cloud usage

Source EMC

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 11: Cloud Bound

11

11

FIguRE 7EMC ITrsquos progression to the private cloud-based infrastructure

bull LearnmoreabouttheseEMCofferingsonEMCcom

bull EMC Atmos

bull EMC Symmetrix Virtual Provisioning

bull EMC FAST

bull EMC Ionix

bull VCE Cloud Computing Strategy Service

Take the next step

To learn how EMC products services and solutions help solve your business and IT challenges contact your local representative or authorized reseller ndash or visit us at wwwEMCcom

EMC Corporation

Hopkinton Mass 01748-9103

1-508-435-1000 (in North America 1-866-464-7381)

Abstract

This white paper is the first in a series of EMC IT Proven papers describing EMC ITrsquos initiative to move toward a private cloud-based IT infrastructure EMC IT defines the private cloud as the next-generation IT infrastructure comprising both internal and external clouds that enables efficiency control and choice for the internal IT organization

Please click here to access a copy of the white paper

Source EMC

EMCrsquos Cloud Optimiser Model

bull AmodeldevelopedbyEMCandMcKinsey

bull Assessestheirenvironmentandprovidesrecommendationsontheoptimal use of Cloud in their environment

ndash Includes private Public and Hybrid Cloud

bull TheCloudOptimizerplacesapplicationworkloadsbasedonthreeldquofiltersrdquo

ndash Economicndash Trustndash Feasibility

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 12: Cloud Bound

12

As enterprises move beyond virtualizing their data centers to build private cloud-computing infrastructures security must evolve to support this While the fundamental principles of information security donrsquot change how enterprises provision and deliver security services must change This research outlines the foundational capabilities that will be required from enterprise security infrastructure to secure private cloud computing

Key Findings

bull Policiestiedtophysicalattributessecuritypolicy enforcement points embedded within physical appliances and the usage of air gaps for security will inhibit private cloud adoption

bull Virtualizationofsecuritycontrolsisanimportant step in enabling secure private clouds but other capabilities are required

bull Contextenablementincludingapplicationidentity and content awareness will be critical to supporting secure private cloud computing

bull Securingaprivatecloudcanrsquotbejustabout technology or it will fail Changes to processes and a shift in mind-set will also be required

bull Theneedforsecuritymustnotbeoverlooked or ldquobolted onrdquo later during the transition to private cloud computing

Recommendations

bull Changeyourmind-setaboutinformationsecurity to think of it as a set of adaptive services that are delivered via programmable infrastructure and controlled by contextual policies based on logical attributes to create adaptive zones of trust using a separately configurable control plane

bull Pressureincumbentsecurityvendorstodeliver their security controls in a virtualized form to more easily address secure private cloud-computing requirements

bull Inevaluationsheavilyweighttheabilityto use a consistent way of expressing security policy across physical virtualized and private cloud-computing environments as compared to using different vendors and solutions to address each separately

bull Maintainseparationofdutiesbetweensecurity policy enforcement and IT operations in the transition to virtualized data centers and then to private cloud-computing environments

bull Beginthetransformationtocontext-awareand adaptive security infrastructure now as you upgrade and replace legacy static security infrastructure such as network and application firewalls intrusion detection systems (IDSs)intrusion prevention systems (IPSs) and Web security platforms

STRATEgIC PLANNINg ASSuMPTIONS

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

ANALYSIS

Gartner defines ldquocloud computingrdquo (including both private and public clouds) as a style of computing where scalable and elastic IT-enabled capabilities are delivered as a service to customers using Internet technologies Often the term ldquocloudrdquo is used as a shorthand to talk about the attributes that enterprises believe cloud-based computing architectures will offer Consumers of cloud-based services want usage-based consumption of the services via standard Internet technologies and self-service interfaces Providers of cloud-based services want the ability to deliver scalable shareable automated and elastic services We discuss

these attributes in ldquoFive Refining Attributes of Public and Private Cloud Computingrdquo

At its core private cloud computing is built on the same concepts and clients indicate their desire to bring these same attributes into the enterprise data center Here the IT department becomes the cloud service provider to deliver IT as an elastic service to multiple internal customers While the focus may shift slightly (for example self-service provisioning for IT customers is more important chargeback capabilities are typically less so) the desired attributes are the same For most organizations virtualization will provide the foundation and the steppingstone for the evolution to private cloud computing However the need for security must not be overlooked or ldquobolted onrdquo later during the transition to private cloud computing

Private Clouds Same Security Needs New Capabilities RequiredWhether securing physical data centers virtualized data centers or private clouds the fundamental tenets of information security donrsquot change ndash ensuring the confidentiality integrity authenticity access and audit of our information and workloads These objectives translate into traditional security controls and policy enforcement points (PEPs) ndash for example firewalling IPS IDS encryption digital signatures authentication and authorization However there will be significant changes required in how security is delivered Whether supporting private cloud computing public cloud computing or both security must become adaptive to support a paradigm where workloads are decoupled from the physical hardware underneath and dynamically allocated to a fabric of computing resources Policies tied to physical attributes such as the server Internet Protocol (IP) address Media Access Control (MAC) address or where physical host separation is used to provide isolation break down with private cloud computing For many organizations the virtualization of security controls will provide the foundation to secure private cloud infrastructures but

From the Gartner Files

From Secure Virtualization to Secure Private Clouds

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 13: Cloud Bound

13

13

alone it will not be enough to create a secure private cloud

To support secure private cloud computing security must be an integral but separately configurable part of the private cloud fabric designed as a set of on-demand elastic and programmable services configured by policies tied to logical attributes to create adaptive trust zones capable of separating multiple tenants (see Figure 1)

Ideally the security models used to support private clouds would enable multidimensional hybrid environments ndash spanning physical to virtual workloads within the same data center and spanning between on-premises and public cloud-based computing environments In this research we outline six necessary attributes of private cloud security infrastructure and describe how security must change to support the construction of secure private clouds

A Set of On-Demand and Elastic ServicesRather than security being delivered as a set of siloed security product offerings embodied within physical appliances it needs to be delivered as a set of services available ldquoon demandrdquo to protect workloads and information when and where they are needed These services need to be integrated into the private cloud provisioning and management processes (not bolted on as an afterthought) and be made available to any type of workload ndash server or desktop (see Note 1) As workloads are provisioned moved modified cloned and ultimately retired the appropriate security policy would be associated with the workload throughout its life cycle

FIguRE 1Evolving to Secure Private Clouds

Source Gartner (October 2010)

Physical

Virtual

Static Dynamic

Noncontextual Contextual

Runtime contextPolicies tied to logicalMultitenantAdaptive policies

Static contextPolicies tied to physicalSingle tenantPredetermined policies

Although it is possible this type of adaptive security protection could be accomplished solely with physical security infrastructure and complex virtual LAN (VLAN) overlays we believe most enterprises will use a combination of physical and virtualized security controls to extend security policy into private cloud structures There are a variety of reasons for this including addressing the loss of visibility of inter-VM traffic within a virtualized data center as well as the inputoutput overhead if traffic is routed out to physical hardware for security policy enforcement Virtualized security controls can place policy enforcement within the physical host closer to the workload and information it is protecting when and where it is needed enabling dynamic data center infrastructures as well as the potential to leverage alternative computing sourcing options

Physical appliances will continue to be used for high-bandwidth applications at the physical boundaries of organizations Virtualized security controls will be used throughout the private cloud fabric for inter-VM inspection and at logical boundaries to create zones of trust for workloads of different trust levels Ideally physical and virtual security controls will intelligently coordinate their inspection to avoid redundant inspection

By 2015 40 of the security controls used within enterprise data centers will be virtualized up from less than 5 in 2010

The transition from security as a set of products to delivering security as a set of services is a significant mind-set shift for information security professionals Virtualized security controls will help to enable this shift In contrast to physical security controls which scale up using larger and larger hardware-based appliances virtualized security PEPs running within security VMs will support the simultaneous need to scale out with a larger number of security VMs running in parallel closer to the workloads and information they protect and taking advantage of the high-availability and load-balancing capabilities available to all VMs

Programmable InfrastructureThe security infrastructure that supplies the security services discussed in the prior section must become ldquoprogrammablerdquo ndash meaning that the services are exposed for programmatic access (see Note 2) By definition private and public cloud-computing infrastructure is consumable using Internet-based standards In the case of programmable security infrastructure the services are typically exposed using RESTful

Note 1 Workloads

Workloads in this sense are the set of applications and services that support a given process which may span more than one VM and one physical machine This includes server and desktop workloads

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 14: Cloud Bound

14

APIs which are programming language and framework independent

By exposing security services via APIs the security policy enforcement point infrastructure becomes programmable from policy administration and policy decision points (such as operational and security management consoles or from other security intelligence systems such as security information and event management systems) There are multiple benefits to this shift in capability This enables significantly higher levels of automation than are possible with traditional security infrastructure As new workloads are introduced into the private cloud security infrastructure can be automatically configured via ldquoself-service interfacesrdquo (where the ldquouserrdquo is a provisioning system not an end user) to protect the new workload based on predefined security policies without requiring manual programming of the security controls

This shift will enable information security professionals to focus their attention on managing policies not programming infrastructure Programmable security infrastructure can be modified in real time so that security services can adapt to workloads as they move dynamically within a private cloud or adapt as a workloadrsquos behavior changes Longer term as application infrastructure evolves within private clouds applications will come prepackaged with models of deployment topology management and security policies for policy-driven automation Policies consumed by management consoles and other security policy administration points will ultimately drive the configuration and programming

of the security and management plane not information technology professionals By enabling security professionals to focus on policies this capability has the added benefit of reducing the chance for human error in the programming of the security infrastructure underneath

Policies That Are Based on Logical Not Physical Attributes and Are Capable of Incorporating Runtime Context Into Real-Time Security DecisionsThe nature of the security policies that drive the automated configuration of the programmable infrastructure needs to change as well As we move to virtualized data centers and then to private cloud infrastructure increasingly security policies need to be tied to logical not physical attributes The decoupling and abstraction of the entire IT stack and movement to private and public cloud-computing models mean that workloads and information (even entire data centers with the notion of a virtual data center) will no longer be tied to specific devices fixed IP or MAC addresses breaking static security policies based on physical attributes

Security policies need to shift ldquoup the stackrdquo to logical attributes such as the identity group or role of the VM being protected the identity group or role of the application the identity group or role of the users and the sensitivity of the workload and information being processed The shift to identity application and content awareness is part of a broader shift in information security to become context aware and adaptive

To enable faster and more-accurate assessments of whether a given action should be allowed or denied we must incorporate more real-time context information at the time a security decision is made Context is not limited to identity application and content awareness It will expand to include environmental context (such as the time of day and geographic location of the server) trust of the device integrity of the virtualization platform underneath reputation of the VM being loaded behavior the user or VM is exhibiting and so on Context should also include virtualization awareness so that as a workload is live migrated or cloned the associated security automatically moves with the workload throughout its life cycle without requiring manual intervention

There are multiple benefits to decoupling security policies from the workloads and information they protect Powerful compound security policies can be delivered independent of network topology avoiding complexity in VLAN configurations and network-cabling infrastructure Also by moving up the stack security policies can be expressed in more business-friendly terms For example identifying which users and groups should access which applications is a straightforward policy to compose and attest to by the business process information and application owners Finally by incorporating runtime context into security decisions organizations can implement adaptive security policy based on the behavior of the user or of the workload (for example if a workload is behaving oddly place a stronger auditing control on it or limit its network access)

Adaptive Trust Zones That Are Capable of High-Assurance Separation of Differing Trust LevelsInstead of administering security policies on a VM-by-VM basis security policies based on logical attributes as described in the previous section will be used to create zones of trust ndash logical groups of workloads with similar security requirements and levels of trust (for

Note 2 Programmatic API Access

These APIs will become a target for attack To reduce the threat of attacks the best practice will remain the isolation and separation of security and management control traffic to a separate physical network

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 15: Cloud Bound

15

15

example all Payment Card Industry [PCI]-related workloads are assigned a specified level of security policy) As the policies are linked to groups of VMs and not physical infrastructure the zones adapt throughout the life cycle of the VM as individual VMs move and as new workloads are introduced and assigned to the trust zone

In todayrsquos virtualized data center workloads of different trust levels are not typically combined onto the same physical server However this breaks the fluidity of private cloud-computing models Increasingly this capability will be desired for higher levels of efficiency and effectiveness of the resource fabric being shared Leveraging emerging root of trust measurements for hypervisors and embedded hypervisors secure private clouds need to be able to support workloads of different trust levels on the same physical hardware without requiring the use of separate physical servers

By 2015 70 of enterprises will allow server workloads of different trust levels to share the same physical hardware within their own data center except where explicitly prohibited by a regulatory or auditor compliance concern

Adaptive trust zones will become the basis for trust audit and compliance policies Security policies will vary between trust zones and security controls will be placed at the logical perimeters between key trust boundaries For example a trust zone of PCI-related workloads may require encryption of all data between virtual machines within the trust zone It may also be restricted to access from only users associated with the PCI group it may have all inter-VM traffic monitored with an intrusion detection system and it may be separated from all other trust zones with stateful firewall inspection as required by PCI In contrast a trust zone of virtual desktop infrastructure (VDI)-related workloads may be treated as untrusted with firewalling and in-line IPS-based inspection of all traffic to and from the zone as well as blocking of any direct peer-to-peer traffic within the zone

Trust zones may be nested so that what was a single physical data center can now be managed and secured as multiple virtual data centers each composed of multiple logical not physical perimeters around trust zones Security policy may then be applied as needed within and between zones In most cases multiple trust zones will be allowed to reside on a single physical host with the enterprise able to define how much separation is sufficient for security and compliance purposes For example storage and backup can be isolated and network traffic can be separated using IPS and firewalling enforcement as internal or external compliance policies dictate

Private cloud infrastructure will require security services that are designed to provide high-assurance separation of workloads of different trust levels as a core capability This is exactly the same type of separation capability required by public cloud providers to separate and isolate tenants from different organizations For enterprises building private clouds the concepts are identical ndash although instead of tenants from different organizations they will routinely be responsible for separating workloads of different trust levels including different business units and divisions sharing the same underlying physical infrastructure

Separately Configurable Security Policy Management and ControlSecurity must not be weakened as it is virtualized and incorporated into cloud-based computing infrastructures The security controls and policies discussed previously must not be able to be arbitrarily disabled by operational staff and should fail open or closed as enterprise policies dictate Strong separation of dutiesconcerns between IT operations and security needs to be enforceable within a private cloud infrastructure just as within physical infrastructure and virtualized infrastructure today

This separation occurs at multiple levels If software controls are virtualized we should not lose the separation of duties we had in the physical world This requires that virtualization and private cloud-computing platform vendors provide the ability to separate security policy formation and the operation of security VMs from management policy formation and the operation of the other data center VMs Typically this will be enabled by integrating and controlling access to security operations at a granular level using role-based access control within the management system controlled by integration with organizational and group information located in enterprise directories (typically Active Directory or an LDAP-enabled repository) along with delegated administration capabilities Likewise all security policy changes and operations to security VMs must be fully audited in tamper-resistant logs that are inaccessible to security administrators

A security policy manager will enable the orchestration and definition of security policies and the assignment of policies to the logical attributes of the workloads and groups of workloads as described previously with an emphasis on policy integrity and testing As a given VMs may be assigned multiple security policies and may be members of more than one trust zone The policy management system should support multiple overlapping security policies to be assigned and be able to identify the resultant least-privilege policy and provide for policy resolution in the event of a conflict Ideally the system will support proactive modeling of ldquowhat ifrdquo scenarios before policy changes are implemented

ldquoFederatablerdquo Security Policy and IdentityPrivate clouds will be deployed incrementally not all at once Private clouds will be carved out of existing data centers where only a portion has been converted to a private cloud model In addition many enterprises will have a percentage of workloads that havenrsquot been virtualized for years to come

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010

Page 16: Cloud Bound

16

Ideally private cloud security infrastructure would be able to exchange and share policies with other data center security infrastructure ndash virtualized and physical There are no clear standards for the sharing of security policy Spanning physical to virtualized infrastructure will require using the same vendor the enterprise has chosen to provide security in both environments or using different vendors in each environment Ideally security controls placed across physical and virtualized infrastructure will be able to intelligently cooperate for workload inspection ndash for example data going to and from the data center inspected by hardware-based physical security appliances

Organizations will also begin experimentation with public cloud infrastructure as a service (IaaS) providers creating hybrid privatepublic cloud-computing environments Ideally security policies designed to protect workloads when on premises would also be able to be federated (along with user identity-related information) to public cloud providers There are no established standards for this either However the VMware vCloud API is a start as is work within the Distributed Management Task Force (DMTF) to extend Open Virtualization Format (OVF) to express security policy Absent clear standards and APIs capabilities for extending enterprise

security policy will remain fragmented relying on a combination of controls bundled within workloads virtual private network-based extension of network security policies remote console-based policy management remote API-based programming of service provider policies and written commitments for security service levels

Gartner RAS Core Research Note G00208507 Neil MacDonald Thomas J Bittman 12 October 2010