Professional Documents
Culture Documents
Cloud Computing
1
Agenda and Objectives
Introduction
Duration: 5 minutes
• If you access multiple servers, you need to only request access; you don’t have
to complete the actual server setup.
• Costs are lower. Public Cloud computing customers do not own the physical
infrastructure, thus avoiding capital expenditure (CapEx) by contracting for the
service from a third-party provider.
• You can release a capability if you are no longer using the resource, while
retaining the configuration in a library for future use.
• You always have the most updated applications and setup.
• As your requirements grow, the cloud expands with you.
• Cloud user groups and communities help to drive the face of the future.
Feedback from early adopters changes the technology.
• The importance of on-demand is that you pay for only what you use, as
opposed to traditional infrastructure.
• Maintenance is easier since the host cloud environment is maintained by the
provider.
Duration: 10 minutes
There is no specific reference architecture for Public Cloud, given that it’s a
service abstraction. All the major vendors do it differently at the physical
architecture level.
Public clouds offer dynamically provisioned resources on a self-service basis over the Internet
via web applications/web-services from an off-site service provider who shares resources and
charges on a fine-grained utility computing basis. In this model, service providers manage the
infrastructure and resource pools which can be paid for and used by any customer.
High Speed
Ethernet
Virtualized Servers Databases/Storage
Firewall
VPN
User Interface
Internet VPN
Hybrid Cloud leverages the same logical model as the Private Cloud.
Enterprise Data Center Preconfigured Standard Operating
High Speed
Ethernet
Virtualized Servers Databases/Storage
Firewall
VPN
User Interface
Internet VPN
Service type
Description of the different service categories
category
• A model of software deployment whereby a provider licenses an
application to customers for use as a service on demand
Software-as-a- • SaaS software vendors may host the application on their own web
Service (SaaS) servers or download the application to the consumer device, disabling it
after use or after the on-demand contract expires
Duration: 10 minutes
Differences of • How does the user interact with the cloud: ordering, monitoring
the Private what you use, billing, releasing what you don’t use.
Cloud vs. • Location/use of firewall will distinguish private from public.
Public Cloud
• Owned by you and configured as a cloud services model, or is it
owned by cloud service providers and you are just renting them?
Effort to
• In the case of private clouds clients may have to build out the
Deploy, Run,
four pieces and parts. There is no standard path around building
and Manage
out these pieces. They can all evolve over time. Flow is relevant
Applications
when you define a new environment.
Duration: 10 minutes
There are many other risks that one has to consider when
implementing cloud. These include:
• Business continuity, disaster recovery, and availability
• Asset management
• Human risks (e.g. malicious insider at cloud provider)
• Electronic discovery
• Financial controls
• Vendor management
• Vendor lock-in
• Risk assessment
• Risk management system/solution
• Implementation of specific controls or remediation
• Internal audits and external assurance
• Ongoing monitoring and improvement
Duration: 5 minutes
There are many legal requirements for providing cloud services that
include:
• Overview regulations and data governance requirements
• Internal compliance requirements
• Privacy laws
• Compliance with local laws and regulations
Duration: 5 minutes
Duration: 5 minutes