What do I need to create a cloud?

1. What do I need to create a cloud? 8/22/12

2. What do I need first? • Standardization • You need to decide on a standard for operating, deploying and maintaining the cloud environment. • Automation • You need automation that will allow users to create accounts through self-service. This means that approval of new requests goes through an automated process. • Shared Resources • All of the entities participating in the cloud need to share their infrastructures completely.

3. What services do you need? • Clouds need to provide access to all of the services needed by their clients. • Any business cloud is going to have to know what it’s clients need and want to do their jobs. • That service then has to be provided. • Human resources • Office automation • High performance computing power • E-mail

4. What services are appropriate for the cloud? • Common services with static interfaces like e-mail are appropriate for the cloud. • Uncommon, mission-specific services are not appropriate for the cloud, unless they are shared by a large part of an organization.

5. How are resources and services paid for? • Resources cost money. How are we going to charge for space and use of services in the cloud? • How many licenses do I need? • Who is going to pay the up-front cost?

6. An approach… Access Management Service Management Resource Management Resources

7. Resources • Infrastructure • Platforms • Software • Virtualization is one way to do this, but … • As long as there is a mechanism for sharing these resources, that is also good enough.

8. Resource Management • Automated management of resources • Allocation of resources across the cloud • Who gets access to what and when?

9. Service Management • Service Governance • Converting pools of resources into service levels. • Is it performance the user is after, or availability? • Depends on the application • Different models of Service • Infrastructure as a service • Platform as a service • Software as a service

10. Access Management • User self-service • Provide a “Service Catalog” • Ties to the Service Management Layer in terms of metering access or charging for access, etc.

11. Infrastructure as a Service • Provisions for: • Processing Power • Storage Capacity • Network Capacity • Fundamental Computing Resources • Consumer decides what software to run on the infrastructure provided. • Operating System • Applications

12. Platform as a Service • Consumer runs applications either developed in house or purchased as they will. • No control over platform at all: • Operating System • Network • Servers • Storage

13. Software as a Service • Everything runs in the cloud • Software is made available in the cloud. • No control over resources. • Access through thin-client interface.

14. Deployment Models • Private Clouds • Community Clouds • Public Clouds • Hybrid Clouds

15. Key Characteristics of Clouds • Flexibility/Elasticity • Scalability of Infrastructure • Broad Network Access • Location Independence • Reliability • Economies of Scale and cost effectiveness • Sustainability

16. Security in the Cloud • Trust • Dependent on the Deployment Model • Identification of Threats • Benefits of Cloud Computing on Security • Centralization of Security • Data and Process Segmentation • Redundancy • High Availability • Risks • Reliability Issues • Data Integrity • Recovery • Privacy • Auditing

17. Categorization of Threats Account Control Multitenancy Issues Malicious Insiders Cloud Computing Management Console Security Data Control Fig. 1 from Zissis and Lekkas

18. User Specific Security Requirements

19. Application Level

20. Virtual Level

21. Physical Level