►
From YouTube: Compliance final planning 16.5 - 2023-09-14
A
B
Awesome
yeah
thanks
Nate
and,
of
course,
I'll
just
say
hello
to
the
compliance
team.
I
look
forward
to
working
more
closely
with
you
guys
I've
been
working
with
Nate
on
the
priorities
here
and
we
are
going
to
be
focusing
on
first
our
compliance
adherence
report,
so
this
will
help
with
defining
separation
of
duties
for
software
development,
we'll
be
kind
of
calling
out
some
kind
of
key
standards
and
aspects
like
multiple
multiple
approvals
for
merge
request.
B
So
this
isn't
going
to
be
accounting
for
any
specific
compliance
framework
per
se,
but
these
are
kind
of
common
requirements
that
you'll
see
globally
across
many
different
compliance,
Frameworks
and
and
also
really
advantages
from
a
security
standpoint
to
highlight
so
that
that's
going
to
be
a
really
awesome
step
and
Improvement
towards
identifying
more
individual
or
specific
compliance
framework
standards
and
kind
of
building
out
that
more
robust
reporting.
So
this
will
be
an
MVC
and
a
starting
point
for
that
effort.
B
The
next
one
is
one
that
I
know
the
team's
been
working
on
a
little
bit
here
already.
This
is
the
saml
s,
so
support
for
merge,
request
approvals
so
today
and
for
some
time
we've
had
support
to
require
passwords
for
merge,
request,
approvers,
and
we
have
customers
who
are
are
already
kind
of
storing
information
in
their
saml
groups
to
be
able
to
authenticate
and
they'd,
rather
not
store
passwords
in
get
lab.
B
I
know
that
we
do
have
a
little
bit
of
a
technical
debt
item
here
around
power,
storing
data
for
audit
events
in
our
current
databases
and-
and
we
want
to
you-
know,
optimize
and
be
able
to
address
a
potential
performance
concerns
further
out
in
the
future.
So
this
this
effort
to
move
to
clickhouse
cloud
is
going
to
really
set
us
up
for
success,
and,
and
hopefully
we
can-
we
can
also
really
consolidate
and
narrow
down
how
how
restoring
events
into
like
a
more
you
know
single
or
more
optimized
database
structure.
B
So
that's
going
to
be
a
huge
Improvement.
Let's
see
retrying
failed
external
status
checks
a
lot
of
our
customers
if
they
have
especially
external
tooling,
that
they're
using
they
can
create
a
middleware
API
and
be
able
to
kind
of
block
merge
requests
based
on
some
input
from
an
external
system.
So
a
common
one
might
be
servicenow
where
they're
handling,
maybe
some
compliance
checks.
B
So
they
can
leverage
SAS
checks
to
you
know
to
enforce
compliance
or
to
enforce
some
certain
approvals,
but
when
they
get
stuck
when
they're
in
an
intermittent
errors
or
issues,
it
can
be
a
bit
of
a
pain
or
burden
if
they
get
hung
up.
So
this
will
make
it
easier
for
teams
to
retry
those
status
checks.
B
Last
couple
here:
compliance
violation,
exports.
You
know
we
have
the
ability
to
view
in
the
UI
lots
of
details
around
compliance
violations,
but
this
this
will
introduce
an
option
to
export
a
robust
set
of
data
that
you
can
really
go
deeper
into
and
drill
down,
break
down,
to
see
exactly
what
you
want
or
work
on
aggregating
it
into
external
systems.
So
that's
going
to
add
a
lot
of
flexibility
for
customers
who
are
monitoring
those
violations
and
then
the
last
one
is
integration
with
third-party
storage
systems.
So
we
have
gcp
logging.
A
Yeah
and
I'll
go
down
to
the
more
detailed
breakdown
of
how
this
plans
out.
So,
as
Grant
mentioned,
the
adherence
report
is
our
top
priority.
At
the
moment,
the
MVC
is
on
track
to
be
delivered
in
16.5.
It's
currently
behind
a
feature
flag
at
the
moment
and
there's
documentation
on
that
as
well,
which
is
good
and
then
we'll
start
work
into
some
of
the
small
improvements,
such
as
grouping
the
adherence
report
checks
and
having
the
export
to
be
able
to
drill
down
deeper
into
that
report
and
sort
it
out
outside
of
the
UI.
A
The
next
one
was
the
samurai,
so
we'll
just
continue
working
on
this
one.
This
the
back
end
apis,
have
been
started.
We
want
to
have
the
front
end
in
place
as
well,
but
it's
not
the
settings
to
enable
this
feature
just
yet
the
migration
to
clickhouse
Cloud.
This
we're
currently
doing
the
load
testing.
A
So
once
we
have
that
out
of
the
way
we'll
be
working
on
nailing
down
the
strategy
and
initiating
the
data
transfer
from
the
current
database
through
to
clickhouse
cloud,
and
then
we
can
start
doing
testing
within
the
staging
environment
there
and
just
also
create
the
model.
So
we
can
start
migrating
across
some
of
the
queries.
A
The
retry
failed
status,
checks
and
violations
exports.
So
both
of
these
are
in
the
final
stages
of
development,
so
we
want
to
complete
and
release
both
of
these
violation.
Export
might
make
it
into
16
4
actually,
but
we're
just
on
the
on
the
edge
of
our
seat.
There
default
Branch
protection.
This
is
something
that's
been
going
on
in
the
background
and
we
hope
to
release
this
as
well
or
all
the
non-breaking
work.
This
one
piece
to
remove
the
current
settings
that
will
wait
for
17.0
mix.
A
One
is
streaming
audit
events
to
AWS
AWS
S3,
so
we're
we're
going
to
continue
on
with
this
and
want
to
release
the
group
level
this
at
the
group
level
in
166.
So
we
want
to
have
the
apis
in
place
and
the
front
end
started
in
16-5
streaming.
Audit
events
to
Google
Cloud
logging-
and
we
currently
have
this
at
the
group
level,
but
we
want
to
enable
this
at
the
instance
level,
that's
in
the
final
stages
of
development
as
well.
So
we
want
to
release
that
in
16,
hopefully
going
to
release
that
in
16.5.
A
The
next
priority
was
the
compliance
Frameworks.
So
we
have
done
solution,
validation
and
design
on
the
on
improving
the
report
and
how
we
integrated
with
things
like
adherence
report
and
security
policies,
so
we're
going
to
start
work
on
the
MVC
for
this
and
16.5
the
next
one
was
streaming
audit
events
by
subproject
or
projects.
This
is
a
feature
that's
been
asked
after
a
little
bit
and
so
we're
halfway
through
building
it
out.
At
the
moment
we
want
to
have
most
of
the
apis
created
in
16.
A
The
next
one
is
the
we're
currently,
the
headers
for
HTTP
streaming
destinations,
there's
an
active
the
ability
to
activate
or
deactivate
them
so
that
you
can
test
and
turn
on
your
headers
as
we
want
to
complete
and
release
that
in
16.5
and
the
final
two
is
just
they're,
increasing
our
ordered
events
that
we
have
within
the
system
and
also
our
test
coverage,
and
that's
just
a
continuation
that
we
continue
every
Milestone,
so
we'll
just
keep
working
on
more
issues.
There.