►
From YouTube: Removing CVE and using ID for Secure data structure
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
Hello
I
wanted
to
share
one
of
the
discussion
points
about
getting
rid
of
CVE
and
moving
it
to
an
ID.
Currently,
when
we
run
a
scan,
you
can
see.
We've
got
a
number
of
vulnerabilities
here
which
are
all
the
same
vulnerabilities,
so
we've
got
a
total
of
seven
vulnerabilities,
but
this
vulnerability
was
found.
This
one
vulnerability
was
found
in
seven
different
spots,
which
is
why
it
shows
up
seven
different
times,
but
when
the
current
dashboard
dismisses
it,
it
dismisses
it
based
on
the
CVE
not
based
on
the
individual
instance.
A
A
It
shows
up
seven
different
times
with
a
different
path.
Now
the
proposal
is
to
get
rid
of
this
field
here
like
that
and
then
to
move
this
to
a
unique
ID.
So
it
would
be
ID
something
like
one.
The
next
instance
would
be,
let's
see,
go
the
next
one,
and
this
would
be
something
like
ID,
two,
so
on
and
so
forth.
A
Now
these
ideas
would
be
globally
unique
or
uu
IDs,
and
there
would
be
no
CBE
ID
anymore
if
we
did
that
the
behavior
would
change
so
because,
right
now,
if
you
look
at
this,
we're
gonna
dismiss
this,
and
this
dismiss
is
based
on
CBE,
and
so
this
is
actually
going
to
get
rid
of
all
seven
of
these
responses.
So
take
a
look,
they're
all
gone.