►
From YouTube: 2020.01.14 - Defend Staff Meeting
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
So
we
should
officially
welcome
me
how
to
the
team
so
welcome
glad
you
could
join
us
yeah.
So
do
you
mind
quickly
introducing
yourself?
Okay,.
A
A
E
D
A
F
A
D
D
D
D
Did
we
definitely
feed
back
on?
We
want
to
be
reasonable,
plus
so
you
know
reasonable,
plus
plus
reaching
so,
and
they
should
be
the
things
that
we're
focusing
on.
So,
if
you
don't
agree
or-
or
you
want
to
add
more
detail
or
you
think
we're
missing
something
completely
in
terms
of
goals,
for
the
group
definitely
comment
on
these
as
appropriate
in
terms
of
the
mission
and
vision,
it's
really
to
solidify
mission
is
long-term.
D
What
we're
trying
to
accomplish
what
we
want
to
be
doing
the
excitation
I
guess
for
your
terms,
much
the
other
one
is
we're
doing
more
in
the
short
term
in
a
bit
more
detail,
so
it's
great
to
make
sure
we're
kind
of
solidify
on
what
our
overall
priorities
are
and
how
we
go
about
things,
but
also
help
them
to
attract
new
new,
get
leverage
as
well
to
the
team.
So
definitely
that's
best.
The
reason
for
those.
A
Alrighty
so
a
couple
items
just
for
the
agent
at
number,
one
so
product
development
workflow.
This
is
something
that
has
been
recently
refreshed
by
buggy
lab
as
a
whole.
It's
something
that
we
haven't
brought
up
here
previously,
but
it's
something.
But
it
is
an
item
that
we
should
start
paying
attention
to
the
item
that
I'm
specifically
calling
out
our
workflow
labels,
which
are
mentioned
throughout
this
very
long
document,
and
it's
something
that
we
should
probably
that
it
would
be
great
if
we
as
a
practice,
we
could
start
using
as
a
part
of
our
daily
workflows.
A
C
A
Helps
kind
of
give
some
early
signings
if
we're
going
to
make
if
something
is
gonna
make
an
individual
release.
Well,
if
you're
back
in
engineer,
we'll
be
talking
more
about
this
later
this
week
and
our
one-on-ones,
but
I
wanted
to
bring
it
up
here,
just
because
this
is
something
that
is
becoming
a
little
bit
more
standardized
and
and.
C
A
A
Okay,
if
you
have
questions
we
can
still,
we
can
move
them
to
slack.
We
can
also
have
these
in
our
one-on-one
conversations
as
later
this
week.
Second
item
is
me
doing
a
plug
for
office
hours,
which
was
moved
today
to
today.
So
there's
an
open
agenda
that,
with
with
questions
that
we
can
start
seeding.
A
So
this
is
a
friend
of
mine
who
was
volunteer
to
come
in
and
start
talking
to
us
about
elasticsearch
best
practices,
whether
it's
having
to
do
setup
for
provisioning
or
access
patterns
or
index
creation
and
bi,
and
the
types
of
queries
that
we
can
in
questions.
We
can
start
we
can
use
this
particular
data
store
to
start
answering.
So
this
is
somebody
who
is
he's
doing
me.
A
A
favor
he's
he's
somebody
that
I've
worked
with
for
a
number
of
years
and
was
in
charge
of
setting
up
with
the
charge
of
architecting
our
use
for
this
particular
of
this
particular
technology
in
previous
organizations
that
I've
worked
with,
and
so
it's
he's
a
great
resource,
and
so,
if
you
have
questions
this
is
this
is
a
good
good
person
to
start
asking
so
so
link
to
that
agenda.
Document
is
available,
so,
if
you
cannot
attend,
please
add
your
questions.
This
will
be
recorded.
A
G
G
Is
our
like
kind
of
slow
strategy
to
kind
of
be
building
an
internal
elk
stack
then
for
some
of
our
features,
as
opposed
to
kind
of
like
we're
kind
of
building
the
e?
Now
right,
the
elasticsearch
of
that
and
then
we'll
have
long
yeah.
So
we
just
like,
but
not
decay
eventually
or,
however,
we
yeah
yeah,
okay,.
A
For
like
customer,
open
production
use
so
but
it's
great
for
prototyping
it's
great
for
exploration,
but
it
is
not
something
you
would
put
within
a
production
of
an
application
typically,
so
so,
but
yeah
this.
This
is
something
that
is
coming
as
a
part
of
the
deed.
Lab
architecture
monitor
is
using
it
as
well,
so
we're
pretty
well
aligned
with
other
groups
and
other
stars.
H
And
if
anybody
wants
to
see
what
those
research
requests
are
I
linked
to
the
issue
that
has
a
list
of
all
of
the
research
requests
that
she
is
that
she's
trying
to
prioritize.
So
we
were
gonna,
keep
moving
forward
with
this,
but
if
anybody
thinks
that
we
should
delay
it
to
prioritize
other
things,
please
let
me
know.
I
That
could
sounds
like
I
need
to
have
a
chat
with
Derek
on
that
one,
okay
and
I'll.
Let
you
know
the
only
reason
I'm
a
little
hesitant
to
scrap
it
for
too
long
is
that's
gonna
feed
into
both
the
laughs
and
The
Container
network
as
well.
So
yeah
I'll
have
to
take
a
look
and
get
you
an
answer.
Hopefully
by
end
of
today.
Okay.
H
Sounds
good
yeah
in
general,
I
think
there's
there's
a
lot
going
on
within
defend
and
engineering
on
the
back
end.
I
just
want
to
make
sure
that
as
UX
we
stay
involved.
We
stay
on
top
of
you
know
what
needs
might
be,
and
so,
let's
just
keep
that
communication
going.
We've
been
working
on
the
wofe,
oh
my
gosh
I
haven't
had
my
coffee,
yet
sorry,
the
the
first
release
the
MVC
of
the
WAP
statistics
reporting.
A
Trying
to
add
scope
to
that
particular
research,
but
I'll
jump
on
my
soapbox.
The
ability
to
do
configuration
weather
for
apps
that
we
are
utilizing
is
something
that
I
would
desperately
love
to
see
within
defend.
I
would
also
love
to
see
it
within
secure
I
would
love
to
elevate
the
configuration
we
have
out
of
environment
variables
and
into
the
UI
as
an
example.
So
just
configuring,
so
it's
this
has
broad
applicability
as
far
as
I'm
concerned.
Okay,.
H
A
E
Right
just
a
reminder:
cookie
minder
that
we're
going
to
have
live
debugging
session
on
the
wire
shears,
the
incremental
HTTP
headers
English
contours.
Tomorrow.
It's
not
going
to
be
today
because
we
have
someone
that
can
now
depend,
and
we
really
need
a
little
bunch
of
people
from
the
infrastructure
team,
because
we
know
they
have
access
to
production.
So
we
can't,
for
example,
compare
the
configurations
free
to
join.
If
you
want
well
best,
we
are
struggling
the
bits
to
be
honest
on
that
one
trying
to
reproduce
the
issue.
E
F
D
D
E
D
E
One
possible
way
to
solve
this
is
to
upgrade
to
the
latest
version
and
deploy
to
that
until
tomorrow,
and
if
we
don't
have
any
any
problem
with
the
new
version,
that
means
there
was
something
fixed
in
the
meantime.
We
don't
need
to
know
exactly
why
that
we
need
to
know
if
we
can
run
that
safely,
so
that
that
could
be
enough,
spend
too
much
time
in
this,
and
we
need
to
move
on.
F
But
we
actually
had
upstream
requirements
that
we
wanted
out
great
anyway.
The
most
recent
mod
security
index
finally
or
monthly
range
X,
finally
got
a
release,
cut
and
I
was
waiting
for
that
for
them
to
really
release
a
new
version
for
that,
and
that
just
happened
like
a
couple
days
ago,
so
I
didn't
mean
to
open
an
issue
for
that's
a
go.
D
D
D
D
D
D
D
I
think
that'd
be
great,
so
so
it's
a
good
point
so
hiring
so
going
back
to
the
top
of
the
table.
They're
hiring.
We
got
another
except
this
week.
That's
four
for
the
quarter.
I
think
we're
done
on
new
engineers
can
contribute
to
architecture
by
q4
with
the
primary
goals
we
had
there.
Do
we
call
that
done
Thomas.
You
think.
D
A
D
That's
those
are
floated,
and
that
was
as
expected
as
those
are
stretch,
goals
and
we've
moved
some
of
those
into
acute
q1
goals.
You
know
for
the
next
quarter,
so
threat
detection
is
on
hold
right
awaiting
resources.
You
know
time,
availability,
Alka,
okay,
Falco,
Network
policy,
cilium,
we're
gonna,
get
something
by
the
end
of
January.
That
is.
Is
there
a
current
thinking.
C
D
A
This
is
something
that
we
were
trying
to
get
done
and
by
January
we'd
have
to
make
twelve
seven
because
our
release
vehicle.
So
what
so
looking
at
a
12-8
this
is.
This
is
a
task,
at
least
on
the
back
end
that
has
become
parallelizable.
I
mean,
if
that's
not
a
words
that
I
have
made
it
up
and
I'm
going
to
stand
by
it
in
that
where
there
are
distinct
tasks.
That
can
be
that
we
can.
We.
D
F
That
keeps
bumping
there
is
two
or
three
outstanding
items.
I'm
gonna
be
pairing
with
Dylan
on
some
stuff
this
week
that
hopefully,
some
we
get
through
and
yeah
we're.
The
frame
is
completely
done.
So
just
some
blockers
on
the
back
end
for
reducing
false
positives-
and
you
know
squeezed
tighter
I,
didn't
want
to
call
it
just
one.
The
bullet
point
on
the
line
above
this,
though
that's
I,
just
added
some
root-cause
analysis,
but
we
just
merged
the
motsek
toggle
as
well.
A
A
There
are
too
many
questions
for
us
to
begin
work
on
it
at
this
time
as
such,
we're
working
to
defer
it
to
twelve
nine
at
the
at
least
until
twelve,
nine,
as
would
we
get
as
we
get
our
questions
answered
and
resources
that
were
there
we're
moving
over
to
first
class
of
stand-alone
vulnerability
objects
in
order
to
continue
to
put
effort
and
pray
our
priority
on
that
one.
Just
because
there's
so
much
value
locked
behind
it
and
we've
been
chasing
it
for
so
long.
J
Make
sense
to
me
Jonathan
you're,
in
the
same
page,
on
there
one,
oh
yeah
and
probably
conversation
yesterday,
I
just
think
it
also
came
down
to
the
the
monitoring
group
expecting
more
out
of
that
issue
than
we
were
wanting
to
put
into
that
issue.
So
there's
quite
a
bit
of
disconnect
on
that
page
as
well.
So,
like
Thomas
said
you
know,
we
need
to
get
in
sync
with
them.
I
think
before
we
can
move
forward
on
this
cool.