►
From YouTube: Defend:Container Security Weekly Group Discussion
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
B
With
the
requirements
for
using
llamo
to
apply
AB
security
policies,
we
haven't
resolved
it
yet
I
think
Arthur
today
is
gonna.
Take
a
stab
on
on
something
that
he
proposed.
I
just
wanted
to
update
that.
That
is
not
going
mean.
We
don't
have
a
solution.
So
the
the
what
the
comments
that
you
made
there
Sam
were
mostly
correct.
Arthur
has
has
replied,
so
if
he
still
doesn't
make
sense,
please
please
get
back
to
us.
B
A
Yeah
I'm
still
trying
to
process
all
of
this
and
understand
it
all
the
way
it
seems
like
another
complex
one,
I
haven't
had
a
chance
to
post
on
the
issue
yet,
but
I
do
want
to
clarify
that
even
if
the
ammo
is
not,
you
know
it's
from
the
policy.
Ui
is
not
being
stored
in
the
cluster
management
project,
I
think
for
psyllium.
If
they're
using
Auto
DevOps,
they
can
still
put
the
Amal
file
in
the
cluster
management
project
and
have
that
pushed
into
kubernetes
and
again.
B
We
will
so
that
the
goal
is
definitely
to
stick
to
Yammer
because,
as
we
mentioned
before,
we're
not
quite
ready
to
take
on
the
UI
there,
a
few
final
things
that
we
need
to
check
there
to
see
well
how
we
want
to
build
it,
but
hopefully,
we'll
know
later
today.
Arthur
is
too
good
to
to
try
your
idea
later
this
afternoon
today,.
B
A
A
C
Just
as
we
want
to
read
and
comment
on
documents
before
the
meeting,
whenever
possible,
that'll
help
us
be
more
efficient,
so
everybody
read
sing,
not
terminate
you
Arthur
it'sit'sit's,
everybody
I
just
saw
that
works
so
well
during
the
CEO
shadow
program
with
Sid,
and
the
group
is
direct
reports
and
others,
and
also,
rather
than
having
a
scribe
in
meetings,
which
we
sometimes
start
to
do
that
has
some
explicitly
or
or
gonna
it
just
kind
of
happens.
We
want
everybody
both
the
person
who
would
be
the
scribe
to
participate.
C
Everybody
should
be
typing
their
own
comments
as
they
talk
or
when
they
talk
to
just
after
just
before,
and
that
makes
to
the
scribe
can
fully
participate.
So
there
is
no
scribe
rather
than
and
so
that
people
who
can't
make
a
meeting
can
see
all
the
notes
and
read
it
as
well.
So
I
think
I
won't
try
to
do
that.
Any
any
comments
on
that
or
seem
reasonable
leave.
Arthur.
C
C
I
taste
right
right,
a
summary.
What
I
do
is
I
try
to
write
a
sum
after
I've
said
it
I
try
to
write
a
summary,
not
get
every
detail,
but
just
a
summary
of
what
I
said
and
that
helps
that
helps
trying
to
type
I've
seen
like
Eric
Johnson.
He
types
as
he
speaks
and
I
don't
know
how
he
does
it
I
can't
do
it
he's
just
maybe
some
practice
he's
really
good
at
it.
I
am
NOT.
C
I
can't
do
two
things
at
once,
like
that,
but
yeah
good
so,
and
that
that
that,
for
example,
hope
Zamir
here
today
and
in
the
next
meeting,
where
Arthur
and
Tiago
it's
you
know,
2
a.m.
your
time
and
we're
meeting
in
discussing
things.
Then
that'll
help
you
both.
You
know,
you
know
what
happened
better
than
good
stuff,
so
on
the
below
items,
so
Sam
I
think
you
have
a
thought
as
well
on
us
yeah.
A
C
B
E
E
B
C
A
C
A
C
D
C
A
So
I'm
not
gonna
cover,
though
I'm
not
going
to
show
the
video
through
zoom
the
Karl
created.
You
can
be
that
asynchronously,
but
I
do
want
to
share
the
Sigma
wireframes,
but
we're
shown
in
that
walkthrough.
So
we
take
a
look
at
those.
These
are
just
rough
wireframes,
but
this
is
for
container
host
security,
so
statistics,
so
we've
already
got
Web
Application,
Firewall
statistics
and
container
network
policy
statistics
here.
One
of
the
design
challenges
that
we're
running
into
is
that
we're
not
able
to
really
scale
this
with
the
current
design.
A
It
takes
up
a
lot
of
vertical
space.
You
know,
we've
got
this
big
Web
Application
Firewall
chart
and
this
big
you
know
container
network
policy
chart,
and
so,
if
we
go
to
add
another
one
for
container
host
security
and
I
think
the
label
on
this
one
is
wrong,
but
you
get
the
idea
container
her
security.
Now
that
starts
to
be
a
little
bit
overwhelming.
So
this
was
just
modeling
out
a
few
different.
You
know
wireframes
of
how
we
might
shrink
things
down
a
little
bit
put
two
charts
on
the
same
line.
A
You
know
what
it
might
look
like
if
it's
not
detected,
so
it
still
has
a
placeholder
there
and
after
some
discussion
with
Kyle,
we
were
looking
at
since
this
is
an
overview
page.
You
know
bringing
like
a
snippet
of
alerts
management
here
onto
this
page
as
well.
In
the
end,
we
decided
that
for
the
MVC
we
don't
want
to
do
that.
A
We
want
to
have
build
the
dedicated
alerts
page
first
and
bring
something
into
the
overview
tab
later,
but
this
is
a
design
that
you
know
we
could
potentially
resurrect
later
on
if
we
wanted
to
show
some
sort
of
summary
early
round
alerting
anyway,
so
just
some
rough
concepts
there.
This
is
not
ready
for
full
planning
breakdown.
Obviously
we're
still
doing
designs,
but
I
just
wanted
to
share
this
early,
because
I
know
that
there's
been
a
request
for
early
engineering
input
into
designs
as
well
as
requirements.
D
D
I
agree
that
it's
better
to
have
side
by
side,
rats
and
I
think
that's
how
management
group
does
graphs
on
the
maintenance
page,
so
I
think
it's
more
so
I
envisioned
and
maybe
since
how
grass
is
so
similar,
but
we
used
slightly
different
colors
and
I
have
a
question
that
goes
way
back
when
I
started
working
in
this
page,
should
they
maybe
somehow
in
our
work
with
management,
because
they're
suddenly
working
more
and
more
and
much
closer
to
the?
What
is
money
train?
A
Yeah,
that's
a
good
question.
Kyle
was
in
Europe
at
the
moment,
that's
not
where
he
normally
lives,
but
he's
kind
of
stuck
in
Europe
for
a
while.
So
when
he
gets
he's
not
able
to
attend
these
meetings,
given
the
time
zone,
so
I'll
make
sure
he
sees
that
note
here
in
this
and
see
what
he
thinks
about
that
approach.
I
think
that's
a
good
good
point
if
they're
similar,
but
the
colors
are
slightly
different,
but
we
might
want
to
align
there.
B
A
I
think
they
are
slightly
different,
I
think
what
you're
seeing
here
is
accurate,
so
for
the
Web
Application
Firewall
we're
just
flagging
anomalous
requests,
whereas
for
container
network
policy
it's
dropped.
Packets,
I
believe
that
is
accurate
for
what
we're
measuring
the
difference
being
that
in
Web
Application
Firewall,
you
can
put
it
into
logging
locally
blocking
thing,
but
your
policies
are
detecting
I,
don't
know
what
to
call
it.
A
B
A
So
we
have
our
issue
here:
it's
container
host
security
to
statistics,
and
again
we
already
have
these
two
charts
today.
They're
just
laid
out
slightly
differently,
so
just
be
adding
in
this
bottom
one
for
container
hosted
security
statistics.
If
I
can
talk
today
and
right
now,
so
the
proposal
here
as
well
and
again
we're
not
quite
ready
for
full
plans
right
down
on
this,
but
we're
I'm,
leaning
towards
the
metrics.
There
would
be
total
activity
and
the
normal
effectivity
would
be
the
two
attributes
that
we
would
measure
for
that
chart
that
we're
adding
in.
C
D
D
D
These
parameters,
leader
through
Prometheus,
yeah
and
again
parameters,
is
what
we
can
really
use
and
get
web
management
page
based
on
parameters
and
so
falco
global
parameters.
So
I
would
want
to
release
it
lots
at
histograms
hard
though
it
was
a
huge
discussion
back
in
the
day
40s,
and
we
decided
that
it's
fine
to
use
different
technologies,
but
I
still
believe
that
it's
just
much
harder
to
use
when
I
was
setting
up
for
them
across
to
his
own
stuff.
B
It's
one
it's
one
data
point
as
well,
but
that
index
lifecycle
management
issue,
an
elastic
stack
that
we
had
to
fix,
wouldn't
wouldn't
have
affected
us.
My
my
experience
with
elastic
is
that
index
management
is
heavy-handed
if
we
want
something
that
that
is
just
showing
numbers,
Prometheus
probe
a
lot
easier
to
yeah.
B
D
A
E
A
All
right
so
that
I
wanted
to
share
again
we'll
discuss
this
again
in
a
later
meeting
and
put
it
through
official
planning
breakdown.
But
you
know
just
wanted
to
get
early
engineering
input
on
this
and
avoid
bottling
everything
up
towards
the
end
of
the
iteration
when
we're
trying
to
do
everything
through
planning
breakdown
and
refining
that
all
at
the
same
time,
it's.
C
It's
great
stuff
that
says
I'm
looking
at
this
remind
me
of
the
comments
over
the
last
two
weeks,
I
heard
a
number
of
times
in
in
discussion
in
discussions
that
Sid
was
in
on
really
excited
about
the
Container
security
space
and
what
we're
doing
you
know
team
is
small,
of
course,
but
team
is
great
too.
So
it's
it's!
It's
really
exciting
stuff.
It's
Mason!
You
know
it's
very
new,
but
it's
really
exciting
stuff
and
can
really
add
a
lot
of
value
for
kid.
C
Lab
customers,
which
is
pretty
neat
one
little
tactical
I
added
for
beyond,
is
so
I.
Think
it's
great
saying
you
you
put
this
in
the
document
a
business
day
before
the
meeting,
which
is
great.
Can
you
also
when
you
do
that
post
in
slack
and
and
say
hey,
it's
ready
to
review,
take
a
look
and
then
folks
know
folks
then
know
to
look
I
think
that
might
help.
Maybe.
C
But
it's
a
day
it
would
have
been
I,
don't
know
yeah,
so
I
wouldn't
have
looked
even
if
I
saw
that
message,
because
I've
just
been
swamped
so
and
it's
not
good
or
bad.
If
you
would
have
so
if
you
would
have
seen
that
message,
a
message
like
that
Thiago
or
Arthur.
Would
you
have
looked
at
this
in
advance
of
the
meeting
yesterday.
B
C
D
C
Okay,
so
no
manual
messages,
just
perhaps
when
people
have
stuff
to
share
that
should
be
reviewed,
is
try
to
get
FRA,
no
guarantee
you
try
to
get
in,
maybe
more
than
one
business
day
in
advance.
Then
then
it'll
be
less
likely,
it'll
be
it'd,
be
more
likely
it'll
be
people
will
see
it,
and
also
everybody
should
endeavour
to
look
at
the
document
in
advance,
which
we
all
do
I
know,
but
you
know
we
need
to
continue
to
so
sound
reasonable
got.