►
From YouTube: Threat Insights Weekly Group Discussion
Description
Weekly meeting for the Secure:Threat Insights group
A
Welcome
to
the
threat,
insights,
weekly
group
discussion,
we
have
a
pretty
short
agenda
today
and
we
have
a
first-time
attendee
samashrese.
Is
this
first
time
you've
made
it
to
this?
That
we've
had
this
meeting
yes
been
here,
okay,
welcome.
We
try
and
do
this
every
week
and
we
alternate
between
an
apec
friendly
and
in
a
maya,
friendly
time
zone.
A
So
we'll
jump
right
in.
We
have
a
pretty
regular
agenda,
which
you
can
see
here.
We
don't
have
any
follow-ups,
wait,
I'm
looking
at
the
fifth,
the
12th.
A
Sorry,
these
are
not
demos.
These
are
follow-ups,
so
I
have
a
question
around
documentation.
This
came
up
in
slack
from
will
and
it
was
around
the
jira
issue
creation
and
I
see
savash
on
the
line,
so
he
might
be
the
person
to
help
me
get
an
answer
to
this
question.
Given
that
we're
doing
all
this
work
for
the
issue
creation
behind
a
feature
flag,
has
there
been
any
development
on
the
documentation
so
far.
B
Sorry
lindsay,
did
you
say
subashi
or
did
you
say
savash?
I
said.
A
Sabash,
sorry,
that
is
going
you're
right.
You
said
this
in
the
last
call
that
your
name
sounds
similar.
Maybe
I
need,
I
said
you
go
by
last
names,
but
sabashi's
are
not
going
to
try
and
pronounce
your
last
name
either.
A
B
Nope,
we
should
do
that
after
the
future
flag.
I
guess.
A
But
that
was
sort
of
my
question,
and
this
is
why
I
wanted
to
bring
it
up
on.
This
call
was
to
get
more,
maybe
a
general
overall
when
we're
developing
something
behind
a
feature
flag.
I
think
there's
a
couple
of
different
ways
that
we
can
approach
the
documentation,
given
that
this
feature
flag
is
basically
going
to
be
off
for
everybody
and
we're
not
going
to
provide
instructions
to
turn
it
on
until
everything's
ready.
I
think
what
you're
saying
makes
the
most
sense
to
do
it
all.
A
B
If
I'm
not
mistaken,
when
we
switched
to
the
new
security
dashboards,
we
did
it
that
way.
We
had
we
developed
everything
and
then
we
created
we
updated
documentation
accordingly.
So,
apart
from
that,
I
don't
know
I
I
would
need
to
check
for
alternatives.
C
I
remember
that
if
I
remember
right,
we
actually
jumped
the
gun
a
little
bit
on
the
documentation.
We
had
the
documentation
out
there
before
everything
was
100
ready
and
it
we
kind
of
had
to
hope
that
no
one
complained.
A
Well,
I've
seen
in
our
documentation
that
there's
there's
ways
to
indicate
that
something's
behind
a
feature
flag.
But
again,
I
think
that's
more.
If
you're
doing
a
gradual
rollout
and
giving
people
the
option
to
configure
things
on
versus
a
development
feature
flag
to
turn
things
on
once
everything's
ready.
A
So
it
sounds
like
what
both
jonathan
and
savage
is
saying
that
this
is
what
we
did
with
stand
alone
vulnerabilities.
So
it
worked
for
us,
then,
with
exception
of
maybe
this
misstep,
where
we
got
things
out
a
little
prematurely
and
does
anyone
have
any
concerns
about
following
that
same
pattern
with
the
jira
issue,
creation.
B
I
think
we
just
need
to
make
sure
that
once
we
switch
the
feature
flag
to
default
on,
then
we
need
to
have
the
documentation
ready.
So
that's
probably
the
only
thing
that
we
need
to
make
sure
that
works.
Well,.
A
A
All
right,
thank
you.
That
was
that
question
for
me
and
then
just
an
fyi,
I'm
depreciating
and
I'm
archiving
historical
meeting
notes
all
over
the
place.
So
your
invite
should
always
still
point
to
the
most
recent.
We
don't
have
any
demos
unless,
if
anyone
has
anything
impromptu
to
share
on
the
call.
A
C
It
was
a
two-pointer,
it's
got
a
refinement
plan
out
there.
It's
it's
a
real,
simple
one
to
to
go
through
it.
I
think
it's
in
there
as
a
feature.
I
don't
know
if
it
should
be
a
bug.
I
don't
know
it's
kind
of
5050
on
that,
but
it's
got
a
it's
got
an
implementation
plan
and
should
be
ready
to
go.
D
Yeah,
it's
kind
of
on
the
fence
about
it
too.
I
mean
I'm
inclined
not
to
necessarily
call
it
a
bug,
since
we
actually
changed
the
way
that
it
behaves.
So
since
the
functionality
is
different,
I
don't
think
it's
a
clear-cut
bug.
I
think
it's
just
a
bringing
parody
back
to
a
previous
behavior
that
we
redid.
A
Cool.
Thank
you.
This
is
another
item
added
to
the
agenda
that
I'm
not
100
sure
it's
in
planning
breakdown.
It's
definitely
not
a
feature
that
we're
breaking
down
it's
a
technical
debt
issue.
I
was
hoping
that
this
would
be
a
discussion
that
thiago
is
on
because,
to
be
honest
with
you,
I
don't
have
the
context
here.
A
We
can
defer
this
until
a
pac-friendly
meeting
when
we
have
thiago
on
the
call
unless
jonathan,
if
you
have
any
insight,
because
this
is
very
back-end
heavy
and
the
api
support
realm.
C
A
I
don't
ask
you
to
do
it
right
now,
so
I
think
that'll
be
the
in
the
next
week's
planning
breakdown
list.
Yeah.
C
A
A
So
that's
all
we
have
on
our
agenda
for
today
we
do
have
an
office
hours
scheduled
after
this
from
9
30
to
10
30.
I
know
that
it's
late
for
you
savage
jonathan
and
sebastian.
This
is
optional.
It
is
always
helpful
if
someone
from
the
engineering
team
can
join
to
help
answer
questions
matt,
I
hope
you're
able
to
attend
because
I
know
felipe
is
coming.
C
C
Like
I
see
it
if
the
issue
gets
assigned
to
me,
but
I
don't
actually
like
go
out
there
and
look
that's
something
that
I
needed
to
start
doing.
C
A
A
C
I
think
it's
just.
I
think
it's
just
making
sure
that
we
go
out
there
and
like
yeah
it's
you
know,
these
are
finding
planning
breakdown.
Is
this
constant
trying
to
figure
out
how
to
make
it
better
how
to
get
us
to
get
us
in
a
better
groove,
better
process
and
making
sure
that
we
go
out
there
to
check
those
things
out
on
a
regular
basis
is
important.
I
think
I
I
usually
filter
for
like
the
current
milestone,
so
I
would
even
have
missed
this
since
it's
13
nine.
C
C
Yeah
yeah,
probably
either
either
one
I
just
forget,
like
I
look
at
these,
sometimes
I'm.
I
look
at
these
things
like
right
before
the
meeting.
I
need
to
look
at
the
you're.
A
So
you
know
if
there
it
would
be
easier
if
we
were
to
go
in
and
at
mention
in
the
issue
that
could
be,
it
would
create
a
to-do
for
you,
I'm
trying
to
get
creative
and
things
to
think
of
ways
to
improve
on
this
we're
trying
if
you've
noticed
the
list
is
the
lists
are
shorter
than
these
two
yeah,
so
that
I
think
that's
helpful
too.
C
E
B
Why
don't
we
bring
this
up
in
in
the
retro?
I
think
it's
it's
important,
it's
an
important
issue,
because
I
also
I
forget
to
look
at
this
agenda
days
before
I
usually
look
at
it
20
minutes
before
so
I
don't
even
have
the
time
to
read
all
the
truth
to
all
the
issues.
So
maybe
we
can
bring
this
up
in
in
in
the
retrospective
yeah.
I
will.
C
Say
the
slight
message
goes
out
on
monday
right.
A
C
A
C
A
B
Also
slack
messages,
I
think,
they're,
not
that
reliable,
because
by
the
time
we
we
see
the
message.
Maybe
there
are
new
messages
being
written,
so
they
they
stay
behind
since
it's
kind
of
asynchronous
tip.
A
It's
one
way
to
remind
people,
but
it
doesn't
need
to
be
our
only
one
so
yeah,
I
don't
want
to
be
a
naggy.
You
know
micromanagey
house
mom
or
anything
like
that,
but
I
want
to
make
sure
that,
given
the
amount
of
things
that
we're
asking
people
to
remember
to
do
on
a
weekly
basis
that
you
know
those
items
are
very
clear
and
present
so
cool,
we'll
stew
on
that
a
little
bit,
and
I
think
for
for
this
meeting
we're
good
right
now,
unless
anyone
has
any
other
topics
or
questions.