►
Description
A run-through of what the user experience might look like for a user when aggregated vulnerabilities is the default on DAST.
A
Hi,
I'm
cam,
I'm
a
das
engineer
and
I'm
going
to
be
taking
you
through
the
the
current
user
experience
for
when
we
turn
on
aggregated
vulnerabilities
in
desk.
Now
I've
got
this
site
that
I'm
testing
it's
just
a
really
simple
site.
You
can
see.
It's
just
got
four
pages.
Basically
do
nothing
and
I
have
this
project
which
basically
just
defines
a
single
job,
a
desk
job.
A
I
go
into
the
definition
so
that
you
can
have
a
quick
look
and
see
you
can
see
it's
just
testing
that
really
simple
site.
I've
got
here.
A
A
A
A
A
A
A
I
don't
understand.
What's
going
on
there,
it's
picked
what
seems
to
be
the
first
url
page,
one
which
wasn't
one
that
we
dismissed.
A
Well,
that's
probably
incorrect.
Oh
heart,
dismissed
there
we
go
yeah,
okay,
so
it's
found
the
vulnerability.
That's
grouped
you
can
see,
so
it
hasn't
found
four
four
vulnerabilities
for
each
page.
It's
found
one
which
covers
all
the
pages.
However,
we
do
click
on
it
and
it
does
only
show
page
one
which
is
potentially
incorrect.
A
A
A
So
this
has
got
the
issue,
so
this
is
the
original
one
we
gave
the
issue
to
so
this
is
also
no
longer
detected,
although
I
don't
understand
why
that
says
detected,
which
means
it
must
have
actually
tracked
it
along
with
page
four
but
oh
yeah.
So
this
is
the
grouped
one
which
is
automatically
recognized
it
is
dismissed.
I
don't
know
how
that
happened,
and
here
you
can
see
the
new
the
urls.
A
Interesting
I'll
show
this
anyway,
love
to
hear
what
people
think.