Earlier this year, McKinsey released a report titled “Making a secure transition to the public cloud,” the result of interviews with IT security experts from nearly 100 enterprises around the world.
Leveraging the expertise of Google Cloud and McKinsey security experts, the research presents a strategic framework for IT security on cloud and hybrid environments, and provides recommendations on how to migrate to the cloud while keeping security top of mind.
The research shows what many already know: that public cloud adoption is accelerating thanks to increased technical flexibility, simpler scaling, and lower operating costs.
What’s exciting is that the research also reveals that many Chief Information Security Officers (CISOs) no longer view security as an inhibitor to adoption but instead an opportunity—“In many cases [CISOs] acknowledge that cloud service providers’ security resources dwarf their own,” the authors write—and now these companies are focused on how to best adopt and configure cloud services for increased security.
This requires enterprises, cloud providers, and third-party service providers to work together collaboratively and transparently within a shared security model.
Google Cloud has long believed in creating trust through transparency, previously releasing a detailed overview of its infrastructure security, explaining their shared responsibility model, and how they already protect users and customers at the lower layers of the stack—and Google is thrilled to see McKinsey’s detailed endorsement of the same approach.
Related: Cloud Security: So are we secured (or not)?
Every company has different IT needs, but the report found two common security decisions companies take when adopting cloud services:
(1) defining the perimeter, and
(2) deciding whether to re-architect applications for greater manageability, performance, and security on the cloud (interestingly, only 27% of companies surveyed actually do this—change is hard).
The research identifies three common archetypes for perimeter security: backhauling, cleansheeting, and adopting cloud provider controls by default.
McKinsey uses these three models, along with the decision to re-architect applications for the cloud, to identify six “archetypes” for cloud security. Each archetype has its own tradeoffs:
There isn’t a “right answer” for security when making a move to the cloud—it depends on your company’s expertise, flexibility, and cost decisions.
And, you don’t have to use only one archetype. For example, Evernote describes in their migration story to Google Cloud Platform:
“For most of our controls we found an equivalent, cloud platform version. For data encryption at rest, we gained a security control that we hadn’t engineered on our own. For some controls, like IP whitelisting, we had to adapt our security architecture to not rely on traditional network controls.”
— Rich Tener, Director of Security, Evernote
Relying on cloud service provider security controls is “the most cost-effective approach,” the authors write.
“As organizations move more and more applications to the public cloud and lean towards using native CSP controls, a decrease in security operating and capex costs is likely.”
Eighty percent of companies that choose to rely primarily on the cloud provider’s controls and re-architect their applications in parallel see cost savings.
So, if you’re planning a cloud migration, where should you focus your security efforts? McKinsey asked respondents about their approach to applying cloud security controls in several areas to find out what companies are doing:
Article first appeared on the Salesforce blog.
Lava is an authorised Salesforce Partner in Malaysia and has more than a decade of experience in cloud solutions which includes marketing automation, CRM implementation, change management, and consultation. We pride ourselves in not just being a CRM partner but in also understanding the needs of our customers and taking their business to the next level.