►
From YouTube: Sec Section PM / Field Sync - April 2023
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
All
right,
thank
you.
Everyone
for
joining
this
is
our
monthly
cspn
sync
for
the
SEC
section,
and
this
is
the
gonna,
be
the
public
portion
where
I'm
going
to
go
over
some
of
the
recent
updates.
That
might
be
a
particularly
interesting
for
y'all,
so
getting
started.
A
The
first
thing
I
wanted
to
talk
about
was
that
we
are
adding
the
group
level
compliance
Frameworks
report,
so,
with
this
you'll
be
able
to
add
change,
remove
Frameworks
from
any
of
your
projects
that
are
within
the
group
at
the
group
level,
so
you
don't
have
to
go
individually
to
each
project
and
add
the
compliance
framework
to
them.
We
added
the
report
to
where
you
could
see
which
projects
of
which
can
which
Frameworks
in
1510
and
in
1511
we're
adding
the
ability
to
to
change
those
Frameworks.
A
So
this
is
building
in
product
support
for
what
Luke
stallman
had
built
when
his
compliance
toolkit.
That's
a
huge
thanks
to
him
for
for
getting
that
built
up
and
providing
some
of
the
inspiration
for
this.
So
that
should
be
super
helpful.
I
know,
there's
a
lot
of
customers
that
have
been
asking
for
that.
Yeah.
A
Yes,
eventually,
so
we're
going
to
be
continuing
to
to
iterate
on
it
and
add
more
more
features
to
it,
we're
going
to
be
adding
search
and
filter
as
well
as
things
like
quick
actions
right
now,
you
can
do
bulk
a
bulk
action
of
adding
and
removing,
but
we'll
also
be
adding
quick
action.
So
you
can
do
it
just
on
a
single
project
at
a
time
if
you
want
to
but
yeah
that
that
will
be
coming.
A
So
the
second
one
I
wanted
to
point
out
was
the
new
license
compliance
scanner
that
was
enabled
by
default
in
on
SAS
in
1510.
It
is
available
for
self-vantage
but
behind
a
feature
flag
in
1510
I'm,
not
sure
if
there,
if
that
feature
flag
is
going
to
be
enabled
by
default,
Sam
or
serif.
Do
you
know?
Is
that
going
to
be
enabled
by
default
for
self-managed
any
in
the
upcoming
releases.
D
I
can
take
that
one
if
you
want
sir
either
way
yeah
so
we're
not
quite
sure
when
we're
going
to
be
able
to
have
that
enabled
by
default.
We're
trying,
obviously
to
get
that
enabled
by
default
as
soon
as
we
can,
but
there's
some
complication
around
that.
So
it's
unlikely
to
be
enabled
by
default
for
1511.
D
right
now
we're
targeting
16.0
by
as
a
goal
to
have
that
enabled
by
default.
But
it
is
supported.
So
if
customers
want
to
turn
it
on
ahead
of
time,
they're
certainly
willing
to
do
that.
One
of
the
challenges
that
we
have
is
that
when
you
turn
it
on
it
downloads
an
additional
like
26
gigabytes
of
data,
because
it
downloads
all
of
the
license
data
onto
your
drive,
which,
for
as
far
as
I,
can
think
of
that
really
shouldn't
be
a
problem
for
any
of
our
customers.
D
Because
I
can't
imagine
anybody
running
this
on
something
that
doesn't
have
enough
disk
space
to
support
that,
but
just
due
to
internal
gitlab
concerns
around
increasing
our
minimum
system
requirements
and
other
such
things
like
right
now
we're
leaving
that
as
an
opt-in
feature.
So
you
do
have
to
go,
enable
it.
If
you
want
that
to
happen
as
an
intermediate
step,
we
might
add
a
setting
in
the
admin
Center
to
turn
it
on
or
off
and
then
enable
the
feature
Flag
by
default.
D
D
Our
end
goal
is
to
have
it
on
by
default,
but
it
might
take
us
a
little
ways
to
get
there
just
given
the
fact
that
we
need
to
get
the
rest
of
gitlab
on
board,
with
increasing
the
minimum
requirements
for
running
a
gitlab
ultimate
server,
and
it
would
not
impact
the
minimum
system
requirements
if
you're
on
a
free
or
premium
license
right.
That.
A
A
And
then
the
last
one
that
I
wanted
to
point
out
and
since
we've
got
all
the
product
managers
on
here,
if
any
of
you
wanted
to
I
guess
except
for
Connor,
if
any
of
you
wanted
to
point
out
anything
else
that
you
wanted
to
make
anyone
aware
of
that's
fine
as
well,
but
the
last
one
that
I
was
going
to
point
out,
is
being
able
to
enforce
IAC
scanning
with
the
scan
execution
policies
and
adding
support
for
for
that
within
those
policies.
A
So
with
that
did
anyone
else
have
anything
to
add
to
the
public
section
here
before
we
stop
this
recording.
B
Yeah
I'll
just
call
out
something
that
we're
working
on
for
1511,
which
is
role-based
approvals
in
scan
result
policies.
So
that'll
allow
you
to
instead
of
today
having
to
choose
approvers
from
an
individual
or
group
level.
You
could
choose
a
role-based
approval,
set
developer,
maintainer
Etc,
so
that's
currently
actually
available
behind
feature
flag,
but
we're
we're
working
on
making
that
default
in
1511.