Okay, it's now in the morning, again, we can start, can you please take a seat?
Welcome everybody, first of all, I would like to thank you for being here so early.
Much appreciated, it's Sunday and in the morning everybody's probably tired and hungover
but you made it.
Welcome to our nevroom, this is the Confidational Computing Devroom, as you probably
know already and before we start, I would like to give you a quick introduction of
the schedule and Confidational Computing in general and our people of the organizer itself.
So I am Ilaria, as you probably figured out and we also have two other Devroom manager
here, one is Paul and then there is your who happens to be probably on the bus right now,
so he will make it here very, very soon, hopefully and then there are three more people
who are unfortunately not here because they could make it for personal reasons, but regardless,
I would love to give them a very big shoutout in case they watch the recording and so there
would be free since Stefan and Fabiano and moving on, just a very quick introduction of Confidational
Computing because we want to keep this beginner friendly as well, so there are many definitions
of Confidational Computing but here I am going to use the one from the Confidational Computing
which is this organization under the Linux Foundation that brings together vendors,
the cloud providers and software developers to accelerate and standardize the user computer
computing and the third definition is actually the protection of data in use by performing
computation in a hardware base that has the trusted execution environment. So key phrase here is data
in use because we know already how to protect data and rest, we can use encryption or data over
the network with good break, all good, all good, all good. So I was saying if we want to protect
data and rest, the data over the network we can use encryption or TLS, but we also want to protect
data in use because if we are processing the data it is generally encrypted which means that
an admin and server can actually see the data. Confidational Computing is targeting exactly
this gap so it protects data while it is being processed by isolating part of the memory
in a trusted execution environment. This means that memory inside the trusted execution environment
is encrypted and even the US and the hypervisor are not able to access it. Of course this requires
a shift in trust so we don't have to trust the cloud provider but we have to trust the hardware
now. And of course we can also increase this trust by attestation. Now on the left there are
some common properties and on the right here we have context dependent properties. So the common
properties across all the trusted execution environments are confidentiality, integrity, data integrity
in code integrity and then we have some other properties that are not provided by all platforms.
For example, code confidentiality, alternative launches, programmability, attestability and recoverability.
And now to give you a quick overview of the timeline of the technical evolution of Confidational
Computing. It started around 2015 with workload isolations within TLS GX which is one of the
first technologies that was invented and then it shifted towards virtual machine isolation with
SIV, TDX, CCI and so on. And the current phase is actually about accelerators so GPUs,
full system rock solutions and so on and the other a different perspective in the same timeline.
Of course Confidational Computing started as an academic project and then slowly became a
false project. And now of course it's also a matter of adoption. So large scale read world
deployments. Of course this come with new set of technical challenges. But so feasibility is
done already. So now it's also a matter of improving reliability of Confidational Computing
and putting it in infrastructure. Now a quick overview of how the Devram is going to look
like today. So we have a lot of talks. So thank you everybody for submitting and thank you so
much for all our speakers. And our talks are going to encompass both firmware, hypervisor,
technologies, hardware platform and last but not least at the station. And if you want to take
a deeper look on our schedule this is how it's going to look like. I just want to I want to
to notice that there will be a five minutes between breaks so you can come and go and the speaker
can set up. I don't think we will do introductions of the speaker. So if you want to speak just
come with your laptop and put set it up. And yeah we will finish at 1245. Our schedule is kind of tight.
So I ask everybody in this room to keep the if you're speaking please keep it in time and if you
have questions and you don't have time for your questions please go to the hallway and move to the
hallway track. And at the inside of course enjoy the Devram. Thank you again for coming and I will
now give five minutes break and give time to the next speaker to come and present. Thank you.