Securing Public Cloud Usage by Default

As more and more of us migrate their business to the cloud, nothing is more important than safeguarding that infrastructure, especially with the steadily increasing number of threats. For example, one recent study notes that hackers attack every 39 seconds, on average 2,244 times a day. In addition to the potential security issues, not having clear visibility into your public cloud usage by development and other teams can cause servicing costs to needlessly explode. This is especially true as more and more of us invest in multi-cloud, multi-platform environments. At Adobe, one of the primary ways we scale our efforts is through automation. This is an effective way to monitor our infrastructure and detect security drift. We term our approach here as ‘securing the public cloud by default.’ Our approach is designed to detect security gaps during provisioning and help prevent teams from creating insecure cloud resources. This effort has also helped us get more visibility into how we are using public cloud resources across the company so that we can optimize our usage costs. In this session, Bogdan Ionita will talk about the security and visibility issues possible as public cloud usage continues to increase, best practices you can use to develop your own strategy for tackling these issues, and examples from our own approach that may be helpful as you work to address the issues.