📅 Webinar - October 27, 11AM EDT - Secrets Management: How to Scale Your Tech Teams’ Knowledge
Save my spot!7
If you’re looking to monitor public repositories listed under your GitHub Organization, and you aren’t interested in detecting secrets leaked elsewhere on the platform (such as in developers’ personal repositories), good news: you fall under our FREE - OPEN SOURCE ORGANIZATIONS plan of GitGuardian Internal Repositories Monitoring!
See pricing for Internal Repos MonitoringAvailable in Saas
Quick start for freeFor Public Monitoring: any publicly active developer who has made at least one public commit somewhere on GitHub.
For Internal Repos Monitoring: any active contributor to a project you are securing with GitGuardian who has made at least one commit in the last 90 days.
Our Internal Repos Monitoring product is free for repositories hosted under your GitHub Organization.
Our Public Monitoring product is charged based on your numbers of publicly active developers. Contributors to your Open Source projects aren’t always members of your development teams. We count these contributors only if they are actual employees. In such a case, we monitor these contributors wherever they commit on public GitHub, especially on personal and third party repositories.
Our Internal Repos Monitoring is integrated with GitHub and GitLab on premise. In order to access your on premise source code management solution, we recommend to use GitGuardian on premise version as well. However, we do offer a secrets scanning API that you can use to integrate with any system.
These two products are distinct and complementary. They come in the form of two different dashboards. GitGuardian for Public Monitoring is typically used by Threat Response, while GitGuardian for Internal Repos Monitoring is typically used by Application Security.
This greatly depends however on the way responsibilities are split between your teams. In any case, the look and feel of both GitGuardian dashboards are very similar, so that your team members aren’t lost when they use our two products!
Internal Repos Monitoring tightly integrates with repositories that are owned by your company, either public (under your GitHub Organization, if you have any) or private repositories. These repositories are part of your Software Development Life Cycle.
Public Monitoring is more of a Data Loss Prevention or Threat Intelligence solution. It monitors the whole GitHub public activity, using many different rules to pinpoint activity that is linked with your company and that might be a threat. This activity mostly occurs on repositories that you don’t control and you don’t even know exist, such as your developers’ personal repositories.
For Public Monitoring, the best option that you have is to reach out to us. We use many different rules to identify public activity that is linked with your company. It just takes one email to our support to get your company’s public activity metrics based on our historical data.
For Internal Repos Monitoring, a developer is an active contributor to a project you are securing with GitGuardian who has made at least one commit in the last 90 days.
For Public Monitoring: a user of your GitGuardian dashboard can either be an admin or a member. An admin can manage users, configure integrations and assign incidents to users.
For Internal Repos Monitoring: Your GitGuardian dashboard has a mandatory owner, which is by default the first registered user. Other users are either managers or members. Managers are just like owners: they can manage users, configure integrations and assign incidents to users. When self-hosting GitGuardian (on premise), we have an additional layer of permissions specific to the administration of your GitGuardian instance.
Quota usage is based on requests and not on content amount or size. As an example, the scan of a single file, via single scan endpoint, and the scan of a commit involving multiple files, via multiple scan endpoint, both use 1 API call per request.
The quota is set on a rolling month basis (and not on calendar month). By default, we grant 1,000 calls/month on our free plans and 10,000 calls/month for our paying customers. Those quotas can be fine tuned upon request.
For Public Monitoring: the product only scans data that is already publicly available on public GitHub. When data is published to GitHub, it is instantly mirrored in multiple locations that you can’t control. Your most important priorities are to revoke any credentials potentially hardcoded in your source code to prevent malevolent access, then to take down the repository to prevent wider spread.
For Internal Repos Monitoring: your source code is uploaded to our cloud. If your security constraints don’t allow this, we recommend to use our on premise version. Contact us to learn more.
We do! Please contact us.
.png)
Securing your systems starts with securing your software development process. GitGuardian understands this, and they have built a pragmatic solution to an acute security problem. Their credentials monitoring system is a must-have for any serious organization.
Solomon Hykes,
co-founder of Docker
