Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Security on AWS


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Security on AWS

  1. 1. AWS: Overview ofSecurity ProcessesRyan HollandEcosystem Solution Architect
  2. 2. AWS Computing Platform
  3. 3. AWS Security Model Overview Certifications & Accreditations Shared Responsibility Model Sarbanes-Oxley (SOX) compliance Customer/SI Partner/ISV controls ISO 27001 Certification guest OS-level security, including PCI DSS Level I Certification patching and maintenance HIPAA compliant architecture Application level security, including password and role based access SAS 70(SOC 1) Type II Audit Host-based firewalls, including FISMA Low & Moderate ATOs Intrusion Detection/Prevention DIACAP MAC III-Sensitive Systems Separation of AccessPhysical Security VM Security Network Security Multi-level, multi-factor controlled Multi-factor access to Amazon Instance firewalls can be configured access environment Account in security groups; Controlled, need-based access for Instance Isolation The traffic may be restricted by AWS employees (least privilege) • Customer-controlled firewall at protocol, by service port, as well asManagement Plane Administrative Access the hypervisor level by source IP address (individual IP Multi-factor, controlled, need-based • Neighboring instances or Classless Inter-Domain Routing access to administrative host prevented access (CIDR) block). All access logged, monitored, • Virtualized disk management Virtual Private Cloud (VPC) reviewed layer ensure only account provides IPSec VPN access from AWS Administrators DO NOT have owners can access storage existing enterprise data center to a logical access inside a customer’s disks (EBS) set of logically isolated AWS VMs, including applications and resources Support for SSL end point data encryption for API calls
  4. 4. Shared Responsibility Model AWS Customer• Facilities • Operating System• Physical Security • Application• Physical Infrastructure • Security Groups• Network Infrastructure • Network ACLs• Virtualization • Network Configuration Infrastructure • Account Management
  5. 5. AWS Security Resources WhitepaperRisk and Compliance WhitepaperLatest Versions May 2011, July 2012respectivelyRegularly UpdatedFeedback is welcome
  6. 6. AWS CertificationsSarbanes-Oxley (SOX)ISO 27001 CertificationPayment Card Industry Data SecurityStandard (PCI DSS) Level 1 CompliantSSAE 16 (SOC 1) Type II AuditFISMA A&As • Multiple NIST Low Approvals to Operate (ATO) • NIST Moderate, GSA issued ATO • FedRAMPDIACAP MAC III Sensitive IATOCustomers have deployed various compliant applications such as HIPAA(healthcare)
  7. 7. SOC 1 Type IIAmazon Web Services now publishes a Service Organization Controls 1 (SOC 1), Type 2report every six months and maintains a favorable unbiased and unqualified opinionfrom its independent auditors. AWS identifies those controls relating to the operationalperformance and security to safeguard customer data. The SOC 1 report audit atteststhat AWS’ control objectives are appropriately designed and that the individual controlsdefined to safeguard customer data are operating effectively. Our commitment to the SOC 1report is on-going and we plan to continue our process of periodic audits.The audit for this report is conducted in accordance with the Statement on Standards forAttestation Engagements No. 16 (SSAE 16) and the International Standards for AssuranceEngagements No. 3402 (ISAE 3402) professional standards. This dual-standard report canmeet a broad range of auditing requirements for U.S. and international auditing bodies. Thisaudit is the replacement of the Statement on Auditing Standards No. 70 (SAS 70) Type IIreport.This report is available to customers under NDA.
  8. 8. SOC 1 Type II – Control ObjectivesControl Objective 1: Security OrganizationControl Objective 2: Amazon Employee LifecycleControl Objective 3: Logical SecurityControl Objective 4: Secure Data HandlingControl Objective 5: Physical SecurityControl Objective 6: Environmental SafeguardsControl Objective 7: Change ManagementControl Objective 8: Data Integrity, Availability and RedundancyControl Objective 9: Incident Handling
  9. 9. ISO 27001AWS has achieved ISO 27001 certification of ourInformation Security Management System (ISMS)covering AWS infrastructure, data centers in all regionsworldwide, and services including Amazon ElasticCompute Cloud (Amazon EC2), Amazon Simple StorageService (Amazon S3) and Amazon Virtual Private Cloud(Amazon VPC). We have established a formal programto maintain the certification.
  10. 10. PCI DSS Level 1 Service ProviderPCI DSS 2.0 compliantCovers core infrastructure & services• EC2, VPC, S3, EBS, RDS, ELB, and IAMUse normally, no special configurationLeverage the work of our QSAAWS will work with merchants and designated QualifiedIncident Response Assessors (QIRA)• can support forensic investigationsCertified in all regions
  11. 11. Physical SecurityAmazon has been building large-scale data centers formany yearsImportant attributes:• Non-descript facilities• Robust perimeter controls• Strictly controlled physical access• 2 or more levels of two-factor authControlled, need-based access forAWS employees (least privilege)All access is logged and reviewed
  12. 12. GovCloud US West US West US East South EU Asia Asia (US ITAR (Northern (Oregon) (Northern America (Ireland) Pacific Pacific Region) California) Virginia) (Sao Paulo) (Singapore) (Tokyo) AWS Regions AWS Edge Locations
  13. 13. AWS Regions and Availability ZonesCustomer Decides Where Applications and Data Reside
  14. 14. AWS Identity and Access ManagementEnables a customer to create multiple Users andmanage the permissions for each of these Users.Secure by default; new Users have no access toAWS until permissions are explicitly granted. UsAWS IAM enables customers to minimize theuse of their AWS Account credentials. Insteadall interactions with AWS Services and resourcesshould be with AWS IAM User securitycredentials.erCustomers can enable MFA devices for theirAWS Account as well as for the Users they havecreated under their AWS Account with AWSIAM.
  15. 15. AWS MFA BenefitsHelps prevent anyone with unauthorizedknowledge of your e-mail address and passwordfrom impersonating youRequires a device in your physical possession togain access to secure pages on the AWS Portal orto gain access to the AWS Management ConsoleAdds an extra layer of protection to sensitiveinformation, such as your AWS access identifiersExtends protection to your AWS resources such asAmazon EC2 instances and Amazon S3 data
  16. 16. Amazon EC2 SecurityHost operating system • Individual SSH keyed logins via bastion host for AWS admins • All accesses logged and auditedGuest operating system • Customer controlled at root level • AWS admins cannot log in • Customer-generated keypairsFirewall • Mandatory inbound instance firewall, default deny mode • Outbound instance firewall available in VPC • VPC subnet ACLsSigned API calls • Require X.509 certificate or customer’s secret AWS key
  17. 17. Amazon EC2 Instance Isolation Customer 1 Customer 2 … Customer n Hypervisor Virtual Interfaces Customer 1 Customer 2 Customer nSecurity Groups Security Groups … Security Groups Firewall Physical Interfaces
  18. 18. Virtual Memory & Local Disk Amazon EC2 Instances Encrypted File System Amazon EC2 Instance Encrypted Swap File• Proprietary Amazon disk management prevents one Instance from reading the disk contents of another• Local disk storage can also be encrypted by the customer for an added layer of security
  19. 19. EBS Wiping / Data DestructionBlocks Zeroed Out Upon ProvisioningLogical-to-Physical Block Mapping• Created during provisioning• Destroyed during de-provisioningFailed or Decommissioned Hardware• Degaussed• Physically destroyed
  20. 20. Network Security ConsiderationsDDoS (Distributed Denial of Service): • Standard mitigation techniques in effectMITM (Man in the Middle): • All endpoints protected by SSL • Fresh EC2 host keys generated at bootIP Spoofing: • Prohibited at host OS levelUnauthorized Port Scanning: • Violation of AWS TOS • Detected, stopped, and blocked • Ineffective anyway since inbound ports blocked by defaultPacket Sniffing: • Promiscuous mode is ineffective • Protection at hypervisor level
  21. 21. Amazon Virtual Private Cloud (VPC)Create a logically isolated environment in Amazon’s highly scalableinfrastructureSpecify your private IP address range into one or more public or privatesubnetsControl inbound and outbound access to and from individual subnets usingstateless Network Access Control ListsProtect your Instances with stateful filters for inbound and outbound traffic usingSecurity GroupsAttach an Elastic IP address to any instance in your VPC so it can be reacheddirectly from the InternetBridge your VPC and your onsite IT infrastructure with an industry standardencrypted VPN connection and/or AWS Direct ConnectUse a wizard to easily create your VPC in 4 different topologies
  22. 22. Amazon VPC Architecture
  23. 23. Amazon VPC Network Security Controls
  24. 24. Amazon VPC - Dedicated InstancesNew option to ensure physical hosts are not shared withother customers$10/hr flat fee per Region + small hourly chargeCan identify specific Instances as dedicatedOptionally configure entire VPC as dedicated
  25. 25. AWS Deployment Models Logical Server Granular Logical Physical Government Only ITAR Sample Workloads and Information Network server Physical Network Compliant Application Access Policy Isolation Isolation and Facility (US Persons Isolation Isolation Only)Commercial   Public facing apps. WebCloud sites, Dev test etc.Virtual Private     Data Center extension,Cloud (VPC) TIC environment, email, FISMA low and ModerateAWS GovCloud       US Persons Compliant(US) and Government Specific Apps.
  26. 26. Thanks! Remember to visit