By VMware Director, Information Security Strategy, Craig Savage and VMware Senior Program Manager Eddie Eriksson
Starting a security program from scratch can be a tall order, especially in this constantly changing global business environment. Over the past few years, we have done just that by deploying and managing a Zero Trust program. We call the initiative Beyond Zero Trust. And we have certainly learned a lot!
This blog series is meant to provide some suggestions as to what considerations could be made when putting together a new security program. The information is meant to offer more than just cut-and-dry guidelines. Our aim is to outline our team’s honest, real-world experiences, including lessons learned and the best practices. To quote a famous film, we’ll cover the good, the bad and the ugly, so you can profit from our experience and ultimately realize a seamless deployment as well as hassle-free ongoing management.
Topics covered in this series will include committees, staffing, finance, communications, change management and executive sponsorship.
Blogs can only do so much
Obviously, introducing a new security program from scratch is a considered undertaking. That’s why we encourage you to contact your account team to schedule a briefing with us. No sales pitch, no marketing. Just straightforward peer conversations revolving around your company’s unique requirements.
For more background on Zero Trust, check out these blogs on the topic.
Blogs in this series released so far:
The importance of steering and audit committees
We look forward to hearing from you.
VMware on VMware blogs are written by IT subject matter experts sharing stories about our digital transformation using VMware products and services in a global production environment. To learn more about how VMware IT uses VMware products and technology to solve critical challenges, visit our microsite, read our blogs and IT Performance Annual Report and follow us on Twitter, YouTube and SoundCloud. All VMware trademarks and registered marks (including logos and icons) referenced in the document remain the property of VMware.
