aws shared responsibility model - aws symposium 2014 - washington d.c
Post on 15-Jan-2015
616 Views
Preview:
DESCRIPTION
TRANSCRIPT
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
AWS Shared Responsibility Model Deep Dive
Mark RylandChief Solutions Architect /
Worldwide Public Sector Teammarkry@amazon.com
Garret Grajekggrajek@secureauth.com
Rishi Bhargavarishi@mcafee.com
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Shared Responsibility Model
• SRM key to understanding and operationalizing security in the cloud
• Traditional “hypervisor up/down” division of responsibilities: a good starting place
• Today let’s add additional concepts and nuances
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Service Types• Infrastructure services• Container services• Abstracted services
– Source: “AWS Security Best Practices,” Nov 2013, p7
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Infrastructure services• Rich control of an “on-prem-like” capability• Separate control plane and data plane
– Caveat: in some sense all services are “container” services: API driven external configuration and control
• E.g.: Amazon Elastic Cloud Compute (EC2), Amazon Elastic Block Store (EBS), Amazon Virtual Private Cloud (VPC), etc.
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Container services• Joint control with service layer over an on-prem-like
capability• Separate control plane and data plane
– Typically services deployed on EC2
• E.g.: Amazon Relational Database Service (RDS), Elastic mapReduce (EMR), Redshift, Elastic Beanstalk, OpsWorks, Elastic Load Balancing, etc.– Level and type of co-administration vary from service to service
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Abstracted services• Network endpoints that responds to commands• Typically: unified control plane and data plane
(although logically distinct operations)• E.g.:
– Simple Storage Service (S3), Glacier, DynamoDB, SQS/SNS, CloudWatch, CloudFormation (unified control/data planes)
– Route 53, CloudFront (distinct control/data planes)
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Varying Responsibility Surface Area
Infrastructure services
Container services
Abstracted services
Configuration plus operation
Configuration
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Three More Dimensions of the SRM
• Type of service– Infrastructure, container, abstracted
• Security configurability– How many relevant knobs and dials?
• Breadth of cross-service security impact– Will configuration impact be broad, or primarily local?
• Potential for integration with on-prem security systems– Greater versus lesser potential for integration
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Four Dimensions: Matrix
Service type Abstract Container Infra
Security configurability Low Medium High
X-service impact Low Medium High
Integration potential Low Medium High
Increasing responsibility
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Example #1: EC2• Foundational infrastructure service• Lots and lots of security-related
features; configuration and operation requirements
• Major impact across services• Rich integration possible with on-
prem security/management at OS and/or app level
Service type Infra
Security config High
X-service impact High
Integration potential High
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#2: S3• Powerful abstract service• Lots and lots of security-related
features• Very foundational, used by
many other services and apps• Some indirect integration via
IAM; logs can be integrated with security tools
Service type Abstract
Security config High
X-service impact High
Integration potential Medium
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#3: RDS• Popular service managing relational
database engines– AWS is the OS and engine admin,
customer is the database admin
• Significant number of security-related features
• Cross-service impact typically low• Can be integrated with broader
database security tools
Service type Container
Security config Medium
X-service impact Low ?
Integration potential High
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#4: DynamoDB• NoSQL database increasingly
used across AWS solutions• Richly integrated with IAM
– Row and column-level access control via IAM policies, policy variables
• Some integration with security-related solutions via IAM– E.g., SAML, Web Identity Federation
Service type Abstract
Security config High
X-service impact Low
Integration potential Medium
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#5: Elastic MapReduce• Managed Hadoop offering• Customer and EMR service are
co-administrators of instances• Significant number of security
knobs/dials• Generally, low cross-service
impact– Unless utilized within Data Pipeline
Service type Container
Security config Medium
X-service impact Low ?
Integration potential Low
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#6: CloudWatch• Foundational service, but… • Primarily read-only data (not
counting alerts)• Not a lot of security knobs/dials• Low integration with security-
related solutions– High integration potential with management
solutions
Service type Abstract
Security config Low
X-service impact Low
Integration potential Low
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#7: CloudTrail• Critical security-related service• Primarily read-only data• Not a lot of security knobs/dials• High degree of important
integration with security-related solutions
Service type Abstract
Security config Low
X-service impact High
Integration potential High
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
#8: IAM• Most critical security-related
“service”• Operationally easy; config
options rich, powerful, complex• High degree of important
integration with security-related solutions
Service type Abstract
Security config High
X-service impact High
Integration potential High
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
AWS Government, Education, and Nonprofits Symposium Washington, DC | June 24, 2014 - June 26, 2014
Thank you!
Mark RylandChief Solutions Architect / Worldwide Public Sector Team
markry@amazon.comGarret Grajek
ggrajek@secureauth.com
top related