Skip to content

Log Git push actions

Problem to solve

As a GitLab administrator, I need to who and when Git data is being modified so that I can respond to security incidents effectively and pro-actively identify suspicious activity. At the moment I have no easy way of doing this.

GitLab should include Git push actions in the audit logs.

Intended users

Administrator of the GitLab instance and/or Security and Compliance officers.

Further details

It should be possible a user of GitLab to have an central auditable trail of all write actions to a Git repository for analysis and investigation.

Proposal

Mockup
Screen_Shot_2019-08-05_at_3.04.15_PM

Extending audit events already supported by GitLab, when ever a Git push occurs, via the web interface, API or directly, we should log:

Permissions and Security

Access should be consistent with existing Audit Events permissions.

Documentation

Update https://docs.gitlab.com/ee/administration/audit_events.html docs to add push events

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Customers interested in this feature:

Links / references

Edited by James Ramsay (ex-GitLab)