AWS and its partners offer a wide range of tools and features to help you to meet your security objectives. These tools mirror the familiar controls you deploy within your on-premises environments. AWS provides security-specific tools and features across network security, configuration management, access control and data security. In addition, AWS provides monitoring and logging tools to can provide full visibility into what is happening in your environment. In this session, you will get introduced to the range of security tools and features that AWS offers, and the latest security innovations coming from AWS.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Bill Shinn
Principal Security Solutions Architect, AWS
April 19, 2016
Getting Started with AWS Security

2. Prescriptive approach
Understand
AWS
security
practice
Build strong
compliance
foundations
Integrate AWS
Identity and
Access
Management
Enable
detective
controls
Establish
network
security
Implement
data
protection
Optimize
change
management
Automate
security
functions

3. Understand AWS security
practice

4. Why is enterprise security traditionally hard?
Lack of visibility Low degree of automation

5. AND
Move
fast
Stay
secure

6. Making life easier
Choosing security does not mean giving up
on convenience or introducing complexity

7. Security ownership as part of DNA
• Promotes culture of “everyone is an owner” for security
• Makes security a stakeholder in business success
• Enables easier and smoother communication
Distributed Embedded

8. Strengthen your security posture
Get native functionality and tools
Over 30 global compliance
certifications and accreditations
Leverage security enhancements gleaned
from 1 million+ customer experiences
Benefit from AWS industry leading
security teams 24/7, 365 days a year
Security infrastructure built to
satisfy military, global banks, and other
high-sensitivity organizations

9. 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 and access management
Operating system, network, and firewall configuration
Customer content
Customers
Security is a shared responsibility
Customers are
responsible for
their security IN
the cloud
AWS is
responsible for
the security OF
the cloud

10. Security training
Security Fundamentals on AWS
(Free online course)
Security Operations on AWS
(Three-day class)
Details at aws.amazon.com/training

11. Build strong compliance
foundations

12. AWS assurance programs
AWS maintains a formal control environment
• SOC 1 Type II
• SOC 2 Type II and public SOC 3 report
• ISO 27001, 27017, 27018 Certification
• Certified PCI DSS Level 1 Service Provider
• FedRAMP Authorization
• Architect for HIPAA compliance

13. AWS account relationship
AWS
account
ownership
AWS
account
contact
information
AWS Sales
AWS Solutions Architects
AWS Support
AWS Professional Services
AWS Consulting Partners

14. AWS Trusted Advisor
AWS Trusted
Advisor

15. Integrate identity and access
management

16. AWS Identity and Access Management
IAM users IAM groups IAM roles IAM policies

17. Account governance—new accounts
InfoSec’s
cross-
account roles
AWS account
credential
management
(“Root account”)
Federation
Baseline requirements
Actions and
conditions
Map
enterprise
roles

18. Enable detective controls

19. AWS CloudTrail and Amazon CloudWatch
AWS
CloudTrail
Amazon
CloudWatch
 Enable globally for all AWS Regions
 Encryption and integrity validation
 Archive and forward
 Amazon CloudWatch Logs
 Metrics and filters
 Alarms and notifications

20. Establish network security

21. AWS global footprint
12 AWS Regions (10
public, China region and
GovCloud region)
Canada, Ohio, India, UK,
and another China region
planned for 2016 and
beyond
32 Availability Zones
(adding 11 more in 2016
across new AWS Regions)
55+ edge locations
Region
Edge location

22. VPC Public Subnet 10.10.1.0/24 VPC Public Subnet 10.10.2.0/24
VPC CIDR 10.10.0.0/16
VPC Private Subnet 10.10.3.0/24 VPC Private Subnet 10.10.4.0/24
VPC Private Subnet 10.10.5.0/24 VPC Private Subnet 10.10.6.0/24
AZ A AZ B
Public
Elastic Load Balancing
Internal Elastic Load Balancing
Amazon
RDS
Master
Auto Scaling
Web Tier
Auto Scaling
Application Tier
Internet
Gateway
Amazon
RDS
Standby
Snapshots
Multi-AZ RDS
Data Tier
Existing
Data Center
Virtual
Private
Gateway
Customer
Gateway
VPN Connection
AWS
Direct Connect
Network
Partner
Location
Administrators and
Corporate Users
Amazon Virtual Private Cloud

23. Availability Zone A
Private subnet
Public subnet
Private subnet
Availability Zone B
Public subnet
Private subnet
ELB
Web
Back end
VPC CIDR 10.1.0.0/16
ELB
Web
Back end
VPC
sg_ELB_FrontEnd (ELB Security Group)
sg_Web_Frontend (Web Security Group)
Security groups
sg_Backend (Backend Security Group)

24. Security groups

25. Security groups

26. Security groups

27. VPC Flow Logs
• Agentless
• Enable per Elastic Network Interface (ENI), per subnet, or per VPC
• Logged to Amazon CloudWatch Logs
• Create CloudWatch metrics from log data
• Alarm on those metrics
AWS
account
Source IP
Destination IP
Source port
Destination port
Interface Protocol Packets
Bytes Start/end time
Accept
or reject

28. VPC Flow Logs
• Amazon
Elasticsearch
Service
• Amazon
CloudWatch
Logs
subscriptions

29. VPC Flow Logs—CloudWatch alarms

30. Implement data protection

31. Cryptographic services
Amazon
CloudHSM
 Deep integration with AWS services
 CloudTrail
 AWS SDK for application encryption
 Dedicated HSM
 Integrate with on-premises HSMs
 Hybrid architectures
AWS Key Management Service
(AWS KMS)

32. Optimize change management

33. AWS Config and Config rules
AWS
Config
Amazon
Config rules
 Record configuration changes
continuously
 Time-series view of resource
changes
 Archive and compare
 Enforce best practices
 Automatically roll back unwanted
changes
 Trigger additional workflow

34. AWS Config

35. AWS Config

36. AWS Config rules—tenancy enforcement example

37. AWS Config rules—tenancy enforcement example

38. AWS Config rules—tenancy enforcement example

39. AWS Config Partners

40. AWS CloudFormation—infrastructure as code
Template StackAWS
CloudFormation
 Orchestrate changes across AWS
services
 Use as foundation to AWS Service
Catalog products
 Use with source code repositories to
manage infrastructure changes
 JSON-based text file describing
infrastructure
 Resources created from
a template
 Can be updated
 Updates can be
restructured

41. Change sets—create change set

42. Change sets

43. Change sets

44. Automate security functions

45. Evolving the practice of security architecture
Security architecture as a separate function can no longer
exist
Static position papers,
architecture diagrams, and
documents
UI-dependent consoles and
technologies
Auditing, assurance, and
compliance are decoupled,
separate processes
Current security
architecture
practice

46. Evolving the practice of security architecture
Security architecture can now be part of the “maker” team
Architecture artifacts
(design choices, narrative,
and so on) committed to
common repositories
Complete solutions account
for automation
Solution architectures are
living audit/compliance
artifacts and evidence in a
closed loop
Evolved security
architecture
practice
AWS
CodeCommit
AWS
CodePipeline Jenkins

47. Demo
Amazon Machine Image (AMI) factory

48. AWS Marketplace security partners
Infrastructure
Security
Logging and
Monitoring
Identity and
Access Control
Configuration and
Vulnerability
Analysis
Data
Protection

49. Prescriptive approach—get started!
Understand
AWS
security
approach
Build strong
compliance
foundations
Integrate AWS
Identity and
Access
Management
Enable
detective
controls
Establish
network
security
Implement
data
protection
Optimize
change
management
Automate
security
functions