Vikas Bhatia (@vikascb, Head of Product, Azure Confidential Computing) and Ron Perez (@ronprz, Intel Fellow, Security Architecture) talk about the technologies and architecture behind Azure Confidential Computing
SHOW: 472
SHOW SPONSOR LINKS:
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
PodCTL Podcast is Back (Enterprise Kubernetes) - http://podctl.com
SHOW NOTES:
Topic 1 - Welcome to the show. Before we dig into today’s discussion, can you give us a little bit about your background?
Topic 2 - Defense in Depth is a strategy that has long been in place in Enterprise computing. We’ve seen previous approaches that connected the OS or Application with the Hardware (e.g. Intel TXT). How has this space evolved over the last few years, and what are some of the reasons why we need another level of depth?
Topic 3 - Let’s talk about the technology basics of Confidential Computing. What are the software elements (Application, OS, SDK) and what are the hardware elements?
Topic 4 - What is the normal migration path for a company to move workloads into Confidential Computing environments? Is this primarily for new workloads, or does it apply to existing applications too?
Topic 5 - Azure has the ability to deliver either Confidential VMs, or recently added Confidential containers along with AKS. When does it make sense to be confidential in one part of the stack vs. other?
Topic 6 - What are some areas where you’re seeing the broader ecosystem (e.g. technology partners or end-user customers) beginning to expand out the functionality of Confidential Computing?
FEEDBACK?
FEEDBACK?