►
From YouTube: Threat Insights Weekly Group Discussion
Description
Weekly meeting for the Secure:Threat Insights group.
A
Welcome
to
the
threat,
insights,
weekly
group
call.
We
have
a
very
short
agenda
this
week
and
I
added
both
items
to
it
so
I'll
get
started.
The
first
is
a
planning
breakdown,
follow-up
from
the
discussion
that
we
had
last
week
on
the
jira
integration
sebastian.
I
think
you
were
here
for
this
conversation
when
we
talked
about
this
last
week.
I
believe
and
there's
been
activity,
so
we
reached
out
to
the
ecosystem
team,
so
the
the
summary
is.
A
That
shows
if
an
issue
is
closed,
we
talked
about
this
last
week
there
was
discussion
around
whether
this
was
something
that
we
would
try
and
store
on
our
side,
or
we
had
to
try
and
make
real-time
calls
out
to
jira
to
get
this
information,
and
we
decided
to
reach
out
to
the
ecosystem
team
to
find
out
how
they
were
handling
this.
A
B
Yeah
yeah,
I
think
that's
you.
What
you
said
is
like
pretty
much
describes
the
whole
thing
it's
like.
If
we
want
like
we
need
to
call
to
jira
for
that
status
check
and
to
show
that
is
it
closed
or
not.
If
you
want
that,
like
in
the
hover.
A
The
status
for
the
whole
list
would
be
the
performance
impact
so
based
on
the
design.
We
don't
show
that
status
until
we
hover
over
the
issue
indicators,
so
there's
also
the
option
of
retrieving
the
status
at
the
time
of
hover.
So
that
was
something
discussed
in
the
issue
as
well.
Tiago,
I
cut
you
off.
C
A
B
Yes,
but
we
don't
have
any
way
to
know
if
anything
changes
in
jira,
so
so
we
need
to
check
somehow,
and
I
think
it
will
be
a
big
performance
things
if
we
check
like
at
the
time
and
check
again
and
try
to
fetch
all
the
jira
issues
status
at
the
time
of
loading,
because
we
already
have
some
issues
on
that
page
so
and
then
the
other
things
we
I
think
jonathan
proposes
like
on.
B
A
So
that
would
turn
it
entirely
into
a
front-end
task
as
well.
I
think
we
had
a
similar
discussion
around
when
a
jury
issue
gets
deleted,
and
I
don't
know
if
these
two
items
overlap
enough
to
consider
that
at
the
same
time
sebastian
I
know
you
also
looked
into
what
we
do
to
remove
an
issue
link
when
a
jira
issue
is
deleted.
Is
that
something
that
we
are
trying
to
solve
in
the
same
way.
B
A
B
Yeah,
I
think
we
need
to
make
a
call
there
as
well
or
I'm
not
sure
the
implementation
plan,
but
I
saw
that-
and
I
think
we
need
to
the
implementation
plan
is
like
according
to
we
need
to
change
and
delete
all
the
associations
that
already
we
have
okay.
C
Is
this
a
good
candidate
for
a
spike
to
find
out
if
this
would
be
too
slow,
not
work?
Well
enough.
A
E
I
would
say
probably
not
the
direction
that
this
is
headed
sounds
like
it's
going
to
be
fairly
involved.
It
would
be
a
nice
to
have,
but
I
think
again
you
know
we
don't
own
the
main
integration.
A
E
I
mean
at
this
point
I
would
say:
let's
just
put
it
to
the
side.
Okay,
I
think
it's
something
we
can
definitely
revisit.
We
still
only
have
to
my
knowledge,
I
think
the
one
customer
that
we've
been
helping
trying
to
get
up
and
running
with
this
I'd
like
to
see
it
have
a
little
bit
of
adoption
to
get
some
feedback
to
understand
how
pressing
it
is.
I
guess
before
we
spend
a
lot
of
extra
effort
on
something
that
maybe
no
one
cares
about.
E
A
All
right:
well,
I
will
stop
bringing
this
issue
to
the
agenda,
then,
because
I
think
this
might
be
its
third
appearance
today,
which
leaves
us
with
the
14.0
kickoff
for
threat
insights.
This
should
have
happened
last
week,
but
I
neglected
to
remember
to
put
it
on
the
agenda.
So
here
we
are
daniel.
I
put
you
on
the
spot
last
time
to
do
this
for
the
front
end.
Would
you
prefer
that
I
do
it
today
or
do
you
want
to
do
it
for
the
front
end.
A
No
there's
so
many
other
tabs,
but
I
know
that
when
things
get
moved
from
like
refinement
to
ready
for
development,
they
sometimes
end
up,
not
where
I
expect
them
to
be,
which
not
surprisingly
did
happen.
So
let
me
just
move
this
one
bug
down
before
I
start
talking
about
all
of
these
things.
Sorry
guys.
A
Okay,
there
we
go
and
I'll
share
my
screen
and
we'll
make
this
quick.
So
I'm
going
to
start
with
the
front-end
issues
for
threat
insights
in
the
14-0
milestone,
I'm
going
to
ignore
the
items
that
are
in
review
and
in
development
right
now,
but
a
lot
of
these
should
fall
into
the
categories
that
I'm
about
to
describe
our
top
priority.
Is
the
generic
report
schema,
so
that
is
the
top
three
items
that
you
see
in
the
ready
for
development
column?
These
are,
I
believe,
now
we've
got
some
item
and
daniel.
A
If
you
could
take
a
look
at
completing,
I
know
that
you've
been
working
on
the
refinement
just
to
call
out.
There
is
some
refinement
also
going
on
still,
but
this
is
our
top
priority
to
try
and
wrap
up
the
generic
schema.
Hey
matt.
Can
I
pause
for
one
question
from
a
priority
perspective,
while
we're
doing
this,
I
was
chatting
with
dave
piezek
about
this
yesterday
and
so
far,
we've
re
prioritized
this
at
the
epic
level.
A
We
say
we
want
to
get
all
the
generic
security
report,
schema
ui
elements
done
and
then
we'll
be
done
with
that
top
priority.
Some
of
these
elements
aren't
even
really
slated
to
be
used
by
any
scanner
teams.
You
know
dave
has
been
working
with
cameron
and
other
folks
on
the
scanner
teams
to
make
sure
that
those
items
that
they
needed
that
were
blocking
das
were
handled
first,
but
some
of
these
other
items
are
much
lower
priority.
If
you
want
to
adjust
the
priority
for
some
of
these.
Based
on
that,
we
can
do
that.
A
E
A
little
bit
torn
on
that
one,
because,
while
the
scanner
teams,
I
would
think
their
work
is
definitely
at
the
top
of
that
list.
I
don't
want
to
say:
let's
not
do
things
like
actually,
because
maybe
I
should
ask
first,
do
we
know
which
of
them
the
scanner
teams
are
not
for
for
sure,
going
to
use
right
now.
D
A
C
If
I
may,
the
enforce
json
schema
validation
for
generic
security
report
that
one
it
has
a
blocker
on
a
back-end
issue,
and
I
don't
know
if,
if
that's
still
true,
I
think
I
think
we've
deviated
from
that
initial
plan
and
it
might
not
be,
it
might
be
no
longer
blocked
if
it
is
blocked.
C
A
A
Thank
you
thiago.
So
the
next
group
of
issues
are
the
conversion
of
the
pipeline
security
tab
to
use
graphql
and
share
ui
components.
So
there's.
A
E
Well,
I
think,
depending
on
what's
left
outstanding,
it's
certainly
worth
a
revisit.
I
don't
want
to
not
do
some
of
the
pieces
for
a
really
long
time,
because
part
of
the
purpose
of
it
is
to
also
be
able
to
offer
third
party
vendors,
some
of
the
more
rich
formatting
options,
because
they
feel
like-
or
some
of
them
have
additional
things,
and
you
know
in
their
uis
or
their
outputs
that
they
can't
really
cleanly
show
today
when
they
integrate.
E
E
A
E
C
Which
which
doesn't
stop
any
other
team
from
delivering
what
they
need?
We
can
tell
you,
this
validation
doesn't
exist
and
it's
optional,
but
it's
it's
something
that
we've
been
looking
forward
to
putting
in.
A
We've
got
some
refactors
some
debt,
that
the
team
is
working
on
getting
rid
of
the
term
first
class
in
our
code
base,
which
has
been
around
for
far
too
long,
and
this
one
might
be
out
of
order
did
alert
when
trying
to
create
an
issue.
This
one
keeps
getting
bumped
out,
so
it's
a
lower
priority
feature
that
was
requested
around
improving
the
look
of
the
message
that's
displayed
when
you
try
and
create
an
issue,
but
you
can't
it's
a
very
kind
of
edgy
edge
use
case.
A
So
we
can
discuss
the
priority
of
the
ready
for
development
items.
We've
got
a
few
items
that
are
blocked
mostly
by
ourselves,
so
this
is
blocked
by
some
of
the
refactoring
that
we're
doing
thiago.
I
just
have
to
remind
you
about
this.
We
we're
blocking.
We
have
this
issue
open
and
it's
blocked
on
the
back
end
bugs
it's.
A
Actually
the
fix,
but
it
was
reported
as
a
front
zone
issue
through
hacker
one,
so
we've
kind
of
created
the
situation
now,
where
we're
just
standing
by
to
close
this
out
once
the
back-end
is
done,
and
I
think
we
are
far
past
our
sla
on
it
so
and
the
other
blocked
items
this
one,
I
believe,
is
because
we
are
wait.
We
I've
marked
this
as
block,
because
we
believe
this
will
be
fixed
as
part
of
the
pipeline
conversion
to
graphql,
because
it's
going
to
be
using
the
same
endpoint.
A
And
this
is
also
this
is
blocked
on
our
own
work
right
here.
So
I
do
at
this
point.
Do
you
guys
want
me
to
go
through
the
refinement
issues?
You
know,
we've
got
a
we've
got
a
feature
flag,
blocked
on
our
own
work,
daniel's
working
or
sorry
a
feature
flag
for
rolling
out
the
pipeline.
Daniel's
refining.
Some
remaining
generic
security
report
schema
issues
daniel.
Do
you
have
any
updates
on
this
spike?
I
think
that
refinements
for
spike
are
kind
of
spikes
are
kind
of
weird.
I
know
you've
been
very
busy
in
filter
land.
A
A
A
A
A
I
think
this
just
got
created,
so
savage
has
been
taking
some
of
the
larger
issues
that
were
under
this
epic
and
breaking
them
down
into
smaller
iterative
pieces.
So
this
one
got
kind
of
left
there.
It
looks
like
all
right
now.
I
know
no
one
likes
doing
that,
walk
through
so
who's
next.
C
We're
at
time,
but
I'm
I'm
gonna,
I'm
gonna.
C
C
Look,
it's,
it
says
from
7
to
7
25.
C
No,
no,
I
can
do
it.
It's
not
super
exciting
in
terms
of
features,
but
it's
a
huge
bug,
hunting
effort
and
season
for
us.
So
I'm
going
to
start
with
ready
for
development.
C
The
first
one
is
not
a
bug,
but
it's
something
that
the
rapid
action
for
on
database.
All
teams,
I
think,
have
already
done
that.
We
were
meant
to
do
the
last
milestone.
We
couldn't
get
to
it.
So
it's
still
there
it's
at
the
top.
It's
the
very
next
one,
not
gonna,
explain
every
bug
that's
in
here,
but,
as
you
can
see,
there's
a
there's
a
lot
of
them.
C
This
particular
guy
here
is
something
that
is
stopping
us
from
doing
the
the
dismissal
reasons.
So
it's
the
it's
a
it's
a
big
epic,
so
this
is
just
starting
to
chip
away
at
this
epic.
It's
the
first
thing
to
go
in
there.
This
one,
which
is
not
a
bug,
is
continuing
a
refactor
effort
on
deprecating
this
field
from
the
database
project,
fingerprint
just
as
a
reminder.
C
This
isn't
the
same
epic,
so
same
story,
another
bug
and
a
performance
issue
at
the
bottom.
We
already
have
heaps
of
stuff
in
flight
from
the
last
that
we
already
started
heaps
of
stuff
in
review.
This
probably
came
from
1312.
C
C
Anyway,
people
can
look
at
this
for
themselves,
but
we
we
got
a
number
of
things
blocked
in
there
and
a
number
of
things
in
refinement.
I
don't
feel
amazing
about
getting
actually
getting
to
all
of
these,
but
we
should
at
least
get
to
this
first
one,
because
it's
a
p1
s2
bug
as
soon
as
refined,
it's
going
to
make
its
way
to
the
top
of
ready
for
development.
C
A
C
A
C
Maybe
maybe
we
yeah,
I
don't
want
to
discuss
it
too
much,
because
then
we
can't
open
this
thing,
but
maybe
I'll
take
it
to
slack
okay
but
yeah.
Let's
follow
up
on
slack,
I
guess
it
is
in
140,
though
lindsay,
but
the
competition
is
fierce.
I
don't
know
that
it's
gonna
that
we're
gonna
get
to
it.
If,
unless
we
do
what
you're
saying
so,
it's
a
good
call,
thank
you
and
that's
it
bugs
bugs
everywhere
and
I'm
really
looking
forward
to
getting
rid
of
a
bunch
of
them.