►
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
So,
as
we've
been
discussing
with
customers
and
also
with
internal
stakeholders,
we've
come
across
a
number
of
challenges
when
configuring
more
granular
security
policies,
so
we'll
take
a
look
at
each
of
those
challenges.
A
The
most
common
challenge
is
around
the
confusion
of
configuring
status,
options
and
I
think
the
best
way
to
demonstrate
this
is
to
look
at
how
it
works
today,
and
so
you
can
see
that
when
configuring
a
scan
result
policy,
we
have
a
list
of
our
statuses,
all
within
a
single
drop
down
and
it's
a
multi-select.
So
you
can
choose
all
states
here
as
you're
configuring,
a
policy.
However,
this
doesn't
make
sense
in
every
case.
A
For
example,
if
you
have
a
newly
detected
vulnerability,
it's
it's
not
possible
for
that
vulnerability
to
have
already
been
confirmed
as
valid
or
already
to
have
been
resolved,
and
so
this
is
causing
a
lot
of
confusion
for
new
users
of
security
policy
management
and
one
of
the
areas
that
we
can.
We
can
make
things
a
little
bit
more
straightforward.
A
The
next
one
is
around
the
age
of
a
vulnerability,
and
this
is
a
pretty
common
for
customers.
One
example
would
be
any
any
government,
U.S
federal
government
customers
that
are
expected
to
address
vulnerabilities
within
an
expected
time
frame.
So,
for
example,
you
might
have
you
know
critical
vulnerability
that
must
be
addressed
immediately.
A
If
there's
not
a
fix
available,
it's
it's
harder
to
to
move
past
that
Mr
or
handle
anything
from
an
approval
standpoint.
So
we'd
want
to
prioritize
vulnerabilities
that
have
a
fix
available
and
require
an
approval
get
those
addressed,
and
this
is
something
that
we
also
have
interest
in
internally
to
dog
food.
This
functionality.
A
So
yeah,
let's
move
on
to
the
proposal
section.
When
we
are
looking
at
our
list
of
status
options,
we
would
like
to
break
that
down
between
new
and
previously
existing.
A
So,
let's
find
an
example
here
in
the
design,
so
you'll
see
that
will
break
it
into
two
different
drop
downs,
so
it
would
be
either
new
and
or
previously
existing
and
then
based
on.
If
it
is
new,
we'd
have
the
options
for
needs
triage
or
dismissed
and
for
previously
existing
vulnerabilities.
A
In
terms
of
the
age
of
the
vulnerability,
users
will
be
able
to
to
break
down
a
policy
as
we
talked
about
into
30-day
60-day
180
day
increments,
and
we
have
an
example
in
our
designs
here.
So
we'll
have
a
drop
down,
so
you
can
choose
less
than
or
more
than
specify,
numeric
value
and
then
choose
your
increment
for
day
week,
month
or
year,.
A
A
Oh,
it's
actually
over
here
yeah.
So
so
you
would
have
an
option
for
an
operator
to
be
an
order
or
and
and
you
can
choose,
is
or
is
not
false,
positive
or
fix
available.
Okay.
So
let's
pause
almost
commonly
you'd
want
to
require
an
approval
when
it
is
not
a
false
positive
and
there
is
a
fix
available.
A
And
lastly,
I
just
wanted
to
mention
that
we
do
have
a
few
error
states
to
keep
in
mind
which
you
can
find
in
the
ux
theme
and
I've
pulled
out
the
ones
that
are
relevant
in
the
issue
here.
So
if
you
have
any
questions,
feel
free
to
reach
out
and
looking
forward
to
seeing
this
into
production.