►
From YouTube: Defend Staff Meeting 2020-06-17
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
D
C
A
We're
not
gonna
talk
about
the
standalone
vulnerabilities
icon
right
now,
so,
let's
get
started,
we've
got
I
put
a
bunch
of
stuff
on
the
agenda,
so
Wayne,
as
you
guys,
are
aware,
I
hope
participating
in
the
CEO
shadow
program
this
week
in
next
week's,
so
hopefully
we'll
get
a
lot
of
good
learnings
from
him
when
he
comes
back.
If
anything
comes
up
and
he's
not
available
or
reach
out
to
myself
or
Tiago
good
analyst.
Thank
you
all
for
participating
in
team
day,
I
was
really
really
thrilled.
A
I
had
a
great
time
and
I
feel
like
I
know
you
all
just
a
little
bit
better
I
plan
on
I
hope
to
work
with
folks
on
this
call
and
other
people
to
put
to
get
a
little
like
asynchronous
fun
things
we
can
do
it
like
Alexander's
Mad,
Libs
that
he
did
during
the
team
day.
So
just
kind
of
keep
that
up
and
have
some
fun
and
depending
on
what
happens
with
contribute
20
21.
Maybe
we
just
start
doing
this
regularly.
I
thought
it
was
great.
So
thank
you
all.
What.
E
A
E
B
A
A
E
B
A
C
A
All
right,
I'm
gonna,
keep
moving
on.
You
know
I
created
boards
for
our
groups
and
decided
shortly
thereafter
that
I
truly
dislike
them,
and
the
reason
is
is
that
the
milestone
is
embedded
in
the
configuration
of
the
board,
which
is
nice,
because
I'm
lazy
and
we
don't
have
to
update
them.
But
it's
not
nice,
because
you
can't
look
at
other
milestones
and
there's
a
confusing
period.
A
You
know
where
there's
two
milestones
that
are
open,
so
expect
new
links
from
me
later
today,
I
just
if
anyone
had
been
using
them,
I
didn't
want
to
throw
anyone
off.
The
overhead
will
be
that
will
need
to
update
the
links
to
update
the
milestone,
I've
been
watching
others
do
and
I'm
seeing
security
that
same
thing
go
ahead.
I
got.
B
I
got
bookmarks
here
with
one
that
shows
the
current
which
which
just
picks
up
the
current
milestone.
Then
there's
a
planning
for
you
that
shows
all
the
milestones
and
then
I
have
a
manager's
view
that
shows
what
each
person
is
doing.
Do
you
know
if
any
of
these
are
gonna
change?
Cuz
I
do
find
them
useful.
It's.
B
A
Right,
but
you
know,
I
know
that
right
now,
for
example,
I
see
that
Alan's
already
like
starting
to
pick
up
some
stuff
from
13.2
he's.
You
know
you
really
got
to
work
to
find
things
that
are
outside
of
that
free
to
find
a
bucket
and
I
think
it
should
be
easier
if
anyone
disagrees
and
wants
to
keep
a
career
milestone,
board
and
I
can
instead
just
create
a
modifiable
milestone
board
I
can.
A
A
Correct,
so
that's
why
I
created
these
boards
in
the
past,
I
and
I
think
other
people
had
been
using
that
in
dev
in
QA
board,
which
allows
you
to
add
a
group
filter,
a
DevOps
filter.
But
then,
if
you
change
the
columns
that
are
on
there
or
the
underlying
configuration
of
the
board,
it
does
change
it
for
other
people.
A
So
with
these
boards,
these
our
defend
specific
boards
and
you
can
see
by
the
labels
in
the
top
left-hand
corner
where
the
drop
down
is
that
it's
you
know,
thread
insights
and
container
security,
they're
labeled
to
try
and
mark
what
they
are.
You
know
current
milestone,
but
you're
right.
If
you
change
the
configuration
or
the
columns
that
are
on
the
board,
it
will
adjust
for
everyone.
I,
don't
know
about
labels,
so
much
I,
don't
think
so.
A
A
Okay,
moving
on
360
reviews,
we
keep
getting
that
bumped
back,
so
we
got
a
little
bit
more
time,
so
procrastinators
like
me,
have
until
next
Monday.
Now
we
don't
know
Philippe
on
the
call,
but
he's
got
a
lot
of
opinions
on
here,
they're
just
great.
Why
asking
feedback
for
every
submission?
It's
painful
right!
You
know
and
some
people
got
a
lot
of
requests.
So
you
know
the
thing
my
response
to
Philippe
is.
These
are
optional.
Remember
that
they're
helpful
for
your
teammates
for
certain
people.
You
just
may
not
have
had
a
negative
experience.
A
I
B
D
A
G
C
A
B
A
A
Box
might
be
different
than
other
people,
so,
but
someone
who's
on
your
direct
team,
you
might
say
I'm
gonna,
take
twenty
minutes
for
someone
who
I
work
with
less
frequently
I'm
only
gonna
take
ten
minutes,
but
if
you
just
put
yourself
a
time
window
on
that,
I
think
it
makes
it
a
little
bit
easier
to
I'm
saying
this
is
I
have
like
half
of
mine
still
to
do.
Yeah.
F
A
A
So
the
the
goal
of
the
suggestion
that
I
have
is
to
encourage
people
to
do
that
and
add
sort
of
a
forcing
function
or
some
amount
of
countability.
That
says:
hey
I've
looked
at
this
before
this,
like
you
know
minute
that
you're
asking
me
to
and
I've
been
studying
with
Thiago,
and
you
know
other
people
about
ways
to
do
that,
and
we
were
talking
about
potentially
asking
people
to
add
like
an
emoji,
you
know
of
you.
B
It
helps
cuz,
you
can
hover
over
the
the
emoji
and
see
the
people
who
are
in
the
coal
who
have
carrot
at
it,
and
then
you
know
right.
Samia
can
talk
about
this
because
he's
seen
and
I
think
the
carrots
a
great
idea,
Lindsay
cuz
of
st.
Austell
aleene's,
it's
gonna
keep
people
wandering
sleighs
this
a
play
on
words.
Is
there
stick
emojis
the
carrot
and
stick
thing
what's
going
on
here.
H
C
B
A
Different
at
that
point
and
I'm
not
sure
I,
don't
think
we're
not
trying
to
like
micromanage
or
police
people,
and
this
sense
I
read
some
handbook
items
and
I
think
it
was
Thomas
with
him
who
really
pushed
this
idea
of
forcing
functions.
A
lot
and
I
think
it's
really
helpful
in
an
asynchronous
environment.
So
Daniel
you
had
a
question
about
the
emoji.
Does
that
answer
it?
It's
just
that
you
it's
that
you've
looked
at
it,
but
we
could
go
a
step.
Further.
A
I've
noticed
that
certain
people
who
look
at
these
issues
prior
to
planting
break
down
actually
make
sure
that
they
ask
their
questions
in
the
issue,
which
is
the
best
place
to
ask
the
question
right,
so
we
could
say
that
you've
looked
at
it
and
you've
asked
the
questions
that
come
to
mind.
That's
not
to
say
you
don't
have
more
that
come
up
for
the
synchronous
discussion,
but
you
know
we
could
define
that
to
the
degree
that
we
think
is
appropriate.
E
C
Think
I
think
it's
a
good
idea.
I
mean
I
think
it
would
be
encouraging
to
like
at
least
put
some
question
something
on
one
of
the
issues
for
everyone.
I
mean
it
might
be
hard
to
kind
of
come
up
with
one,
but
it
forces
us
to
really
take
a
deep
look.
It's
like
oh
yeah,
okay,
good,
and
you
know
at
least
I'm
working.
You
know
forth
to
put
something
on
someone
of
them.
How
do
you
feel
today.
K
E
A
Like
Alexander
just
want
some
that
it's
kind
of
a
step
in
the
right
direction,
we
could
decide
in
the
future
that
we
want
to
encourage
more
asynchronous
questions
and
issues.
But
it's
really.
Let's
take
that
first
step
towards
really
getting
people
to
look
at
them
in
advance
of
the
secure
in
its
discussion.
I.
B
I
I
can
I
think
that
when
we
started
at
the
weekly
group
it
was
like
the
idea
that
I
think
Thomas
had
the
idea,
if
I'm
not
mistaken,
was
that
there
was
a
couple
of
issues
that
were
not
straightforward,
let's
say,
for
example,
the
network
policy
at
the
time
it
was
a
huge
issue
with
lots
of
comments
and
people
having
different
opinions.
So
the
idea
was
to
have
this
meeting
so
then
the
engineering
team
could
clarify
that
and
ask
the
product
owners
about
that,
and
then
I
think
there
was
a
little
bit
of
shift.
I
There
so
became
more
like
team
three.
Instead
of
being
more
like
a
clarification
and
then
and
the
product
the
POS,
they
start
like
presenting
the
ideas
and
presenting
the
tests
that
they
wanna
that's
going
to
come
in
the
pipeline
and
things
like
that
and
on
the
same
time
we
lost.
Previously,
we
had
a
desk
assigned
to
someone
to
do
the
grooming,
for
example,
so
that
this
person
knew
that
that
task
was
more
or
less
what
they
are
like
going
to
focus
right
now
and
now
it's
kind
of
everybody
looks
at
everything.
I
B
Really
good,
really
good
point
that
that
meeting
is
is
expensive
right.
We
only
got
30
minutes
a
week
if
we
could
be
a
bit
more
selective
about
the
things
that
that
we
bubble
up.
So
maybe
not
everything
needs
to
go
be
talked
about
in
the
in
the
meeting.
So
some
of
the
simple
herb
things
can
just
move
from
playing
break
down
to
refinement
synchronously,
and
then
we
leave
the
the
you
know
expensive
sort
of
meeting
to
for
these
I
like
it
to
me
and.
E
I
do
think:
we've
had
some
successful
I.
Remember
at
least
one
call
that
we
were
on
where
I
someone
had
know
that
me,
someone
had
questions
and
then
I
think
Tiago.
You
were
maybe
running
in
you're
like
do
you
have
aim,
I
see
you
post
them,
some
questions.
Do
you
want
to
talk
about
it
and
the
person
was
like
no
I'm
fine
with
leaving
this
asynchronous?
Now,
let's
move
on
and
I
think
that's
in
the
spirit
of
a
synchronicity.
A
Add
one
more
thing
to
respond
to
zamir's
comment
and
I
put
it
in
the
message
as
well.
You
know
I
think
that
the
goal
of
that
meeting
had
always
been
around
planning
breakdown,
which
is
that
high-level
conversation
ask
questions
about.
You
know,
understanding
the
requirements
and
getting
things
into
the
right
place
where
someone
can
then
pick
it
up
and
groom.
So
I,
don't
know
if
that
answers
your
question
at
all
or
your
concern.
Are
you
seeing
that
we're
getting
too
much
into
the
weeds
of
grooming
in
those
discussions?
Was
that
your
observations
I
mean
no.
I
It's
more
like
I
noticed
that
we
have
been
like
evolving
and
bringing
the
meeting
kind
of
slightly
a
different
format
from
time
to
time.
I
think
I'm,
I
think
some
time
for
us
to
come
to
a
single
format
that
it's
going
to
address
our
main
problem.
That's
why
I
think
the
main
point
for
me
was
that
I
think
that
the
assistance
that
we
are
having
some
aspects
or
another-
it's
just
because
of
this
change.
Okay,.
A
E
Yeah
exactly
it'd
be
like
here
are
the
tickets.
Everyone
should
look
at
them
before
the
meeting
bring
their
questions
to
the
ticket
and,
if
there's
anything
they
want
to
verbalize
they
can,
but
otherwise
they
should.
You
know
you
so
who
was
overlaying.
It
should
be
like
they
might
want
to
talk
about
it,
and
these
tickets
I
mean
yes
or
no
and
then
move
from
there
is
my
suggestion.
E
A
E
A
Been
a
little
bit
inconsistent
about
putting
things
on
the
list
for
planning
breakdown,
you
know
it's
a
bug
and
it's
very
clear,
especially
if
it
was
created
by
someone
in
this
group,
especially
a
follow
up
typically
put
those
into
refinement
and
just
assign
them
to
someone
and
kind
of
skip
over
the
planning
break
break
down.
If
you'd
like
to
see
those
items,
let's
sit
on
a
planning
breakdown
list
as
well.
It's
just
to
have
the
option
to
say
now.
We're
good
I
can
start
doing
that.
I.
A
A
B
A
E
F
We're
gonna
have
to
rename
this
meeting
anyway
right.
It's
not
going
to
be
incites
anymore
either
right,
that's
getting
changed,
no!
So
threat
insights.
It's
that's
a
good
question,
so
the
team
name
is
staying
the
same
on
the
website.
It
will
live
under
the
secure
section,
but
every
person
is
the
same.
So
we're
really
doing
it
for
is
to
confuse
everyone
inside
of
gitlab
because
wait,
wait.
A
F
I
am
NOT
gonna,
do
a
good
job
of
this.
I
actually
saw
so
Kenny
Johnson,
one
of
the
directors
of
product
management
actually
just
opened
up
an
issue
to
say
hey.
This
is
super
confusing
to
everyone
inside
of
get
lab,
there's
a
difference
between
the
way
that
we
have
the
product
structured.
So
this
is
that
sort
of
marketing
externally
facing
this
is
where
we
end
up
with
its
section
stage
group
category
as
the
hierarchy
for
organizing
the
stuff
that
we
build.
That's
separate,
but
often
very
much
I
guess
aligned
with
organizational
structure.
F
So
this
is
the
I
guess
what
was
a
division
department,
sub
department
team,
or
something
like
that?
That's
why
this
is
confusing,
because
we
we
will
end
up
with
a
sub
department
that
actually
crosses
stages,
which
doesn't
seem
to
happen
very
often,
and
a
lot
of
the
ways
that
we
talk
about
things
aren't
really
structured
to
make
that
clear.
I
was.
I
F
It
has
gotten
away
believe
me:
I
am
equally
as
confused
by
this,
but
the
reason
that
I
think
it
was
done
is
the
executive
team
had
made
the
request
and
I
know
a
lot
of
our
customers.
Think
about
vulnerability
management
in
particular,
being
part
of
the
secure
stage
and
so
I
think
just
from
a
messaging
perspective.
It
does
make.
Some
sense,
obviously
did
make
sense
to
move
all
the
teams
around
and
everything.
So
that's
why
this
is
such
a
weird
thing,
because
we
had
to
move
it
between
stages.
A
A
I
F
Well,
I
think
the
good
news
for
that
is
because
we're
keeping
the
group
name
the
same
by
moving
it
from
defender
to
secure
it's
still
gonna,
say
group
thread
insights
on
everything
that
the
thread
insights
team
has
been
responsible
for.
The
only
change
is
the
DevOps
secure
label.
Gitlab
is
supposed
to
work.
The
way
it's
supposed
to
work.
The
labels
is
whatever
group
label
is
applied.
Is
the
group
that's
doing
the
work
to
allow
for
teams
to
grab
things
out
of
other
groups
and
stages
backlogs
if
they
need
to
implement
some
people
quickly?
F
A
A
This
to
the
next
one
and
I'm
also
wondering
from
Thiago,
Matt
and
Sam
I,
don't
know
if
we've
shared
our
discussions
or
the
outcomes
of
our
discussions
of
wanting
to
improve
the
way,
we're
using
epics
and
breaking
down
things
into
implementation
issues,
so
that
might
be
a
good
agenda
item
to
share
with
the
team
in
the
next
staff
meeting
as
well.
You
know
that
it's
already
kind
of
honor
13.1
retrospective,
that
it's
frustrating
that
you
know.
We
can't
move
things
independently
across
the
workflow
and
things
like
that.
So
I
did.