The AWS Shared Security Responsibility Model in Practice

©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
The AWS Shared Security Responsibility Model in
Practice
Dave Walker
Specialist Solutions Architect, Security and Compliance
16/03/16

AWS Global Footprint
US West (N.California)
US West (Oregon)
GovCloud
US East (Virginia)
EU West (Ireland)
Asia Pacific (Tokyo)
Asia Pacific (Singapore)
Asia Pacific (Sydney)
China (Beijing)
São Paulo
EU Central (Frankfurt)
Asia Pacific (Seoul)

US West (Oregon)
GovCloud
US East (Virginia)
EU West (Ireland)
São Paulo
China (Beijing)
Region
An independent collection of AWS
resources in a defined geography
A solid foundation for meeting location-
dependent privacy and compliance
requirements

US West (Oregon)
GovCloud
US East (Virginia)
EU West (Ireland)
China (Beijing)
São Paulo
Availability Zone
Designed as independent failure zones
Physically separated within a typical
metropolitan region

Edge Location
collections of servers in geographically
dispersed data centers
deliver content to end users with lower latency

12 Regions
33 Availability Zones
54 Edge locations
Over 1 million active customers
Every day, AWS adds enough new server
capacity to support Amazon.com when it was a
$7 billion global enterprise.

Data Locality
Customer chooses where to place data
AWS regions are geographically isolated by
design
Data is not replicated to other AWS regions
and doesn’t move unless you choose to move it

Shared Responsibility
Who manages which parts?

AWS Foundation Services
Compute Storage Database Networking
AWS Global
Infrastructure Regions
Availability Zones
Edge Locations
Client-side Data
Encryption
Server-side Data
Encryption
Network Traffic
Protection
Platform, Applications, Identity & Access Management
Operating System, Network & Firewall Configuration
Customer content
Customers
AWS Shared Responsibility Model
Customers are
responsible for
their security and
compliance IN
the Cloud
AWS is
responsible for
the security OF
the Cloud

AWS Shared Responsibility Model – Deep Dive
Will one model work for all services?
Infrastructure
Services
Container
Services
Abstract
Services

AWS Global
Availability Zones
Edge Locations
Optional – Opaque data: 1’s and 0’s (in transit/at rest)
Platform & Applications Management
Customer content
Customers
AWS Shared Responsibility Model:
for Infrastructure Services
Managed by
Managed by
Client-Side Data encryption
& Data Integrity Authentication
Network Traffic Protection
Encryption / Integrity / Identity
AWSIAMCustomerIAM
Server-Side Encryption
Fire System and/or Data

Infrastructure Service
Example – EC2
• Foundation Services — Networking, Compute, Storage
• AWS Global Infrastructure
• AWS IAM
• AWS API Endpoints
AWS
• Customer Data
• Customer Application
• Operating System
• Network & Firewall
• Customer IAM
• High Availability, Scaling
• Instance Management
• Data Protection (Transit, Rest,
Backup)
Customers
RESPONSIBILITIES

AWS Global
Availability Zones
Edge Locations
Optional – Opaque data: 1’s and 0’s (in transit/at rest)
Firewall
Configuration
Operating System, Network Configuration
Customer content
Customers
for Container Services
Managed by
Managed by
Client-Side Data encryption
Network Traffic Protection
Encryption / Integrity / Identity
AWSIAMCustomerIAM

Example – RDS
• Foundational Services –
Networking, Compute, Storage
• AWS IAM
• Platform / Application
AWS
• Customer Data
• Firewall (VPC)
• Customer IAM (DB Users, Table
Permissions)
• High Availability
• Data Protection (Transit, Rest,
Backup)
• Scaling
Customers
RESPONSIBILITIES

AWS Global
Availability Zones
Edge Locations
Customer content
Customers
for Abstract Services
Managed by
Managed by
Data Protection by the Platform
Protection of Data at Rest
Network Traffic Protection by the Platform
Protection of Data at in Transit
(optional)
Opaque Data: 1’s and 0’s
(in flight / at rest)
Client-Side Data Encryption
AWSIAM

• Foundational Services
• AWS IAM
• Platform / Application
• Data Protection (Rest - SSE,
Transit)
• High Availability / Scaling
AWS
• Customer Data
• Data Protection (Rest – CSE)
Customers
Example – S3

Summary of Customer Responsibility in the Cloud
Customer IAM
AWS IAM
Firewall
Data
AWS IAM
Data
Applications
Operating System
Networking/Firewall
Data
Customer IAM
AWS IAM
Infrastructure
Services
Container
Services
Abstract
Services

Shared Responsibility
What about security OF the cloud?

Security Shared Responsibility Model
AWS is responsible
for the security OF
the cloud
AWS Global
Availability Zones
Edge Locations

Auditing - Comparison
on-prem vs on AWS
Start with bare concrete
Functionally optional – you can build a secure
system without it
Audits done by an in-house team
Accountable to yourself
Typically check once a year
Workload-specific compliance checks
Must keep pace and invest in security innovation
on-prem
Start on base of accredited services
Functionally necessary – high watermark of
requirements
Audits done by third party experts
Accountable to everyone
Continuous monitoring
Compliance approach based on all workload
scenarios
Security innovation drives broad compliance
on AWS

What this means
You benefit from an environment built for the most security
sensitive organizations
AWS manages 1,800+ security controls so you don’t have to
You get to define the right security controls for your workload
sensitivity
You always have full ownership and control of your data

AWS Global
Availability Zones
Edge Locations
Meet your own security objectives
Customer scope and
effort is reduced
Better results through
focused efforts
Built on AWS
consistent baseline
controls
Your own
external audits
Customers
Your own
accreditation
Your own
certifications

Navigating Shared Responsibility
Achieving accreditation or certification on
AWS is possible but how can we help?

Shared Responsibility & Security By Design
Phase 1. Outline your requirements
• Outline your policies, controls you inherit from AWS
• Document controls you own and operate on AWS
Phase 2. Build a Golden Environment
• Define your AWS resources and controls as Code
Phase 3. Enforce with the use of Templates
• Templates presented to users within Service Catalogue as Products within Portfolios
Phase 4. Perform validation checks
• Deploying your environment through Service Catalogue as Gold Templates you make your
environment audit ready

GoldBase — Security Control Responsibility Matrix
NIST SP 800-53 rev. 4 control security control matrix

GoldBase — Architecture Diagrams

GoldBase — CloudFormation Templates

GoldBase — Additional Resources

Getting help — AWS Compliance
Workbooks
– IT Grundschutz (TUV Trust IT)
– CESG UK Security Principles
– PCI Workbook – Anitian
– Audit Checklists
Whitepapers
– EU Data Protection
– Risk & Compliance
– Overview of Security Processes
– FERPA
FAQs
– PCI, HIPAA, EU Data Protection,
ISO 27001, 9001 etc…
Training
– eLearning: Security Fundamentals,
3 hour free online course
– Instructor Lead Training: 3day
course for Security Professionals
– Qwiklab: Security & Auditing Self
Paced Lab
Security Blog: http://blogs.aws.amazon.com/security/

Helpful Resources
Compliance Enablers: https://aws.amazon.com/compliance/compliance-enablers/
Risk & Compliance Whitepaper: https://aws.amazon.com/whitepapers/overview-of-risk-and-compliance/
Compliance Center Website: https://aws.amazon.com/compliance
Security Center: https://aws.amazon.com/security
Security Blog: https://blogs.aws.amazon.com/security/
AWS Audit Training: awsaudittraining@amazon.com

The AWS Shared Security Responsibility Model in Practice

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à The AWS Shared Security Responsibility Model in Practice

Similaire à The AWS Shared Security Responsibility Model in Practice (20)

Plus de Amazon Web Services

Plus de Amazon Web Services (20)

Dernier

Dernier (20)

The AWS Shared Security Responsibility Model in Practice

Notes de l'éditeur