(sec201) aws security keynote address | aws re:invent 2014

61

Upload: amazon-web-services

Post on 24-Jun-2015

1.807 views

Category:

Technology


0 download

DESCRIPTION

Security must be at the forefront for any online business. At AWS, security is priority number one. Stephen Schmidt, vice president and chief information officer for AWS, shares his insights into cloud security and how AWS meets our customers' demanding security and compliance requirements, and in many cases helps them improve their security posture. Stephen, with his background with the FBI and his work with AWS customers in the government, space exploration, research, and financial services organizations, shares an industry perspective that's unique and invaluable for today's IT decision makers. At the conclusion of this session, Stephen also provides a brief summary of the other sessions available to you in the security track.

TRANSCRIPT

Page 1: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 2: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

JOB ZERO

Page 3: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Job Zero

Network

SecurityPhysical

Security

Platform

SecurityPeople &

Procedures

Page 4: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

SHARED

Page 5: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

constantly improving

AWS Foundation Services

Compute Storage Database Networking

AWS Global Infrastructure Regions

Availability Zones

Edge Locations

AWS is

responsible for

the security OF

the Cloud

GxP

ISO 13485

AS9100

ISO/TS 16949

Page 6: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

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 applications & contentC

ust

om

ers

shared responsibility

Customers have

their choice of

security

configurations IN

the Cloud

AWS is

responsible for

the security OF

the Cloud

Page 7: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

FAMILIAR

Page 8: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

familiar

– Agility

Page 9: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

VISIBILITY

Page 10: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

VISIBILITY

RIGHT NOW?

Page 11: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 12: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 13: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Visible

Page 14: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

You are making

API calls...On a growing set of

services around the

world…

AWS CloudTrail

is continuously

recording API

calls…

And delivering

log files to you

AWS CLOUDTRAIL

RedshiftAWS CloudFormation

AWS Elastic Beanstalk

Page 15: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Use cases enabled by CloudTrail

Page 16: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

CloudTrail Regional Availability

Page 17: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

AUDITABILITY

Page 18: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

and notifies you

Page 19: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Continuous ChangeRecordingChanging

Resources

AWS Config

History

Stream

Snapshot (ex. 2014-11-05)

AWS Config

Page 20: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 21: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 22: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 23: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 24: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 25: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Integrated Support from Our Partner Ecosystem

Page 26: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

CONTROL

Page 27: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

First class security and compliance

starts (but doesn’t end!) with encryption

Automatic encryption with managed keys

Bring your own keys

Dedicated hardware security modules

Page 28: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Encryption & Best Practices with AWS

Managed key encryption

Key storage with AWS CloudHSM

Customer-supplied key encryption

DIY on Amazon EC2

Create, store, & retrieve keys securely

Rotate keys regularly

Securely audit access to keys

Partner enablement of crypto

Page 29: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 30: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 31: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 32: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 33: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 34: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Nasdaq is a great example of security excellence in the cloud

Page 35: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Nasdaq Use Case Requirement

Replace on-premises data warehouse while keeping

equivalent schemas and data

Only one year of capacity remaining

4-8 billion rows of new information stored daily stock trading

Must cost less than existing system

Must satisfy multiple security and regulatory audits

Must perform similarly to legacy warehouse under

concurrent query load

AWS’s ability to satisfy multiple security and regulatory audits was critical to

Nasdaq’s migrating its data warehouse to AWS

Page 36: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Nasdaq Data Warehouse ImplementationPull data from numerous sources, validate data, and securely load into Redshift

Page 37: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

AWS CloudTrail to monitor and audit environment

Network isolation with Amazon VPC and AWS

Direct Connect

Encryption in flight using TLS and Amazon

Redshift JDBC connections

Encryption at rest with Amazon S3 (client-side,

AES-256) with Amazon Redshift cluster

encryption enabled and AWS CloudHSM

Nasdaq Security Best PracticesAWS CloudHSM integration was critical to Nasdaq adoption of AWS

Page 38: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Block key

Amazon

S3

Block key

Cluster key Cluster key

Master key

AWS

CloudHSM

1MB

1MB

Amazon Redshift and Encryption

Page 39: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

AGILITY

Page 40: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

AWS

Page 41: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

The practice of security at AWS is

different, but the outcome is familiar:

So what does your security team look like?

Page 42: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Everyone’s an owner

When the problem is “mine” rather than

“hers” there’s a much higher likelihood I’ll do

the right thing

Page 43: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Measure constantly, report regularly, and

hold senior executives accountable for

security – have them drive the right

culture

Our Culture:

Page 44: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Measure measure measure

• 5 min metrics are too coarse

• 1 min metrics just barely OK

Page 45: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Saying “no” is a failure

Page 46: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Apply more effort to the “why” rather than the

“how”

Why is what really matters

When something goes wrong, ask the “five whys”

Page 47: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Decentralize — don’t be a bottleneck

It’s human nature to go around a bottleneck

Page 48: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Produce services that others can consume

through hardened APIs

Page 49: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Test, CONSTANTLY

• Inside/outside

• Privileged/unprivileged

• Black-box/white-box

• Vendor/self

Page 50: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Proactive monitoring rules the day

• What’s “normal” in your environment?

• Depending on signatures == waiting to

find out WHEN you’ve been had

Page 51: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Collect, digest, disseminate, & use intelligence

Page 52: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Make your compliance team a part of your

security operations

Page 53: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Our Culture:

Base decisions on facts, metrics, & detailed

understanding of your environment and

adversaries

Page 54: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Simple Security Controls

Page 55: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014
Page 56: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

REDUCTION

Page 57: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

REDUCTION

Page 58: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

ENCRYPTION

Page 59: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

GRANULAR

SEPARATION

Page 60: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

BETTER OFF IN AWS

Page 61: (SEC201) AWS Security Keynote Address | AWS re:Invent 2014

Please give us your feedback on this session.

Complete session evaluations and earn re:Invent swag.

http://bit.ly/awsevals