Cyberstudy
PDF p.153 In progress

Cloud Deployment Models

Open PDF at p.153 16 flashcards

Summary

PDF p.153

Cloud deployment models classify how services are owned and provisioned, impacting threats and vulnerabilities. The main models include Public, Hosted Private, Private, Community, and Hybrid clouds, each with unique characteristics and security considerations.

In plain words

Supplementary — not from your PDF

Deployment models describe who owns the cloud and who shares it. A public cloud is multi-tenant and shared over the Internet. Hosted private is dedicated to you but run by a third party. Private is owned and run by you. Community is shared by organizations with common needs. Hybrid mixes them. More sharing is cheaper, but brings more risk of data leaking between tenants.

Detailed explanation

PDF p.153
  • Public (or Multi-tenant)
    • Definition: Services offered over the Internet by cloud service providers (CSPs) to consumers.
    • Functions: Businesses can offer subscriptions or pay-as-you-go financing, with lower-tier services often free.
    • Risks: Shared resources pose performance and security risks.
    • Usage: Multi-cloud architectures use services from multiple CSPs.
  • Hosted Private
    • Definition: Hosted by a third party for exclusive use by an organization.
    • Benefits: More secure and better performance.
    • Costs: More expensive than public clouds.
  • Private
    • Definition: Cloud infrastructure completely private to and owned by the organization.
    • Functions: Managed by a dedicated business unit, with other units using the cloud.
    • Benefits: Greater control over privacy and security.
    • Usage: Suitable for banking and governmental services requiring strict access control.
  • Community
    • Definition: Shared by several organizations to pool resources for common concerns like standardization and security policies.
    • Usage: Can be hosted private or fully private.
  • Hybrid
    • Definition: Combines public, private, community, hosted, on-site, and off-site solutions.
    • Benefits: Flexibility and scalability, with data risk considerations when moving data between environments.

Security Considerations

  • Single-tenant Architecture
    • Definition: Dedicated infrastructure for a single customer.
    • Benefits: Highest security level, complete control.
    • Costs: More expensive, customer manages security.
  • Multi-tenant Architecture
    • Definition: Multiple customers share the same infrastructure.
    • Benefits: Cost-effective.
    • Risks: Increased risk of unauthorized access or data leakage.
  • Hybrid Architecture
    • Definition: Uses both public and private cloud infrastructure.
    • Benefits: Flexibility and control over sensitive data.
    • Challenges: Requires careful management for integration and security.
  • Serverless Architecture
    • Definition: Cloud provider manages infrastructure, scaling resources based on demand.
    • Benefits: Potentially more secure, provider manages security.
    • Responsibilities: Customers must secure access to applications and data.

Important terms

taken from the text above
Public (or Multi-tenant)
Services offered over the Internet by cloud service providers (CSPs) to consumers.
Hosted Private
Hosted by a third party for exclusive use by an organization.
Private
Cloud infrastructure completely private to and owned by the organization.
Community
Shared by several organizations to pool resources for common concerns like standardization and security policies.
Hybrid
Combines public, private, community, hosted, on-site, and off-site solutions.
Single-tenant Architecture
Dedicated infrastructure for a single customer.
Multi-tenant Architecture
Multiple customers share the same infrastructure.
Hybrid Architecture
Uses both public and private cloud infrastructure.
Serverless Architecture
Cloud provider manages infrastructure, scaling resources based on demand.

Examples & real-world scenarios

Supplementary — not from your PDF
  • A startup running on a public cloud with pay-as-you-go pricing.
  • A bank running its own private cloud for strict access control.
  • Several hospitals sharing a community cloud with common compliance policies.

Scenario

A government agency must keep sensitive records under its own control but wants cheap burst capacity for a public website. A hybrid model fits, but moving data between environments needs careful controls.

Common mistakes

Supplementary — not from your PDF
  • Assuming hosted private means you own the hardware. A third party hosts it for your exclusive use.
  • Thinking serverless means no security work. You still secure access to your apps and data.

Practical skills

Supplementary — not from your PDF
  • Pick a deployment model from cost, control and compliance needs.

What I should remember

Key Points PDF p.153
  • Public (or Multi-tenant)
    • Shared Resources: Performance and security risks.
    • Multi-cloud: Services from multiple CSPs.
  • Hosted Private
    • Exclusive Use: More secure, better performance.
    • Cost: More expensive.
  • Private
    • Complete Control: Over privacy and security.
    • Usage: Banking, governmental services.
  • Community
    • Shared Costs: For common concerns.
    • Types: Hosted private or fully private.
  • Hybrid
    • Combination: Public, private, community, hosted, on-site, off-site.
    • Flexibility: With data risk considerations.
  • Security Considerations
    • Single-tenant: Highest security, more expensive.
    • Multi-tenant: Cost-effective, higher risk.
    • Hybrid: Flexibility, requires careful management.
    • Serverless: Provider-managed security, customer responsibilities.