►
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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: Modern Least Privilege and DevSecOps - James Watters, CTO, VMware
Modern apps are more complicated than traditional apps—they have greater scale, change faster, and are more distributed (i.e., don’t have a traditional security perimeter). Although it may seem like this would make it more difficult to keep them secure in the long run, innovations in the cloud native space—such as automation—simplifies many aspects of security.
As the industry has increased the adoption of cloud native applications over the past decade, a clear set of best practices has emerged predicated on “least privilege.” Now, it’s time to dramatically improve enterprise application security by embracing a modern set of principles.
A
A
It
really
orients
around
the
idea
that
we
have
a
new
paradigm
around
modern
applications
that
introduces
new
ways
of
doing
security
in
addition
to
new
ways
of
doing
development
operations.
So
I'm
pretty
excited
about
the
overall
term
of
devsecops.
In
some
ways
it
you
know
it's
not
a
perfect
term,
but
it
galvanizes.
A
You
know,
maybe,
a
month
after
the
equifax
breach
happened,
and
you
know
he
looked
up
at
me
at
dinner.
He's
like
you
know.
If
that
happens
to
us,
I
have
to
sit
in
front
of
congress
and
he
basically
said
like.
Could
we
come
up
with
a
plan
so
that
that
would
not
be
the
default
in
my
organization
because
it's
not
fun
to
run
around
tasking
people
constantly
to
turn
the
wheels
like?
A
How
can
we
make
modern
security
more
of
an
affordance
of
an
overall
platform
or
system
that
I
run
as
an
organization
and
less
of
a
potential
and
a
lot
of
what
my
passion
in
the
space
is
around?
Is
that,
like
some
of
these
modern
security
principles
need
not
only
be
possible
within
the
cncf
community?
A
They
need
to
become
affordances
and
I
think
that's
sort
of
the
distinction
that
I'm
going
to
push
on,
and
maybe
some
of
my
thoughts
will
be
interesting,
and
so
my
ask-
and
my
call
to
action
is
like
if
you
agree
with
any
of
this
help,
make
me
smarter
about
it
or
help
push
it,
because
I
think
it
can.
Just
you
know,
help
us
all
in
our
day-to-day
jobs.
Does
that
sound
interesting
as
a
topic?
A
Oh,
I
got
more
than
one
thumb.
I'm
gonna
keep
talking
cool,
so
I
use
the
term
devsecops,
I'm
not
really
here
to
get
in
a
big
semantic
debate.
If
it's
the
cool
thing,
if
we
think
of
another
way
of
making
affordances
security,
first
class
performance
of
a
platform,
I'll
use
it.
But
that's
what
I
got
today
and
I
think
part
of
the
observation
of
modern
applications
was
that
they
weren't
quite
as
static.
A
Maybe
the
old
model,
I'm
old
enough
that
I
was
alive
in
the
90s
and
some
people
today
were
not
and
in
the
90s
I
started
working
at
a
big
iron.
You
know
tech,
company
called
sun,
and
every
year
we
would
deploy
a
server
anywhere
in
that
very
old
school
mode.
In
fact,
my
first
day
there
was
like
watching
a
customer.
A
Do
a
six
week
consulting
agreement
to
size,
a
server
six
weeks
to
size
the
server,
so
I've
really
lived
this
evolution
from
large
static
process,
driven
it
to
more
of
this
iterative
emergent
cloud
pattern,
but
I
do
think
that
iterative
emergent
pattern
is
super
interesting
and
so
I
think,
just
the
same
way
the
applications
change.
We
can
change
security
in
this
new
world
and
I'm
going
to
push
on
a
couple
dimensions
of
that,
but
I
do
like
to
study
history
a
bit
and
so
as
we're
you
know,
kind
of
suddenly
there's
this
craze
around.
A
A
They
were
much
more
collaboration
systems,
and
so,
while
the
70s,
we
were
clear
on
lease
privilege
so
anyway,
I'm
going
to
go
really
fast.
The
the
founder
of
yubikey
basically
said
think
about
the
web
as
a
different
paradigm,
the
least
privilege
it
was
a
sharing.
First,
you
know
set
of
tech.
Everything
is
about
sharing
fast,
and
I
see
devsecops
as
this
really
exciting
new
synthesis,
between
least
privileged
system
design
of
the
early
era
and
these
collaboration
technologies
that
we
built
like
http,
which
are
originally
just
like
here's,
my
document,
everyone
have
it
like.
A
So,
as
opposed
to
saying
to
that
developer,
you
need
to
always
scan
and
do
all
these
things.
With
your
app
by
hand
now
you're
saying,
there's
a
set
of
automations
that
introduce
mechanistic
least
privilege
to
the
pipeline,
and
I
do
think
paying
attention
to
things
like
build
packs
is
the
first
step
so
here's
some
stuff
I
did
in
my
previous
generation
of
technology,
it's
more
of
a
closed
system
called
cloud
foundry,
but
I
worked
with
a
lot
of
banks.
One
bank
runs
about
500
000
containers
on
this
platform
and
here's
what
they
love
about.
A
A
We
have
something
called
the
tonzo
application
platform
which
will
do
security,
scans,
signing,
etc
by
default
and
come
talk
to
me
more
about
this,
but
we're
baking.
Some
of
these
security
processes
right
into
the
developer
experience-
and
I
think,
what's
really
interesting-
is
that
we're
introducing,
I
think,
more
of
a
decomposed
set
of
templates
that
allow
you
to
express
the
semantics.
A
developer
should
see
what
the
app
operations
team
should
see
and
what
core
cluster
admins
should
see
in
a
way
that
allows
you
to
decompose
what
alders
call
a
monolithic
set
of
pipelines.
A
Some
people
run
into
more
like
a
microservice,
so
that
that
developer
can
reason
about
their
surface
area
and
a
lot
more
things
are
secure,
signed
by
default.
I
think
asking
developers
to
reason
about
a
2000
function.
Monolith
is
as
unreasonable
as
asking
them
to
reason
about,
like
a
giant
monolithic
pipeline
with
no
abstraction
for
them.
A
That's
my
observation,
and
then
we
can
bake
security
into
these
things,
and
the
final
note
I'll
leave
you
with
is
that
an
increasingly
secure
software
supply
chain
doesn't
eliminate
runtime
variants,
and
so
you,
like,
I
know
exactly
when
it
went
into
prod
and
now
it's
running
so
now.
What
has
it
done
since?
And
I
think
this
is
where
the
repaving
modality
is
so
important-
is
that
the
ability
now
that
you
trust
your
software
supply
chain
and
you
have
git
ops
functionality
to
constantly
recreate
it?
Why
not
use
that?
A
So
why
not
make
that
a
first
class
part
of
the
system?
And
so
what
I
want
to
do
with
tanzu
and
we're
increasingly
doing
with
technologies
like
cluster
api
is
introduce
programmatic,
affordances
to
constantly
repave
the
system,
to
constantly
repair
the
system,
as
vulnerabilities
come
out
and
to
constantly-
and
this
will
take
some
time-
rotate
shared
secrets,
credentials,
etc,
and
therefore
I
think
we
can.
Let
me
just
close
on
this.