►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
That's
going
to
be
transmitting
cardholder
data
and
it
really
talks
about
evaluating
processes
to
rank
these
vulnerabilities
and
ways
to
actually
enforce
it
in
the
environment
to
make
sure
we're
not
introducing
any
critical
vulnerabilities
to
our
payment
systems
and
that's
really
what
6.5.6
has
to
do
with
as
well.
Now.
Not
only
do
we
bring
in
the
exact
language
of
the
control,
but
stackrocks
has
actually
done
the
interpretation
for
you.
So
we've
we've
measured
a
control
guidance
for
how
this
translates
to
kubernetes
and
we've.
A
A
If
there
are
risks
present
as
the
control
states
and
the
deploy
level
will
actually
use
the
admission
controller
to
fail
that
at
the
api
server
for
kubernetes
and
reject
anything.
That
goes
so
I'm
going
to
rescan
the
environment
now
for
pci
and
you'll,
see
I'm
at
81
right
now
and
now
I'm
at
83,
and
if
I
go
down
to
those
controls
I
see.
6.1
is
now
at
100
6.5.6,
also
at
100.