Confidential Computing Needs to Go Mainstream
Confidential computing is a term you may have heard in the past, but it is also one that a lot of the industry is sleeping on. Many cloud providers are looking towards a world in the not-too-distant future where confidential computing is ubiquitous. While it is challenging to secure a computing environment to ensure the data brought into that environment is safe from even a cloud provider, it is even more challenging to expand that past the CPU motherboard and to AI and other accelerators. As such, it was time to get into confidential computing.
As a quick note: Confidential computing is an industry-wide effort, and needs to be. At the same time, we cannot go into every unique implementation of it, so instead, we are going to use AMD SEV-SNP for our examples since AMD is already powering many of the confidential computing cloud offerings and they are rapidly growing server CPU market share. We need to say AMD is sponsoring this.
When it comes to data security, most of us have been trained to think in two dimensions. We protect “data at rest” by encrypting it where it is stored. This can be on self-encrypting SSDs, in encrypted storage arrays, or encrypted by the application.
We protect “data in transit” by encrypting it between two endpoints. These days, virtually every website uses HTTPS. Inside large data centers, even network flows between machines are often encrypted as default behavior.
As an industry, folks realized that they needed a solution, especially for industries with strict confidentiality and sensitive data. Better put, after data at rest and data in transit became standardized, the next step was the hard one. That step is figuring out how to secure data that needs to be decrypted for processing while it is being decrypted.
Fundamental to confidential computing is the TEE or Trusted Execution Environment. The idea behind the Trusted Execution Environment is to create a virtual machine environment where the customer of that environment knows that it is secure and has not been tampered with, before bringing data to be processed there. Maybe in our example above, this would be like storing your money (data) in a bank so that it could be used in the banking system without directly exposing it to passers-by who want to pilfer funds.
This hardware-based TEE creates a secure enclave to protect both the code and the data inside it. When we say protect, that is not just from other virtual machines that may be running on the same system. Even the hypervisor and cloud provider are locked out. Getting to a TEE is not automatic.
Nomination link:
https://academicawards.sciencefather.com/award-nomination/?ecategory=Awards&rcategory=Awardee
Contact us: academic@sciencefather.com
Get connected Here:
You Tube: http://www.youtube.com/@academicawards
Facebook: https://www.facebook.com/profile.php?id=100093671170511
Instagram: https://www.youtube.com/channel/UCM-OlZD0B3uvxFE2dEITMhg
Linkedin: https://www.linkedin.com/in/harita-r-1b9861224/
YouTube: https://www.youtube.com/channel/UCM-OlZD0B3uvxFE2dEITMhg
#sciencefather
#academicawards
#confidentialcomputing
#dataprivacy
#securecomputing
#trustedexecution
#privacybydesign
#cybersecuritytrends
#securecloud
#edgecomputingsecurity
#zerotrustsecurity
#secureenclaves
Comments
Post a Comment