►
From YouTube: Keynote: Back to the Future: Next-Generation Cloud Native Security - Matt Jarvis, Snyk
Description
Don't miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from 18 - 21 April, 2023. 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.
Keynote: Back to the Future: Next-Generation Cloud Native Security - Matt Jarvis, Director of Developer Relations, Snyk
This talk will be a look into one possible future, taking into account multiple strands of emerging technology, and viewed through an almost certainly subjective lens of folks who’ve both been around through multiple technology iterations over the last decade or more and have the t-shirts and scars to prove it. We’ll probably be wrong, but we might get some things right, and we aim to at least be thought provoking. An eye on the future over the hill is always a good idea in our humble opinion, and thinking about those propositions can often engender change in the present !
A
Thanks
folks,
okay,
so
a
decade
ago,
I
was
sat
on
my
own
in
this
semi-deralic
data
center
in
in
Manchester
bootstrapping,
an
open
set
public
Cloud
on
a
rack
of
second-hand
Hardware
bought
on
eBay
and
over
time
we
rebuilt
that
data
center.
We
built
a
team
and
we
built
a
real
platform
with
real
customers,
but
there
was
no
kubernetes.
There
was
no
docker.
Everything
was
pretty
good
for
its
time.
A
Everything
in
Version
Control,
orchestrated
using
puppet,
but
there
was
lots
of
brittle
bash
scripts
that
needed
regular
tending
and
we
took
that
platform
through
the
iso
27001
security
certification
and
the
experience
of
managing
security
back
then
was
pretty
difficult.
There
was
lots
of
manual
work
external
scans
using
things
like
nessus
custom,
vulnerability,
checks
in
nagios
and
very
limited
tooling
for
automation,
and
the
point
of
all
of
this
is
that
the
cycle
of
Technology
change
moves
pretty
fast
and
it's
only
getting
faster.
A
So
at
this
point
a
huge
disclaimer.
This
is
in
no
way
a
prediction
or
investment
advice.
History
is
littered
with
examples
that
most
things
in
technology
very
rarely
go
in
the
direction.
We
think
they're
going
to
so
you're,
going
to
hear
an
awful
lot
about
Keys
about
certificates
and
about
signing
this
year
and
it's
a
fairly
safe
prediction
that
artifact
signing
in
our
software
development
lifecycle
is
going
to
become
pretty
much
standard
and
public
key
cryptography
has
served
us
well
for
more
than
30
years.
A
So
this
is
a
quantum
computer
and
quantum
computers,
not
only
look
cool,
but
they
work
very
differently
to
classical
computers.
They
replace
the
idea
of
bits,
our
zeros
and
ones
with
Quantum
bits
or
qubits,
based
on
the
properties
of
quantum
mechanics
and
unless
you're
a
Quantum
physicist.
Most
of
quantum
mechanics
is
completely
mind-bending
for
normal
humans,
but
most
folks
might
be
familiar
with
the
concept
of
Schrodinger's
cat.
A
This
is
a
visualization
of
Shaw's
algorithm
developed
in
the
1990s
by
mathematician,
Peter
Shaw,
and
it's
widely
viewed
as
a
proof
that
quantum
computers
could
potentially
break
public
key
cryptography,
including
diffie-hellman
key
exchanges
and
algorithms
like
RSA,
and
this
might
be
theoretical.
But
some
researchers
think
that
this
could
happen
in
the
next
decade.
A
On
a
day
known
as
Q
day,
when
most
of
our
cryptography
would
be
broken,
our
certificates
would
be
vulnerable
to
man
in
the
middle
attacks,
and
our
encryption
would
be
cracked
now,
there's
a
lot
of
different
actors
involved
in
building
quantum
computers,
including
nation
states
and
three
letter
agencies.
So
we
may
never
actually
know
that
this
has
happened.
A
And
it's
serious
enough
for
governments
to
take
action
with
a
move
towards
new
kinds
of
algorithms
resistant
to
this
threat
of
quantum
Computing
post
Quantum
cryptography
and
in
the
US
niss.
The
National
Institute
for
standards
and
technology
has
been
running
a
competition
for
the
last
few
years,
and
the
algorithms
were
selected
in
2022
and
they've
all
got
very
cool
names.
Any
algorithm,
With
The
Star
Trek
reference
has
got
to
be
good
right,
but
at
some
point
it's
likely
we'll
all
need
to
switch
our
keys
of
certificates
and
our
infrastructure
over
to
these
new
methods.
A
So,
coming
back
to
signing,
I
don't
want
to
take
once
you
start
signing
everything.
What
we're
really
doing
is
building
chains
of
trust
and
the
reality
of
any
chain
of
trust
is
that
there
has
to
be
something
at
the
bottom,
that
we
can
actually
trust,
and
it's
obviously
very
important
that
we
trust
our
build
systems,
the
things
that
produce
our
artifacts
and
there's
a
couple
of
different
dimensions
to
this.
The
first
being,
can
we
trust
our
build
to
always
produce
the
same
thing
now?
A
This
may
be
maybe
kind
of
non-obvious,
but
there's
not
necessarily
any
guarantees
that
the
thing
you're
building
is
exactly
the
same.
Every
time
you
build
it
and
if
it's
not
exactly
the
same,
then
you
can't
really
guarantee
its
validity.
Even
slight
differences,
May
introduce
unexpected
Behavior
or
even
new
security
vulnerabilities.
A
A
Well,
this
reproducible
builds
concept
has
been
around
for
a
long
time
and
it
aims
to
do
exactly
that.
It's
a
set
of
software
development
practices
aimed
at
creating
bit
for
bit
identical
artifacts
every
time
we
run
the
process
and
lots
of
large
open
source
projects
already
practice
this,
but
we
again
hit
the
issue
of
what
can
we
trust
if
we
use
pre-built
binaries
in
our
build
pipeline?
A
A
Now,
there's
a
trainer
thought
that
even
the
smallest
general
purpose
operating
system
is
now
too
big
to
be
auditable
and
verifiable
by
a
human
and
there's
lots
of
interesting
work
happening
in
this
space,
with
projects
trying
to
build
the
smallest
possible
thing
that
can
boot
hardware
and
build
compilers,
which
can
then
build
other
things
and
so
on,
and
these
are
generally
written
in
low-level
languages
with
the
aim
to
be
human
auditable.
So
at
least
some
programmers
are
capable
of
reading
and
understanding
the
entire
code
base
and
we're
talking
about
really
really
tiny.
A
A
A
And
there's
an
argument
to
be
made
that
computer
architectures
have
remained
relatively
unchanged
for
more
than
30
years.
Yes,
they've
got
smaller,
they've
got
more
powerful,
but
fundamentally
the
way
the
CPU
Works
virtual
memory,
paging
multitasking
operating
systems
are
all
quite
similar
and
we're
still
using
the
same
paradigms
in
programming,
and
these
architectures
have
features
that
could
be
considered
contributory
to
certain
classes
of
vulnerabilities,
particularly
around
memory
safety.
A
So
it's
a
combination
not
just
of
Hardware
but
of
tool
chain
support
to
reduce
the
amount
of
vulnerabilities
that
an
attacker
can
exploit.
So
basically,
the
idea
of
least
privilege,
but
highly
scalable
highly
efficient,
as
it's
done
directly
in
the
CPU
and
Cherry's,
been
around
as
a
concept
since
around
2010,
but
there's
now
Hardware
that
actually
supports
it
in
the
form
of
this
Amarillo
board
and
there's
lots
of
development
going
on
to
widen
the
ecosystem
of
software
support
for
this
new
architecture.
A
So
we've
talked
about
cryptography.
We've
talked
about
build
systems,
we've
talked
about
hardware
and
architecture,
but
the
real
elephant
in
the
room
is
the
rise
of
artificial
intelligence
and
specifically
large
language
models.
Now,
unless
you've
been
living
under
a
stone,
you
will
have
seen
a
lot
of
traffic
about
chat
GPT,
since
it
was
released
back
in
November
and
the
growth
in
users
has
been
unprecedented
and
millions
of
people
have
been
trying
it
out,
and
you
know
whatever
your
your
feelings
about
chat
GPT
in
general.
A
If
you
actually
used
it,
it's
clear
pretty
quickly
that
this
technology
is
going
to
be
truly
transformational
for
how
we
interact
with
computers.
Entire
Industries
are
going
to
be
disrupted
by
these
abilities
to
write
complex
text
based
on
limited
human
input
and
pretty
quickly
after
the
release,
people
started
to
experiment
with
having
chat,
gbt
write
code
and
again,
the
results
here
have
been
pretty
extraordinary,
given
relatively
small
inputs
chat.
A
Gpt
is
already
capable
of
writing
mostly
correct,
complex
applications
in
multiple
languages,
manipulating
data
between
formats
and
translating
programs
between
different
programming
languages
and
even
writing
programs
in
fictional
programming
languages
and
whilst
it's
not
about
to
displace
programmers
just
yet
the
field
is
moving
incredibly
quickly.
We're
really
only
a
few
weeks
into
the
AI
Revolution
and
it's
already
clear.
That's
going
to
drive
massive
change.
A
If
the
future
involves
computers,
writing
programs
for
us,
where
we
only
really
care
about
the
output,
then
the
question
arises
about
why
computers
would
use
high-level
programming
languages
at
all
commuters,
don't
know
anything
about
programming
languages.
Languages
are
basically
abstractions
to
make
it
easier
for
human
programmers
to
program
computers,
everything's,
either
interpreted
or
compiled
down
to
something
the
computer
can
actually
run.
A
So
since
such
a
huge
proportion
of
our
issues
with
software
supply
chain
at
the
minute
come
from
how
we
assemble
applications
from
packages
and
libraries,
perhaps
the
era
of
AI
generated
programs
will
solve
that
problem
for
us
most
likely,
though
it
just
introduces
a
whole
new
raft
of
security
issues.
We're
still
back
to
our
starting
point
about
trust.
Can
we
trust
our
AI
model
and,
more
importantly,
is
it
plotting
a
robot
takeover
of
the
human
race
so
to
return
to
the
disclaimer?
Some
or
all
of
this
talk
is
highly
likely
to
not
come
true.