Bug 441548 - Log repository access for security compliance
Summary: Log repository access for security compliance
Status: NEW
Alias: None
Product: JGit
Classification: Technology
Component: JGit (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 enhancement (vote)
Target Milestone: 3.5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 458445
Blocks:
  Show dependency tree
 
Reported: 2014-08-11 17:16 EDT by Vincent Phan CLA
Modified: 2015-02-06 02:33 EST (History)
4 users (show)

See Also:


Attachments
Provided logging of repo files on fetch or push (8.31 KB, patch)
2014-08-11 17:16 EDT, Vincent Phan CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Phan CLA 2014-08-11 17:16:17 EDT
Created attachment 245901 [details]
Provided logging of repo files on fetch or push

We have a corporate security requirement to log user access to repositories hosted on our Git server.  Part of this requirement involves detailing the access time, user info, the Git action and repository state and files fetched or modified.  There does not seem to be any auditing or logging capabilities in JGit that would help us comply with those requirements.  Ideally the auditing should allow administrators to enable or disable the types of events or data that get logged.
Comment 1 Robin Rosenberg CLA 2014-08-14 11:34:45 EDT
Gerrit (which uses JGit) has logging. It doesn't log while files are updated, but that information is in the repo and Gerrit can ensure that users only push changes in their authenticated users own name.

Else, if you build something on top of JGit, you can add logging too on top of JGit, just as Gerrit does.
Comment 2 Vincent Phan CLA 2014-08-15 12:36:36 EDT
Thanks Robin for your comments.  We are in fact using Gerrit and have already added a com.google.gerrit.audit.AuditListener but the logging information here is insufficient to meet our requirements.  Is this the Gerrit logging you were referring to?  We are not considering developing an additional layer at this time, we were hoping that logging for security and auditing purposes would be an integral component of JGit itself.