32
November 13, 2014 | Las Vegas, NV SEC202 Closing the Gap: Moving Critical, Regulated Workloads to AWS Chad Woolf, Director, AWS Risk & Compliance

(SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

Embed Size (px)

DESCRIPTION

AWS provides a number of tools and processes to help you decide when and how to move audited, regulated, and critical business data to the cloud. In this session, we answer the following questions: when is it time for you to make this significant move? When will you be ready to address industry best practices for control (including third-party audits, access control configurations, incident response, data sovereignty, and encryption). We discuss how some highly regulated AWS customers have addressed the challenges that legacy regulatory requirements present to partners, vendors, and customers in migrating to the AWS Cloud. Finally, we cover general trends we're seeing in several regulated industries leveraging AWS and the trends we're seeing from the regulators themselves who audit and accept AWS control environments.

Citation preview

Page 1: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

November 13, 2014 | Las Vegas, NV

SEC202

Closing the Gap: Moving Critical, Regulated

Workloads to AWS

Chad Woolf, Director, AWS Risk & Compliance

Page 2: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 3: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 4: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 5: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 6: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 7: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 8: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 9: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 10: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 11: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

{

"configurationItems": [

{

],

"relationships": [

{

"resourceType": "AWS::EC2::NetworkInterface",

"resourceId": "eni-f097eca9",

"relationshipName": "Contains

NetworkInterface"

},

{

"resourceType": "AWS::EC2::SecurityGroup",

"resourceId": "sg-9ddbb9f8",

"relationshipName": "Is associated with

SecurityGroup"

},…

"resourceType": "AWS::EC2::Subnet",

"resourceId": "subnet-62dde924",

"relationshipName": "Is contained in Subnet"

},

{

"resourceType": "AWS::EC2::Volume",

"resourceId": "vol-122ede1d",

"relationshipName": "Is attached to Volume"

},

{

"resourceType": "AWS::EC2::VPC",

"resourceId": "vpc-ba9072df",

"relationshipName": "Is contained in Vpc"

}

],

"arn": "arn:aws:ec2:us-west-

2:350616417307:instance/i-7a220375",

"version": "1.0",

"configurationItemMD5Hash":

"f62b29193af10e25f713ba6f746de8b1",

Page 12: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 13: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 14: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 15: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 16: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

AWS CloudTrail

Page 17: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 18: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 19: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 20: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 21: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 22: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 23: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

Adopted by Large Healthcare Providers

Page 24: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 25: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

• Working to “achieve military-grade

security in a commercial setting”

Page 26: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 27: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 28: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 29: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

Singapore

MTCS

Page 30: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014
Page 31: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

https://run.qwiklab.com/

Page 32: (SEC202) Closing the Gap: Moving Critical, Regulated Workloads to AWS | AWS re:Invent 2014

Please give us your feedback on this session.

Complete session evaluations and earn re:Invent swag.

http://bit.ly/awsevals