►
From YouTube: Threat Insights Weekly Group Discussion
Description
Weekly meeting for the Secure:Threat Insights group
A
Welcome
to
the
weekly
threatened
sites
group
discussion,
I
have
the
first
item
on
the
agenda
and
I
just
said
this
to
everybody.
That's
on
this
call,
but
now
it'll
be
here
on
the
recording
for
posterity.
We've
scheduled
a
knowledge
sharing
session
on
Thursday
to
try
and
get
some
questions
answered
across
the
secure
group.
Please
populate
your
questions
in
the
agenda
in
advance
so
that
we
can
make
sure
we
have
the
right
audience
and
try
and
get
things
answered
asynchronously
as
much
as
possible.
It
will
be
recorded
for
people
who
cannot
attend.
B
C
C
D
A
F
Yeah
there's
some
discussion
and
that
issue
Lindsay
run
on
the
group
and
the
instance
level
dashboards,
because
they've
got
the
like
the
visualization
little
widgets
down
that
right-hand
side.
It
squished
everything
together,
gotta
hold
off
in
there
for
now
until
we
can
actually
separate
out
the
the
lists
into
a
separate
page.
A
G
There's
been
a
helpful,
a
arise
got
a
chance
to
kind
of
sort
through
that
issue.
It's
it
there's
a
lot
of
conversation
in
that
one.
This
is
one
actually
that
I
finished
and
then
got
told
no,
that's
not
all
of
it
and
then
kind
of
been
trying
to
go
back
and
forth
the
figure.
Exactly
what
the
ask
is
looking
for
on
this.
G
Looking
I'm
actually
having
to
read
back
through
my
notes
on
it
about
linking
versions
into
the
finding
branch
instead
of
the
master
branch,
since
we
don't
have
any
branch
other
than
the
development,
it
says
master
branch,
but
whatever
the
default
branch
is
so
we
don't
have
anything
other
than
that
have
all
branch
in
the
dashboard.
We
won't
see
things
linked.
A
G
A
It's
okay,
you've
been
looking
at
this
for
quite
a
while
and
I
think.
Maybe
we've
gotten
to
a
place
we're
setting
up
a
half
hour
with
Dennis
I've,
let
the
reporter
of
this,
and
maybe
Iago
or
I'm,
not
sure,
but
like
getting
some
folks
to
focus
specifically
on
this
topic,
to
bring
some
more
clarity
for
you.
Would
that
help
I
think.
G
So
and
the
other
one
yeah,
the
other
part
of
this
thing-
and
it
probably
is
not
even
planning
breakdown,
but
it's
just
something
that
keeps
popping
up
is,
and
it's
actually
letter
B
on
there
as
well.
You
know
we
have
the
overall
structure
net,
you
know,
that's
that's
a
lot
of
other.
You
know
packing
engineers
have
had
the
same
issue
where
the
vulnerabilities
findings
feedback,
those
tables.
There's
some
circular
dependencies,
there's
replicated
data.
You
got
to
go
through
one
to
get
to
the
other.
G
You
know
I
think
when
we
put
in
the
Boehner
abilities
we
were,
we
said.
Eventually
we
need
to
get
everything
back
in
sync
and
back
in
line
kind
of
clarify
those
structures
and
I
think
which
we
need
to
do
that
sooner
than
later,
I've
got
the
tests
to
get
with
minute
about
a
plan
on
that
and
we've
got
a
coffee
chat
scheduled
for
tomorrow
morning,
which
spring
that
on
him.
C
Well,
if
you
go
you're
gonna
meet
with
my
man,
that'd
be
great.
You
just
put
that
down.
You
guys
are
gonna
brainstorm.
It
I'd
like
to
a
little
more
like
what
kind
of
data
integrity
is
occurring
and
we
can
save
the
second
question.
What
solutions
that
you
until
you
guys
talk
tomorrow,
you
folks
check
tomorrow,
but
what
are
the
data
integrity
issues?
What
kind
of
what's
happening
so.
G
The
one
that
I
just
had
to
create
a
migration
for
where
the
the
feedback,
not
all
the
feedback,
was
getting
into
the
vulnerability
the
dismissed
by
and
dismissed
at
fields
we're
in
the
feedback,
but
that
data
didn't
get
pulled
from
old
abilities
and
we
were
only
pulling
the
data
from
the
vulnerabilities
to
show
the
dismissed
that
it
dismissed
information.
The
other
one
I
think
was
one
that
Philippe
had
brought
up.
I'm.
Sorry
I
think
that
was
the
the
first
one
I
think
is
wonderful,
because
the.
G
G
H
The
thing
is
like
previously
I,
don't
know
the
reason
like
we
were
using
the
occurrence
feedback
to
collect
the
issues
like
trade
issues
in
the
database.
At
some
point,
we
also
we
introduced
another
model
called
a
shillings,
so
we
started
writing
the
data
into
another
table
while
implementing
a
feature
to
show
the
icon
like
issue
icon.
H
If
the
vulnerability
has
issue
in
the
security
dashboard,
I
used
this
assurance
model,
but
the
details
page
was
using
model
and
after
like
implementing
this
new
like
creating
this
new
model,
probably
at
some
point,
we
forgot
to
migrate
the
data
from
the
like
old
table
to
the
NIV
table.
So
this
is
why
we
had
this
like
discrepancy.
H
So
if
you
just
like
create
like
like
new
entities
for
the
new
table,
then
the
issue
issue
will
be
gone
but
in
the
meantime,
I'm
also
like
I,
also
Pro,
like
proposed,
like
workaround,
so
till
we
fix
the
issue.
We
can
just
like
implement
a
patch
work
around
and
then
like
migrate,
the
data
and
then
roll
back.
The
workarounds.
G
Yeah,
that
seems
to
be
the
common
theme
with
these
data
integrity
issues
where
it
existed
in
an
old
model,
but
it
didn't
get
moved
to
the
new
model
and
we're
pulling
that
information
from
the
new
model.
So
we
that's.
The
other
thing
is
we
need
I
feel
like
we
need
to
check
and
see
the
data
that
should
have
been
migrated,
and
you
know,
go
through
our
models
and
check
to
make
sure
the
data
that
should
have
been
migrated
dig
it
migrated
if
it
didn't
to
try
to
preempt
some
of
this
stuff.
A
G
E
Sorry
I
interrupted,
you
could
shoot
I,
don't
remember
what
I
was
saying
that
go
ahead.
Would
it
be
beneficial
for
us
to
have
a
meeting
like
it
sounds
like
it
didn't
get
migrated?
Maybe
because
there's
some
history
behind
here
that
we
we
don't
know
well,
it
would
be
beneficial
to
maybe
step
a
synchronous
meeting
with
some
people
who
used
to
work
on
this
code
and
I'd.
Ask.
A
G
G
Spit
balling
here,
no,
no,
that
that
occurred
to
me
for
sure
when
we
were
talking.
The
meeting
on
Thursday
is
figuring
out
historical
reasons
behind
some
of
the
stuff,
maybe
figure
out
what
their
plan
was
moving
forward.
If
there
are
steps
that
they
had
anticipated,
missed
that
didn't
get
you
know
document
or
something
that
we
did
not
anticipate,
and
you
know
no
totally
totally
on
board
with
you.
Yeah.
C
If
y'all
couldn't
put
your
some
of
your
notes
in
there,
maybe
we
can
wait
until
I
know
I'm
harping
on
this
too
much,
but
I've
been
trained
well
over
the
last
two
weeks.
Maybe
wait
till
you
guys
till
you
meet.
You
know
tomorrow
and
write
up
the
issue
and
maybe
Lu
the
issue,
but
I
think
about
a
summary
or
especially
correct.
Anything
I
got
wrong
or
an
add
anything
key
I
missed
to
the
notes.
I
tried
to
take
notes
on
what
police
had
that'd
be
great.
G
A
We've
got
one
last
item
which
is
I
think
actually,
when
we
discussed
last
week
and
it's
in
planning
breakdown,
I
know,
Alexander
has
added
some
questions,
so
let's
I'm,
just
gonna,
share
I
think
that
might
be
easier
for
this
one.
Should
we
just
look
at
it
like
we
haven't,
talked
about
it
before
because
I
don't
think
Matt
was
here
when
we
talked
last
week
and
jump
right
in
you
can
look
for
carrots
first
to
see
of
anyone
putting
carrots
on
it.
A
D
A
So
this
might
be
a
good
example
of
this
could
be
our
crazy
balloon
design
issue.
The
results
of
this
design
issue
move
into
an
epoch
and
it's
nice
and
organized,
and
it's
got
all
of
the
final
decisions
that
were
made
over
the
course
of
the
several
months
of
this
design
issues
been
discussed
and
that
epic
might
be
a
better
thing
for
us
to
look
at
next
week
in
planning
breakdown.
So
we
don't
have
to
weed
through
all
the
discussion,
and
we
know
that
Andy's
seal
of
approval
is
on
all
the
final
design
decisions.
F
Andy
I
think
you
and
I
should
probably
touch
base
too,
because
I
I
guess
the
discussion
didn't
progress,
much
past
when
I
went
out
on
PTO
and
it
sort
of
looked
like
hey
we've
taken
this
too
far,
but
I'm
not
clear
what
the
the
pairing
back
should
look
like
necessarily
it
does.
It
require
a
revision
to
the
existing
designs
because
they've
they
pretty
much
started
here
and
then
turned
into
this
big
thing.
That
was
a
very
large
tent
that
encompassed
several
different
use.
Cases
for
different
scanners,
I.
D
F
F
E
Sorry,
the
these
comments
in
the
doc
were
pulled
from
prior
week
meetings
and
so
I
had
left
issued
questions
that
you
had
answered
several
weeks
ago,
but
so
that
is
that
point
number
two
for
me
is
like
old
questions
and
then
my
question
at
the
bottom.
Regarding
the
stability
of
this
to
comment
on.
Is
this
week's
where
I
just
looked
at
the
comment?
So
it's
like
what
yeah.
F
A
D
A
D
A
This
is
a
good
I'm
glad
you
brought
this
up
India,
while
we
have
everyone
on
the
call
looking
forward
to
the
next
like
two
milestones
or
so.
It
feels
to
me
that
we've
got
a
lot
of
focus
on
the
pipeline
view
and
the
security
widget
on
the
pipeline
view
and
the
security
tab
is
that
a
correct
assessment,
I.
F
A
F
The
main
things
for
the
the
project
and
the
instance
are
sorry.
The
group
in
the
instance
level
dashboard
specifically,
are
going
to
be
to
start
separating
out
the
vulnerability
list
component
into
a
separate
standalone
page
to
kind
of
a
number
one
address.
The
real
estate
challenge
and
the
number
two
the
vulnerability
list
is
really
more
of
sort
of
an
interactive
report.
It's
not
really
a
dashboard
per
se
and
that
will
sort
of
set
the
the
forward
direction
for
having
true
dashboards
with
a
little
turks
and
grass
dashboard
things
on
them.
F
A
Partially
asked
cuz:
we've
been
having
a
lot
of
conversations
about
migrating
certain
things
to
use
graphical,
so
I
know
the
front-end
team
have
been
talking
about
it
and
whether
it
makes
sense
in
the
loaner
ability
details
page.
You
know
I've
been
kind
of
pondering
the
same
thing
around.
How
do
we
keep
the
dashboard?
Vr?
Sorry,
the
pipeline
view
in
sync
with
dashboards,
so
you
know
I
this
just
planting
seeds
for
everyone
on
the
call
here
the
benefits
and
challenges
of
updating
other
areas.