Downloaded 21 times
Uploaded by2nd Sight Lab
AWS Security Ideas - re:Invent 2016
The document provides security strategies for enhancing cloud security, emphasizing the importance of designing systems with security in mind. Key recommendations include centralizing security functions, implementing automated checks, utilizing immutable infrastructure, and ensuring effective key management. It also highlights the need for thorough endpoint security and maintaining secure logs to prevent breaches and intrusions.
More Related Content
Similar to AWS Security Ideas - re:Invent 2016
More from 2nd Sight Lab
AWS Security Ideas - re:Invent 2016
- 1. © 2016, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Teri Radichel | @teriradichel 11/28/2016 AWS Security Ideas Leverage The Platform - Enhance Security
- 2. Many companies havegotten past the belief that the cloud is not secure... But you still have to secure it. Here are some ideas for a more secure cloud. @teriradichel
- 3. Architect Systems ForSecurity First If system is designed by security professionals, Security is built in from the ground up. @teriradichel
- 4. Centralize and AutomateSecurity Functions Manage security via trained professionals. Limit mistakes due to lack of knowledge. @teriradichel
- 5. Build System asGatekeeper If changes have to go through gatekeeper… Every change can be monitored. @teriradichel
- 6. Build System asSecurity Training System Automate security checks at deployment… Train developers at the point of action. @teriradichel
- 7. Leverage Event DrivenSecurity Automation Monitor for unwanted behavior… Automatically respond. @teriradichel
- 8. Separation of Dutiesby Design If it takes multiple people to make a mistake… Chances are someone will catch the problem. @teriradichel
- 9. Immutable Infrastructure If itcannot change once it has been deployed… Malware cannot be installed after deployment. @teriradichel
- 10. Eliminate Published CVEs Accordingto 2016 Verizon Data Breach Report: Known CVEs cause majority of breaches. @teriradichel
- 11. A Key isa Password Keys: brute forced, lost, shared, stolen. RBAC may be more easily managed. @teriradichel
- 12. Use Key Hierarchies Limituse of each key to subset of data. If one key is stolen, limits the damage. @teriradichel
- 13. Make It EasyFor Developers Automate common security related functions. Simplify: authenticate, log, encrypt, deploy. @teriradichel
- 14. Consider Process vs.Technical Controls Think encrypting data in memory. May be more feasible to secure via process. @teriradichel
- 15. Think About WhoCan Change Controls If the control can be changed by lots of people… It is not an effective control. @teriradichel
- 16. Understand Reconnaissance Network scanslook for vulnerabilities to attack. Secure all endpoints. @teriradichel
- 17. The Benefit ofNetwork Security A kernel mode root kit makes machines lie. The network doesn’t lie. @teriradichel
- 18. Most Developers !=Network Professionals Implementing is not the same as securing. One hole in the fence enables intrusion. @teriradichel
- 19. Secure Your Logs Writeonce, read only, replicated. Ensure logs are not missing or deceiving. @teriradichel
- 20. Thank you! Teri Radichel| WatchGuard Technologies | @teriradichel