►
From YouTube: Threat Management Staff Meeting 2020-12-02
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
Excellent,
so
threat
management
staff
meeting
for
december
2nd
lindsay
thanks
for
adding
the
accomplishments
in.
How
many
is
that,
since
the
last
meet
30.
B
B
A
The
so,
let's
see,
item
two
any
questions
about
the
additional
teams
and
growth
that
I'm
responsible,
for
I
don't
think
I
may
have
to
bring
that
up
in
a
group
session
yet
so
I
figured
out
how
to
ask.
A
I'm
seeing
some
noso,
I'm
I'm
drinking
from
the
fire
hose
in
a
big
way.
I
feel
like
I'm
going
through
onboarding
again
just
it's
a
lot
of
components,
a
lot
of
t
a
lot
of
people,
a
lot
of
what
is
going
well,
what's
not
going
well
what
the
priorities
are,
what
the
okrs
are
etcetera,
but
it's
really
exciting
and
fun
stuff.
So
it's
still
very
much
in
the
middle
of
it.
Like
I
haven't
met.
I've
only
met
about
a
third
of
the
folks
in
coffee,
chats
on
the
team.
A
Not
yet
hey
growth
has
needs
from
other
teams
and
vice
versa,
all
their
teams,
including
ours.
So
there
might
be
some
stuff
shared
there,
but
we'll
see
so.
The
department's.
A
Interaction
so
far,
and
it
was
how
we
collect
data
on
usage,
and
but
there
was
like
a
thread
from
six
weeks
ago,
where
david
convinced
gila
as
david's
peer
in
product
management,
then
what
we're
doing
is
good
enough
for
now,
and
we
have
bigger
fish
to
fry
and
threat
management
than
changing
how
we
collect
our
data
from
telemetry,
which
is
just
fine.
Anyone
open
up
that
camera
again,
but
there
might
be
something
in
the
future.
Like
you
know,
they
ask
us
to
do
things.
It's
that
interesting,
but
yeah.
A
You
know
I'm
also
looking
at
how
they
operate,
how
we
operate.
What
can
both
sides
learn
from
each
other
and
like
there's?
No,
mr,
in
growth,
for
a
narrow,
mr
rate,
for
the
team,
and
I
think
we
can
probably
get
away
with
that.
We
can
get
away
from
having
one
ourselves
because
we've
kind
of
hit
steady
state,
so
they
don't
have
one
because
they
don't.
A
They
didn't
feel
the
need
to
have
one-
and
I
think,
maybe
in
in
q1
we
probably
won't
need
one
anymore
either
or
how
meetings
are
organized
and
other
stuff.
So
it's
it's
it's
very
interesting.
So
so
we
all
won.
I'm
sorry
lindsay
want
to.
I.
B
B
A
We
are
two
separate
sub
departments
just
happens
to
be
me
as
the
manager
of
the
hey
jonathan,
the
manager
of
the
of
the
engineering
managers.
So.
A
Maybe
but
overall
it's
it's
a
great
question.
Like
you
know,
we
have
a
combined
manager,
slack
channel
for
threat
management
and
growth.
Just
that
and
we
we're
talking
about
doing
you
know,
combine
potentially
a
combined
social
day
or
you
know,
holiday
social
day
thing.
A
I
think
that's
where
things
overlap,
otherwise
it's
or
like
I
asked
and
no
but
nobody
jumped
on
it
and
that's
fine,
like
we
have
a
bunch
of
hiring
to
do
in
growth
for
back-end
engineers
and
because
that
team's
growing
a
good
bit
and
you
know,
do
we
want.
Does
anybody
on
the
back
end
team
for
threat
management
want
to
help
with
the
hiring
right
and
some
people
might
some
some
some?
Maybe
nobody
does
and
that's
fine,
but
I,
like
I
put
the
call
out
in
both
directions.
A
So
I
think
it's
things
like
that.
Just
I
happen
to
be
aware
of
things
on
on
both
sides.
So
I've
also
brought
my
experience
as
a
customer
of
telemetry
threat
management,
customer
telemetry
to
the
growth
team
saying
well.
This
was
my
experience.
What
do
you
think
of
this,
or
what
do
you
think
of
that
you
know
etc?
So
so
that's
been
good
as
well.
Just
bringing
up
that
kind
of
perspective.
B
A
Started
just
because
growth
is
separate,
then
fulfillment.
A
B
That's
what
I
saw
in
this
growth,
social
discussion
with
gila
and
bartek
and
folks
that
fulfillment
would
also
be
part
of
this.
So
I
did
update
the
issue.
That's
linked
here
in
the
agenda
for
folks
who
are
interested
to
include
not.
It
was
originally
just
an
issue
for
the
growth
team,
so
I've
added
threat,
management
and
fulfillment
to
it.
They'd
originally
scheduled
this
or
tentative
date
of
december
11th,
which
is
next
friday.
So
I
just
added
a
comment.
Saying:
hey
fridays
are
hard.
We've
got
a
lot
of
team
members
in
the
apec
region.
B
That
would
be
saturday
for
them.
You
know
the
following
thursday
is
the
will
be
the
friends
and
family
day
for
the
folks
in
apac,
so
scheduling
the
date
is
still
tbd.
It
could
potentially
be
next
thursday,
but
that
seems
very
soon
so
if
we
can
pull
together
a
full,
you
know
agenda
of
fun
things
to
do
which
again
much
like
the
last
time.
We
did.
The
threat
management
team
day
will
be
optional.
We
encourage
participation,
but
you
know
we're
not
gonna
require
it
at
all.
We'll
keep
you
posted
on
the
date,
so
they.
C
I
am
surprised
at
how
many
teams
are
under
the
growth
subgroup.
There's
like
five
of
them.
You
know
I.
A
Thought
seven!
Well!
Okay,
that's
actually,
quite
so!
There's
two
managers,
so
it's
phil
in
new
zealand
and
jerome
in
central
canada
see
him!
No
is
he
wes,
I
can't
remember.
Maybe
he
moved
to
vancouver
okay
he's
in.
D
A
How
about
that?
Sorry,
I'm
not
remembering
the
city
correctly,
so
two
managers
and
now,
but
they
have
very
small
teams,
so
they
have.
They
have
actually
they're.
Well,
there's
a
analytics
team
which
currently
has
three
people
we're
working
to
hire,
there's
one
transferring
to
the
team
from
a
different
team
and
then
hiring
four,
because
there's
gonna
be
one
largest
team
and
then,
on
the
other
side
on
phil
side,
it's
actually
four
teams
of
two
people
each
so
it's
it
is
a
number.
A
A
How
many
the
percentage
of
users
that
convert
from
free
to
paid
is
one
group.
Another
group
is
how
focusing
on
improving,
for
example,
how
many
stages
each
user
adopts.
So
because
the
more
stages,
a
user
adopts
the
more
likely
that
they're
happy
with
gitlab
and
getting
value
out
of
it
so
they're
using
just
source
control
management.
Are
they
also
using
source
control,
management
and
ci
for
doing
you
know
for
doing
pipelines,
for
example,
and
there's
other
teams
as
well?
But
but
so
yeah.
C
Yeah,
I
just
I
guess
I
was
thinking
from
a
manager
point
of
view.
That's
a
lot
of
different
use
cases
and
a
lot
to
manage
and
keep
track
of,
and
now
you
have
to
keep
track
of
all
of
it.
So,
let's.
A
Go
yes
and
jerome
and
phil
are
awesome
too,
so.
C
B
I
brought
up
this
topic
during
the
engineering
manager
office
hours
with
christopher,
just
because
I
wanted
to
get
his
take
on
it,
and
he
had
some
really
great
observations
around
why
this
is
not
a
matrix
organization
and
that
if
we
do
start
to
see
wayne
becoming
less
involved-
and
you
know
not-
you
know
someone
who's
overseeing
the
general
day-to-day
from
a
director
level
within
threat
management
that
we're
supposed
to
tell
on
him.
C
A
And
please
do,
and
that
is
why
I've
gotten
out
of
a
number
of
things.
So
I
can
spend
like
I'm
doing
less
public
speaking
and
fewer
blog
kind
of
things
and
stuff
like
that,
and
to
make
time
to
be
able
to
focus
on
this,
which
is
good,
which
is
what
my
intent
was.
C
Right
until
you,
until
you
get
up
to
speed
and
everything,
then
you
can
it'll
be
easier
and
you
can
go
back
to
the
things
you
like.
C
Down
dope
so.
C
A
And
actually
I
gotta
type
in
a
container
security,
and
so
so
thiago's
out
today,
so
I'll
give
the
update
is
she'll
rock
and
name
a
candidate.
So
we
can
make
this
public
this
recording
public,
but
we
had
a
good
good
pipeline
of
candidates
and
we
actually
got
two
accepts,
so
one
candidate
is
starting,
I
believe
in
two
weeks
ish
in
december.
A
Somebody
from
I
forget
where
in
canada,
but
in
canada
and
and
the
other
person
is
in
march
and
is
in
india,
which
is
cool
and
reason
for
march,
is
their
contract
with
the
current
employer
requires
them
to
give
a
good
bit
of
time
before
they
start,
which
is
okay.
Of
course,
one
of
one
of
the
candidates
is
a
referral
not
from
anybody
on
the
call
now,
but
a
referral
from
a
current
gitlab
team
member.
A
It's
kind
of
neat
that
they've
worked
with
in
the
past
and
the
other
is
a
top
community
contributor
who
wanted
to
work
at
lab
and
is
coming
on
board
actually
as
a
team
member
as
an
employee,
which
is
kind
of
neat
and
reason
why
I
forget
who's
going
to
container
security
and
who's
going
to
thread
insights
and
then
alan's
eventually
going
to
move
from
threat
insights
to
container
security.
A
But
I
forget
who's
going
to
which
team.
I
think
the
person
in
canada
is
going
to
container
security
because
they
have
more
experience
with
kubernetes
and
security
specifically
and
the
other
person
who's.
A
community
contributor
has
contributed
many
parts
of
gitlab
and
is
just
has
a
good
bit
of
back
back-end
back-end
engineering
experience
is
going
to
go
to
threat
insights.
When
that
person
comes
on
board,
then
allen's
probably
gonna,
move
to
container,
but
I
think
thiago
is
still
figuring
all
that
out.
D
A
I
think
we're
saying
it's
gonna
be
january
or
february,
or
you
know,
we've
got
a
lot
to
do
and
we
have
a
shorter
time
frame.
Customer
commitments
on
thread
insights
than
we
do
on
container
security,
so
we're
gonna
keep
going
a
bit
longer
on
because
the
new
folks
take
a
little
longer
to
get
up
to
speed,
of
course,
than
folks
already
here
to
be
to
be
fully
contributing.
A
So
we're
probably
going
to
overdo
thread
insights
a
little
bit
prefer
thread
insights
more
than
container
security,
a
little
bit
as
we
onboard
the
new
folks
and
then
switch
things
over.
A
So
annual
engagement
surveys
that
should
be
in
your
inbox,
I
think
it
actually
went
out
a
week
or
so
ago.
So
please
fill
it
out.
It's
not
a
required
thing,
of
course,
but
please
fill
it
out.
We
don't
track.
A
Who
said
what
we
you
know
so,
if
you're
worried,
if
you're,
if
that's
a
concern,
so
it
does
say
which
team
feedback
is
from,
but
it
only
says
that
if
there's,
I
think
more
than
don't
quote
me
on
this,
but
it's
like
more
than
four
or
more
than
five
people
in
a
team
give
feedback.
Does
the
manager
that
team
get
specific
feedback
so
otherwise
it
doesn't
give
the
feedback
at
all,
so
that
anonymity
is
preserved
so
yeah,
and
only
thanks
thanks
lindsey.
It
only
takes
about
15
minutes.
A
I'll
tell
you,
I
use
these
surveys
quite
a
bit.
I
get
a
lot
out
of
them
in
terms
of
like
okay,
here's
what
people
said
not
just
for
my
team
but
for
engineering
overall
gitlab
overall
okay.
A
What
should
we
do
and
did
we
improve
what
we
said
we
were
going
to
improve
on
from
the
survey
six
months
ago
or
a
year
ago,
and
if
we
haven't,
I
feel
quite
sad,
but
you
know
it
happens
of
course,
but
I
I
really
pay
attention
to
these,
and
I
personally
I
want
to
hear
what's
going
well,
I
want
to
hear:
what's
not
going
on
lindsay.
You've
got
the
next
one.
B
If
you
haven't
already,
please
install
the
endpoint
security
on
your
client
if
you
have
a
mac,
so
I
know
thank
you
alexander
good
job.
I
did
it
as
well,
so
I
didn't
check
jonathan
or
zamie.
I
was
just
looking
for
my
team,
so
please
be
sure
to
do
that,
and
then
I'm
just
going
to
keep
this
last
item
in
the
agenda.
Until
I
maybe
see
a
change
in
trends
and
behavior,
I
don't
think
this
meeting
should
just
be
wayne
or
thiago
or
myself,
adding
agenda
items.
B
If
you
have
things
that
you
want
to
share
here,
you
know
ideas
that
you
think
would
benefit
the
whole
team.
Please
add
them
to
this
agenda.
This
is
the
one
synchronous
discussion
that
we
have
across
the
whole
team.
It's
not
specific
to
one
of
the
two
groups,
so
things
that
are
about.
You
know
how
we
work
together
as
a
team
or
even
just
something
interesting.
You
learn.
So
that's
it
for
me.
A
So
before
we
break
alexander
zamir
jonathan
anything
like
to
bring
up
to
the
group
or
any
other
thing
you
can
say
earlier.
C
A
A
So
thanks
a
little
better.
Is
it
or
jonathan
anything
to
add
four
brick.
D
No
it's
good.
I
just
would
like
to
ask
alexander
that
for
next
time
we
also
need
to
understand
how
defend
and
secure
fit
into
the
picture
under
defend.
B
B
C
A
A
Is
that
showing
correctly
so
protect
stage
has
container
security
group,
which
is
in
the
threat
management
department?
The
threat
management
department
also
has
the
threat.
Insights
group,
which
happens
to
be
part
of
the
secure
state
and
secure
stage,
has
a
bunch
of
groups
that
are
part
of
the
secure
department.