GitHub
GitHub is monitored across several content surfaces. Public commits are the primary surface and are covered in real time; public gists are also monitored, through a historical scan.
Commits
What we scan: public commits on GitHub.
Scan model:
- Real-time: every public commit is scanned as it happens. The average time from a public commit to creating a GitGuardian incident and triggering an alert is about 10 minutes.
- Historical: a historical scan runs when your Public Monitoring dashboard is initialized, to catch secrets exposed before monitoring began.
Attachment reasons: a commit is attached to your company through your perimeter when it matches one of:
- a monitored developer - the commit author belongs to your perimeter,
- a monitored GitHub organization,
- a secret grasper found in the commit content.
Secret graspers only apply to real-time monitoring, not to historical scans. They are monitored from the moment they are created, with no retroactive scanning of past activity.
Gists
What we scan: public gists on GitHub.
Scan model: historical only. GitGuardian has run a historical scan of public gists. Gists are not yet monitored as new ones are published.
Attachment reasons: gists are currently attached to your company through monitored developers only - the gist author belongs to your perimeter of monitored GitHub developers. Organization attachment does not apply to gists, since gists belong to individual accounts rather than organizations. Secret-grasper attachment is not supported on gists yet.
