Cloud computing has evolved from a bleeding-edge technology to the dominant platform for building and deploying new applications and services. While there are plenty of hand-wringing FUD sessions at industry conferences, there are few opportunities to learn the practical, hands-on skills for security IaaS and PaaS deployments. Many of your security skills still apply in the cloud, but you need to leverage them in new ways.
James Arlen leads a hands-on exploration of techniques for protecting the cloud, with extensive labs in Amazon Web Services. The first day focuses on root account security, virtual networking security, IAM, and logging/monitoring; the second day covers leveraging PaaS services, using immutable infrastructure, and automating security controls.
If you’re responsible for designing or architecting security for infrastructure- and/or platform-as-a-service deployments, if your organization is moving into cloud computing and you need the skills to defend it, or if you’re interested in learning how to secure Amazon Web Services and implement security automation for the cloud, this tutorial is for you.
James Arlen is a member of Heroku’s security team assisting customers in understanding how Heroku enables security programs and reduces the impact of compliance and security operations allowing them to move fast and focus on their apps. Over the past 20 years, James has delivered information security solutions to Fortune 500, TSE 100, and major public-sector organizations. James is a frequent speaker at industry conferences and a prolific contributor to standards bodies and media. He is also a contributing analyst with Securosis and has a recurring column in Liquidmatrix Security Digest. He is best described as an infosec geek, hacker, social activist, author, speaker, and parent.
Comments on this page are now closed.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com