►
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
Welcome
to
our
group
conversation
for
the
container
security
meeting.
Just
to
start
off,
anything
new
to
demo
looks
like
alexander's
got
something
alexander's,
not
on
the
call,
but
let
me
see
if
I
can
pull
it
up.
A
Looks
like
he's
added
the
warning
message:
if
you
do
not
have
an
agent
installed,
which
is
great
because
especially
where
right
now,
the
kubernetes
agent
service
is
disabled
on.com,
once
we
roll
this
out,
you
know
it
may
be
enabled
by
then
it
may
not
be,
and
even
if
it
is
enabled
users
may
or
may
not
have
an
agent
in
their
cluster.
A
A
So
this
next
one
is
optional.
There
was
some
discussion
about
whether
we
should
talk
about
this
now
or
later.
Some
of
the
ux
has
changed
slightly
for
our
project
level.
Das
scan
execution
policies,
epic,
that's
a
mouthful.
I
guess
this
mostly
impacts
you
alexander
on
the
front
end.
So
it's
up
to
you.
Do
you
want
to
talk
through
some
of
that
now?
Do
you
want
to
wait?
I
don't
really
care.
We
can
do
either.
One.
A
That
sounds
good
and
there
is
a
lot
that
still
is
changing,
so
I
mean
alan's
proposing
to
store
it
in
a
repository
instead
of
the
database,
which
is
going
to
impact
the
front
end
a
little
bit.
I
have
a
meeting
this
evening,
my
time
to
talk
about
it
with
thiago,
as
well
as
the
rest
of
the
das
team,
so
annabelle
our
ux
designer
plus
seth
and
derek
who's,
their
pm,
just
because
they're
also
planning
to
have
scheduled
scans
in
their
scan
interface,
and
so
we're
just
trying
to
make
sure
like
that.
A
This
is
gonna
work
with
all
the
groups
and-
and
so
there
is
a
little
bit
that
still
is
in
flux
there.
So
it
probably
wouldn't
hurt
to
wait
all
right
so
alexander
other
topics
to
discuss.
This
is
going
to
be
a
fast
meeting
today.
B
Yeah,
as
you
just
mentioned,
you
are
having
a
meeting
later
on
today
with
some
people
from
the
secure
group
about
the
das
on
demand,
and
I
I
just
saw
there
was
a
conversation
going
on
in
slack,
and
I
wanted
to
move
it
to
this
group
meeting
one.
So
we
like
have
record
that
we
talked
about
it,
but
also
just
consolidate
all
the
conversation
around
it.
So
you're
saying
they're
gonna
have
something
very
similar,
but
it's
going
to
be
different
enough
that
it's
not
that
we're
it's
fine
having
both.
A
A
A
Your
policies
are
something
that
you
want
enforced
like
you
want
that
to
have
to
happen,
whereas
you
know
your
scans,
maybe
an
auditor
requests
a
scan,
and
so
you
just
run
a
one-off
scan
for
the
auditor
or
you
know.
Maybe
the
developers
said
hey.
I
did
a
bunch
of
stuff
and
I
know
it
ran
in
the
pipeline,
but
can
we
run
it
again
just
to
check
you
know
whatever
the
case
may
be?
It's
just
like
a
one-off
scan
that
you're
running
on
your
own.
A
So
that's
what
they're
working
on
with
on-demand
scans
and
then
they
also
want
to.
Let
you
schedule
scams,
but
again
that
would
be
more.
A
So
that's
one
of
the
items
we
need
to
work
out
is
the
permissions,
because
that
would
be
more
like
for
a
developer
or
maintainer
to
run,
rather
than
like
the
security
team
requiring
that
it
has
to
run
every
week.
So
it's
just
a
slightly
different
persona.
Ideally
you
would
actually
you
know.
We've
talked
about
showing
them
in
both
places,
so
there
are
some
definitely
some
details
there
that
we
need
to
work
out
amongst
ourselves.
We're
going
to
talk
about
that
later
today,
with
those
scheduled
scans.
The
on-demand
scans
do
not
overlap
the
scheduled
scans.
Do.
C
Yeah
about
that
I
was,
I
was
thinking
that
what
we
are
doing
with
policies
and
what
they're
doing
with
on
on
demand,
scan
like
schedules
on
demand
scans
and
we,
as
you
said,
we
our
work,
is
about
enforcing
some
policies,
some
scans
to
run
given
time.
So
what
I
was
thinking,
okay,
we
can
have
like
everything
in
policy
I
mean
you
would
like
to
schedule
a
dust
scan
to
happen,
weekly
and
so
on,
and
then
what
it
should
do.
It
should
create
a
scheduled
dest
on
demand
test
scan
in
in
database
reuse.
C
Those
services
that
that's
team
is
gonna,
create
so
from
policies
there
will
be
like
one
directional
run,
directional
relationship.
We
have
it
in
policy.
That
means
we'll
create
it
in
this
table
for
schedule
on
demand
scheduled
scans,
but
not
like
the
opposite.
We
shouldn't
be
able
to
create
on
demand,
scan
that
it's
scheduled
and
on
desktoi,
and
then
that
that
will
create
a
like
policy
right.
A
C
Sense,
I
agree
yeah
and-
and-
and
that's
that's
also,
a
good
thing
if,
if
they
want
to
develop
that,
I
mean
that's
theme,
because
that
means
that
we'll
only
reuse
what
they're
we're
working
on
right
so
we'll
just
have
like
they'll,
create
all
the
models
for
schedules
and
to
to
do
actually
to
be
able
to
run
a
schedule
scan
and
we
in
in
security
policies
we're
just
gonna
reuse
that
so
that
will.
That
means
that
we'll
have
like
less
work
for
us,
but
the
same
time.
C
We
can
help
them
because
we're
already
thinking
about
models
and
about
what
to
do
and
so
on.
So
I
believe,
I
believe
we
have
a
spike
I'll
I'll,
add
links
to
spikes
under
my
comments,
so
you
you
could
use
that
in
your
conversation
with
with
derek
and
others.
A
Yeah,
that
would
be
great,
thank
you,
and
it
is
worth
noting
that
we
are
pretty
far
ahead
of
the
das
team
on
this,
like
we're
gonna
get
to
it
first,
so
it's
more
likely
that
they're
gonna
use
whatever
we
build,
then
that
we
will
use
what
they
build
so.
C
Got
it
got
it
so
maybe
maybe
we
should
the
way
we
should
like
start
working
on
that
one
is
to
help
them
build
their
feature
and
then
we'll
reuse.
That
feature,
because
that
will
be
like
the
best
way
to
approach
that
I
mean
for
some
time,
help
with
that
and
and
then
get
back
to
security
policies,
because
we
we
need
their
help
to
to
properly
design
it
and
properly
develop
that
because
they
have
the
expert
knowledge
about
tasks
and
how
they
would
to
have
that.
C
A
Yeah,
I
agree
so
and
I'm
I'm
supportive
of
that
too.
Actually,
I've
had
conversations
with
derek
on
that
topic.
Exactly
saying
hey,
you
know.
If,
if
your
work
is
a
roadblock
for
us,
maybe
we
have
our
developers
go
help
you
for
a
little
while
so
yep.
I
think
we're
thinking
on
the
same
line,
same
line
of
thought
there
and
we'll
record
the
meeting
later
today
and
post
it.
So
everyone
can
see
that
as
well.
D
D
It
can
happen
that
maybe
the
best
team
goes
a
little
bit
quicker
than
we
expect
and
we
end
up
with
different
same
path.
Different
paths
in
this
code
base
doing
almost
the
same
thing.
A
A
A
See
all
right!
Well,
thanks!
Everyone
we'll
talk
to
you
next
week
and
hopefully
we'll
see
you
on
thursday.