GitLab 12.9 Release Kickoff, 13 Feb 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.9 Kickoff - Manage:Compliance

Description

- Export audit events data to CSV: https://gitlab.com/gitlab-org/gitlab/issues/1449
- Extend PAT expiration setting to GitLab.com: https://gitlab.com/gitlab-org/gitlab/issues/118893
- Introduce an optional expiration date for SSH keys: https://gitlab.com/gitlab-org/gitlab/issues/36243
- Project deletion should be logged in Group Audit Events: https://gitlab.com/gitlab-org/gitlab/issues/39139
- Add audit event for impersonated events: https://gitlab.com/gitlab-org/gitlab/issues/536

- Add project import audit event: https://gitlab.com/gitlab-org/gitlab/issues/35855

- Filter Audit Events: https://gitlab.com/gitlab-org/gitlab/issues/32388

A

Hi, my name is Matt Gonzalez and I'm, a product manager here at get lab for the compliance group today, I'm going to walk you through the features we'd like to ship in 12:9 the focus for my group. This release will be on exporting out of events, credential management and adding additional audit events. First up we're looking to add an export option, for instance, level. Audit events. This feature will generate a CSV file for you to parse through and process in all of the ways that make sense for your organization.

A

We hope this will empower you to better analyze your instance activity and make informed decisions, we're also extending the personal access token expiration, setting from the self managed instance level to get lab comm for group managed accounts, as a group, owner of a group managed account you'll, be able to define an expiration value for all of the personal access tokens created by members of your group to enforce credential rotation for your users and align your gitlab group with your company policies.

A

We're also extending the personal access token expiration, setting to get lab comm for group managed accounts, as a group, owner of a group managed account you'll, be able to define an expiration value for all personal access tokens created by members of your group to enforce credential rotation for your users and align your gitlab group with your company policies.

A

Similarly, we'll be introducing an optional SSH key expiration setting for users. This is the first iteration towards providing group owners of group managed accounts, similar credential management control for SSH keys. This setting is optional and is set by users themselves, not by group owners or administrators for audit events, our goals, add project deletion and import events to the group level table we're also adding administrator impersonation events of the innocence level, audit events table and we're looking to introduce better filtering options for all of these audit event tables at the project group and instance level.

A

To make using these tables a much better experience for you.

A

I'm excited to be making progress on these fundamental controls and visibility, features that will better enable you to manage the compliance state of your gate, lab groups and projects. As always, we encourage you to visit the issue, links and the description below and provide your feedback. Please also consider joining the compliance special interest group to help me shape our roadmap. Thanks for listening.