►
From YouTube: UX Showcase: DAST On-Demand Scans
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
Cool
I'm
in
committee,
I'm,
the
secure
stage
and
the
money
focus
on
that's
the
many
dynamic
security
applications.
Can
the
padding
test
today,
I'm
just
going
to
introduce
on
the
new
on
demands,
can
have
so
first.
What
is
on-demand
scan
I
hope.
I
can
explain
this
like
a
really
in
a
quick
way
and
if
I,
if
you
didn't
understand
that
you
can
always
count
on
me,
we
can
have
a
cop
each
other
or
something.
A
So
if
you
remember
that,
currently
women
have
security
scans,
it's
always
like
part
of
the
DevOps
circles
is
triggered
by
M
R.
So,
for
example,
the
user
have
a
code
changes
and
they
pushes
the
corrida,
mr
and
their
automatic
test
trigger
and
scan
triggered,
and
then
this.
Finally,
everything
goes
to
production
and
those
scans
are
really
part
of
this
development
cycle
is
once
regularly
and
it
runs
in
comparable
a
short
time
to
make
sure
the
the
new
code.
Everything
is
secure
and
compared
to
this
continuously
scanning
on
demand
scan
is
something
outside
of
this
code.
A
Sometimes
that's
like
the
codes
user
had
on
the
code
base
is
complicated.
The
website
is
beret.
The
amount
of
skin
is
very
deep,
with
different
URLs
and
stuff
and
user
want
to
know
more
about
their
set
specific
security
status
and
to
do
that
to
have
like
a
scan
that
might
really
be
configured
into
detail,
to
their
knees
and
to
fund
the
security
are
issues
things
they
won't
offend.
A
And
who
are
their
target
user?
Who
are
our
target?
Users
is
more
like
a
security
specialist,
those
people
who
have
deep
knowledge
about
what
they
want
to
scan
and
how
to
configure
it.
So
it
did
problem
validation,
research
around
that's
not
really
on
the
own
demons
can.
But
it's
really
only
when
scanned
those
type
of
things
came
out.
Very
often,
that's
user
told
us
they
need
to
run
the
scans
with
really
specific
goals,
what
type
of
fun
vulnerability
they're
looking
for
and
they
change
the
settings
and
deciding
need
to
be
reused.
A
A
So
the
design
flow
for
this
is
like
burying
I
would
say.
It's
quite
complicated
new
feature
that
I
start
with
the
product
manager,
mapping
up
a
medium
that
all
the
feature
they
needed
and
wanted,
and
as
elaborate,
you
iterative
small
steps
that
we
need
to
create.
A
MVC
and
the
easiest
way
or
the
quick
way
is
like
we
don't
want
something,
that's
built
about
that
in
a
year,
so
we
cannot
talk
with
engineers
so
for
maybe
one
or
two
milestone.
A
What
are
durable
and
it
go
down
to
a
features
like
create,
run
view
report,
the
very
basic
steps
and
it's
only
limited
to
passive
scan
no
profile
at
the
beginning
and
from
the
US
perspective,
I
always
ask
my
question
like:
when
is
narrowed
down
to
MVC?
If
the
job
still
valid,
are
we
still
having
people
to
run
a
security
scans
also
have
their
cycles
and
can
be
like
no
time
limits
and
change
their
settings,
and
that's
it's
still
online
with
the
future
direction
we're
going.
A
A
A
So
this
is
the
MVC's
design
that
user
click
on
only
my
skin
and
they
see
anti
studies
that
create
a
new
gas
can
and
the
thing
that
can
computers
by
really
limited
and
they
can
put
a
URL
and
we
tell
them
that
it's
passive
scan.
They
cannot
change
anything
and
after
they
creates
a
skin,
and
we
use
the
similar
label
with
pipeline.
And
if
you
to
go
to
pipeline
I,
tell
them
clearly
that
there
is
no
commute
attached
to
it,
and
this
is
a
pesky.
A
And
after
this
how
we
move
forward.
We
already
have
the
NVC
and
they
have
the
vision
there
and
we
want
to
have
a
next
focus
and
the
babies
to
focus
on
setting,
because
if
we
don't
enable
user
to
have
like
a
comprehensive
settings,
how
they
can
have
like
a
more
detailed
without
to
see
that
the
website
is
secure
or
not.
So
we
start
with
settings
and
for
the
settings
remember
from
the
research.
We
understand
that
user
need
to
have
that
setting
easy-to-use,
and
that
can
be
reusable.
A
So
there
are
two
real
durability
feature
that
we
need
to
focus
on
is
user?
Can
change
the
setting
and
also,
naturally,
for
me
from
the
user
flow
when
they
create
a
new
scan,
they
can
create
a
new
profile
and
they
can
change
the
settings
in
the
profile
and
before
in
this
feature
to
the
engineers
and
make
us
some
constraints,
it's
the
same
thing
same
cycle.
That's
like
we'll
may
want
to
do
it
in
one
or
two
milestone.
A
What
we
can
do
and
the
feedback
is
we
use
our
phone,
the
profile
or
updated
the
profile
during
the
skin
creation
is
kind
of
complicated.
So,
with
those
constraints,
ask
myself
the
same
question,
so
it
is
still
balanced
job
and
whatever
happen
either
there
and
then
I
come
with
like
on
the
additional
UX
problem.
That's
we
need
to
solve
able
to
explain
detailing
the
later.
So
this
is
the
original
design.
That
I
was
thinking
of
wait
the
profile
just
to
click.
A
Each
thing
the
profile
profile
is
a
group
of
setting
that
the
user
can
save
and
reuse
and
scan
profile
is
about
skin
type
and
side
profile.
Is
where
user
scan
their
application.
It
could
be.
A
website
could
be
an
API
anything
that
you
want
to
scan
it
and
when
we
want
to
enable
this,
the
natural
is
the
most
natural
flow
is
when
so
create
a
new
scan.
They
can
either
create
a
new
profile
or
use
an
existing
one,
but
it
cut
the
technical
constraining.
We
need
to
separate
in
two
steps.
A
We
need
to
make
sure
that's
their
own
website
without
scanning
something
running
website
just
for
them,
and
there
are
some
other
things
came
out
with.
The
validation
is
the
validation
like
take
a
long
time,
so
what
they
can
help
the
user
now
to
lose
the
status?
We
have
a
promotion
button.
We
have
a
safe
profile
button
at
the
bottom,
but
now
we
want
to
promote
in
a
little
more
to
help.
You
know
to
save
the
status
in
case.
A
The
station
takes
a
really
long
time
and
user
follow
all
the
steps
the
set
is
validated
and
throw
in
everything
and
they
save
the
profile
and
is
created
and
to
follow
the
second
step
to
create
a
scan
profile
and
flu
scamper
found
a
similar
thing.
The
follow
step
by
step,
and
this
last
step
they
have
and
they
can
save
the
profile,
and
now
we
tell
them
to
for
its
own
demon
skin.
A
So
with
this
kind
of
found,
step
MVC
offer
MVC
and
they
can
let
user
to
create
a
new
skin.
Finally,
with
the
existing
profile,
they
already
credit,
so
they
cannot
do
lab
editing
and
they
can
create
many
profiles
to
if
they
want
to
to
edit
again
and
then
create
it.
So
this
is
not
the
ideal
flow
away
want
to
do,
but
I
think
is
probably
the
something
we
can
validate
it
to
see.
A
We
can
do
the
iterative
process,
but
we
shouldn't
loss
our
final
goal,
and
this
is
kind
of
summary,
with
the
process
we're
doing
always
like
have
a
bigger
region,
go
to
MVC,
bigger
region
and
go
to
MVC
and
I
think
this
will
be
a
continuously
flow
for,
like
a
bigger
things,
we're
doing
in
the
security.
Thank
you.