►
From YouTube: Lightning Talk: Computing Confidentially in the Clouds - Aeva Black, Azure Confidential Compute
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Lightning Talk: Computing Confidentially in the Clouds - Aeva Black, Azure Confidential Compute, Microsoft
A cloud is just someone else's computer -- someone that you trust in ways you may not even realize: to patch their infrastructure against the latest threats, to keep your data in the right country, and to only access it in legally compliant ways. What if you didn't have to trust them? What if you could audit the integrity of their systems at any time, isolate your work from cloud admins, and guarantee your data is processed only when and where you want? Sounds good, right? With new hardware coming online in all major cloud providers, Confidential Computing promises to alter this trust relationship - but the tech stack is still young, and it isn't integrated in cloud native yet. In this session, Aeva Black will present a vision towards this goal, introduce a few open source projects which facilitate it, and hold space for a discussion of future work.
A
A
It
belies
the
complexity
and
the
scale
of
operating
a
cloud
and
it
hides
all
of
the
work
underneath
those
layers
which
must
not
be
forgotten.
If
you
were
well
working
in
security
now,
if
you're,
not
cloud
provider,
then
your
operating
environment
is
fundamentally
different
today
than
it
was
before.
You
were
consuming
a
cloud
or
you're
using
a
cloud
whether
it
was
a
decade
ago
or
more,
but
contractually
speaking,
the
business
arrangements
or
agreements
around
responsibilities.
A
Requirements
to
protect
data
are
not
all
that
different
today
than
in
the
days
of
dedicated
hosting
when
everyone
got
their
own
bare
metal
server
and
over
time
we
have
added
a
lot
of
additional
security
protections
to
encrypt
data
at
rest.
Encrypt
data
in
transit,
we've
even
added
specialized
hardware
devices,
particularly
to
cloud
computing
environments
like
hsn's
and
tpms,
to
try
and
bring
some
of
the
security
promises
back
to
these
environments.
A
There
are
we
can
talk
about
three
different
isolation
models,
guest
guest,
guest
host
and
host
guest.
Traditional
hypervisors
only
support
two
of
these
right.
They
protect
the
host
against
potentially
malicious
guests,
because
if
a
guest
could
compromise
the
host,
it
could
then
get
at
other
guests,
and
we
don't
want
that.
A
A
Some
layer
below
the
guest,
if
the
compromise
with
a
threat
comes
from
there
today,
there
is
really
not
much
protection
in
the
guest
environment,
and
so
this
movement
by
the
industry
is
trying
to
trying
to
solve
that
particular
problem
or
that
that
threat
vector
now
no
security
solution
is
perfect,
and
so
this
should
be
seen
as
entirely
additive
to
any
existing
security
measures
you
might
have
in
place.
It's
also
still
very
early
days,
and
so
things
are
changing
pretty
rapidly.
A
Now
the
confidential
computing
consortium
itself
is
another
linux
foundation
project
like
the
cncf,
backed
by
some
of
the
same
companies,
a
lot
of
the
large
hardware
and
cloud
providers,
and
it
has,
as
a
group,
we've
defined
confidential
computing
as
the
protection
of
data
in
use
by
performing
computation
in
a
trusted
execution,
environment
and
all
these
companies.
Since
the
founding
about
a
year
and
a
half
ago,
a
lot
of
companies
have
come
together
to
really
rally
behind
this
cause
and
try
and
bring
this
vision
to
reality.
A
We've
also
identified
two
different
modes.
If
you
will
for
that
protection
based
on
hardware,
one
is
process
based
and
one
is
vm
based
or
application
based
and
so
the
in
the
process.
Isolation
scenario,
a
particular
trusted
environment,
is
set
up
where
a
process
is
run.
It's
launched
within
a
untrusted
guests
next
to
other
untrusted
processes,
and
this
works
through
the
cpu
itself
in
this
case
sgx.
But
that's
not
the
only
way
arm.
Trust
zone
has
a
pretty
similar
model
to
this,
and
it's
just
less
prevalent
in
cloud.
A
So
I
didn't
really
include
it
in
the
slide.
The
alternate
model-
the
vm
based
model,
actually
relies
on
the
hypervisor
to
launch
a
trusted
guest
operating
system,
but
it's
the
cpu
that
is
ultimately
isolating
that
environment,
that
memory
region,
those
memory
pages
from
other
guests,
from
the
hypervisor
and
from
other
hardware
devices.
A
Now
I
should
mention
tpms
and
hsns.
These
tools
have
been
around
for
a
while,
and
people
often
ask
how
are
they
different
than
tees?
A
tpm
lets
a
verifying
process,
verify
the
integrity
of
other
components
of
the
platform
like
the
hypervisor
or
the
hardware,
but
it
doesn't
isolate
memory.
It
doesn't
protect
against
a
changed.
A
Different
access
pattern,
but
it
might
let
you
detect
a
faulty
system
or
an
unpatched
system,
something
like
that
and
an
hsm
lets.
You
protect
the
confidentiality
of
some
small
amount
of
data
like
a
key,
but
it
doesn't
guarantee
the
integrity
of
the
application
processing
that
data
now
today
available
for
cloud
native
use,
intel
has
released
the
sgx
device
drivers
for
kubernetes,
which
is
pretty
awesome
and
azure,
has
also
been
working
on
some
similar
things
and
we
have
in
production
kubernetes
clusters
with
sgx
devices
enabled
in
them.
I
know
a
couple.
A
I
did
mention
at
the
beginning
of
this
talk
the
notion
of
trust
and
maybe
inverting
trust.
So
I
want
to
talk
more
about
that
and
I
need
to
introduce
two
legal
terms
now.
The
exact
definition
of
these
terms
varies
depending
on
what
regulation
you're
looking
at
what
region
you're
in
and
so
the
gdpr
here
in
europe,
for
example,
or
if
you're
in
california,
the
ccpa
other
states
like
washington,
have
other
laws
that
are
being
drafted
right
now.
I
know
india
is
looking
at
similar
laws.
A
A
Whenever
a
person's
data
is
handled
by
a
company
with
whom
they
have
established
a
relationship
like
say,
for
me,
my
email
provider,
that
company
is
the
data
controller.
They
are
controlling
the
data
on
my
behalf
and
according
to
our
agreement,
whatever
I
checked
and
signed
when
I
signed
up
for
that
email
provider,
now
that
data
controller
might
set
up
agreements
with
other
businesses
to
process
data
on
their
behalf,
maintain
backups
or
off-site
data
recovery
or
index
the
data
or
provide
some
other
services.
A
For
me,
those
data
processors
operate
on
the
data
on
behalf
of
or
under
the
guidance
of
the
data
controller,
and
so
there
are
obligations
as
far
as
protecting
my
data
on
both
of
those
entities
and
and
those
might
differ
between
different
laws
again.
So
I'm
not
going
to
give
advice
here,
but
just
broach
the
topic.
We
all
need
to
begin.
Considering
these
implications,
one
thing
is
important
to
think
about
that.
None
of
those
obligations
today
are
contractually
enforced
between
the
data
processor
data
controller.
A
It's
a
business
agreement,
there's
no
enforcement
at
a
hardware
or
a
crypto
level.
So
that's
today
what?
If,
what
if
we
could
enforce
policy
cryptographically,
you
know
notary,
is
working
on
enforcing
it
and
adding
that
capability
for
these
checksums,
for
what
images
are
run
and
signed
where
and
by
whom
and
that's
fantastic.
A
A
So
that's
cool.
What
if,
as
a
tenant,
I
could
lock
down
my
environment.
I
could
prevent
the
cloud
hosting
company
or
their
agents
or
anyone
else
using
the
environment
from
accessing
my
data
or
my
customers
data,
and
what,
if
I
could
verify
that
through
a
trusted
third
party,
even
if
my
data
controller
chose
through
business
agreements
to
have
someone
else
process
the
data
on
my
behalf,
what
if
I
could
still
maintain
that
enforcement
through
hardware
and
so
really
what?
If
we?
What
if
we
invert
the
trust
relationship
inherent
in
outsourced
computing?
A
A
They
recently
published
a
position
paper
that
proposes
the
implications
this
technology
could
have
on
the
gdpr
regulations
and
companies
underneath
it
that
it
might
strengthen
the
guarantees
that
data
controllers
are
able
to
make
and
thus
enable
more
companies
to
more
easily
comply
with
the
gdpr.
I
think
that's
pretty
awesome,
there's
a
lot
of
other
implications.
I
just
don't
have
time
to
go
into
here,
but
I
would
love
to
chat
with
you
about
them
and
I'd
love
it.
If
you're
interested
in
collaborating
on
this.
A
You
know
come
work
with
the
ccc
or
look
at
some
of
the
projects
around
confidential
computing
and
sgx
or
amd
sev
or
arm
trust
zone
and
find
ways
to
surface
up
those
capabilities
into
the
cloud
native
landscape
and
the
ccc
is
actually
planning
to
host
a
dev
summit.
Pretty
soon
stay
tuned
for
details.