►
From YouTube: Weekly meeting for the Defend:Threat Insights group
Description
Weekly meeting for the Defend:Threat Insights group
A
B
B
So
I
was
curious
if
anyone
was
aware
of
if
we
were
yet
pulling
in
this
new
I,
say
ID
field
that
is
actually
labeled
ID
as
a
replacement
for
the
CBE
field
and
the
common
report
format
just
trying
to
see
if
that's
something
that
we
already
did
because
I
know,
DAST
is
having
a
lot
of
discussions
about
whether
or
not
they
can
move
forward
with
that
change.
If
it's
gonna
break
anything
in
the
new
stand-alone
vulnerability,
dashboard
views.
A
A
A
D
B
A
B
Absolutely
I
think
I
was
more
curious
than
anything
to
help
answer
that
for
the
task
team,
but
just
in
general.
This
is
kind
of
an
ongoing
challenge,
we'll
have
where
the
scanner
teams
have
need
to
put
more
or
different
information
and
the
JSON
report
formats
and
we'll
have
to
coordinate
updating
the
dashboards
to
consume.
A
B
A
Okay,
so
the
second
topic,
this
case
has
come
up
a
number
of
times:
I
think
it
was
12,
8
or
12.
9
Jonathan
created
this
demo,
his
web
project.
For
us
it's
worked
and
then
it's
stopped
working
and
now
it's
not
working
and
Sam
ker
had
a
similar
production
project
that
has
pipelines
and
vulnerabilities
resulting
from
them,
but
we're
not
able
to
load
the
dashboards
from
any
of
them.
A
A
Diagnosis
was
that
the
webgoat
project
had
no
scan
result,
so
it
was
really
confusing
when
I
round,
when
I
ran
the
export
report,
download
and
saw
a
bunch
of
results
there
and
also
I
can
see
that
the
jobs
running.
So
if
somebody
Emil
I
know
that
at
one
point
we
had
a
mr
around
the
feature,
flags
that
were
being
used
in
the
grass
queue
on
the
dashboard
and
I
wasn't
sure.
If
that
got
closed
out,
because
we
are
confident
that
we
are
going
to
be
launching
with
1210
or
if
there's
something
else
going
on
there.
A
E
Was
getting
it,
the
grass
grow
stuff
working
with
a
project,
scoped
feature
flag
was
a
lot
of
work
and
when,
at
the
time
I
closed,
the
Americas
I
thought
that
within
a
few
days
we
would
be
defaulting
the
details
like
true
and
it
would
become
irrelevant
anyway,
so
like
if
it
worked,
that's
gonna
end
up
happening,
so
we're
still
stuck
with
this
issue.
The
quickest
solution
is
to
just
remove
the
feature
flags
from
the
graph
QL
entirely
and
count
on
the
feature
flag.
E
You
used
on
the
front
end
to
turn
it
on
or
off
for
projects,
and
that
should
work
just
fine.
The
only
caveat
is
it
means
that
the
fields
will
be
open
to
the
public
to
consume
from
our
SQL
API
I.
Don't
think,
that's
a
big
risk,
I,
don't
think
anyone's
gonna
really
build
a
whole
lot
of
architecture
over
those
fields
and
I
also
don't
think
they're
gonna
change
very
much,
at
least
for
now.
So
I
think
it's
fine
to
remove
it
and
I'm
happy
that
either
one
can
you
do
that
I
mean.
C
I
had
actually
when
I
had
defaulted.
Everything
to
true
I
had
ganked
that
stuff
out,
like
a
V
L
said
so,
and
so,
if
we
even
if
we
had
to
set
everything
back
to
false,
we
still
would
have
had
the
feature.
Floods
like
stuff
yanked
out
of
the
graph
key.
Well
so
III
I
agree.
You
know
pulling
it
out
of
the
graph
QL
I,
don't
think
it's
gonna
be
a
TV
deal
that
would
get
us
to
where
we
need
to
be,
or
we
can
actually
see
everything.
A
A
A
Right
I
feel
like
she
should
contribute.
I
should
assign
an
action
item
to
her
or
something
so
next
week,
Matt
was
planning
on
definitely
having
this
meeting,
because
we're
gonna
have
a
couple
of
items
that
we're
gonna
want
to
discuss
for
planning,
break
down.
Looking
forward
to
13
13.1,
correct
Matt.
B
Yes,
I
think
the
main
ones
are
going
to
be
if
anyone
hasn't
heard
about
it.
Yet,
there's
a
company-wide
push
to
identify
so-called
North
Star
metrics
for
all
the
stages
which
is
basically
coming
down
to
what
are
the
things
that
we
want
to
track
that
we
think
are
most
important
to
show
adoption
and
usage
for
each
stage.
So
I
am
going
to
be
working
on
those
for
next
week.