platform
For individuals, open-source projects, and teams of 24 developers or fewer.
platform
for {{devsCount}} Developers
Advanced collaboration, remediation
and prevention workflows for Sec, Dev,
and Ops teams.
Up to unlimited contributing developers
Customize detection and find public leaks (out of the perimeter)
Automate incident remediation steps with playbooks
platform
Software supply chain security at
scale–centralize policy governance and decentralize remediation.
Manage unlimited teams to remediate incidents at scale
Unlimited API quota for Shift Left scans (pre-commit)
Deploy and run on your own infrastructure (self-hosted)
platform
Discover your developers’ footprint on public GitHub and map your attack surface.
Sources
Source code, Infrastructure-as-Code, Docker images
Git repositories
(full historical scan)
Other data sources
(e.g., Slack, Jira, and Confluence)
Historical scan
SDLC stages
Developer workstations (git hooks)
CI environments
Multi-VCS support
(GitHub, Azure Repos, GitLab, Bitbucket)
Pull requests (GitHub only)
Detection
Specific detectors (420+)
Generic detectors (12+)
Custom detectors
(based on regex)
Secrets validity and presence checks (frequency)
Remediation
Automated severity scoring
(context-based)
Developer-in-the-loop
(feedback and resolution)
Playbooks
(automated workflows)
Remediation guidelines
for developers
Prevention
GitGuardian CLI ggshield
(in pre-commit hooks)
Honeytokens
Deployment
Automated detection in source code
Perimeter coverage tracking
Inventory management
(with key/value labels)
Deployment jobs
Monitoring
Leakage detection
on public sources (GitHub)
IP labeling
IP allowlisting
Incident response
Enriched events stream (e.g., user agent, action, IP address, tags, etc.)
SCA support
Supported languages
Multi-VCS support
(GitHub & GitLab)
Implementation
Implementation
CI support
(GitHub Actions, GitLab, Jenkins & Azure)
Direct & Transitive dependencies
Remediation
Remediation guidance
Vulnerability context
Automated severity scoring
SBOM
SBOM generation
SBOM file support
Deployment
SaaS
Self-hosted
(KOTS or Helm chart)
Authn/Authz
SSO login with
SAML 2.0 support
Teams
Custom roles
(coming soon)
Alerting & ticketing
Native integrations for Slack, Discord, PagerDuty, and Splunk alerts
Jira integration
Event-driven webhooks
Analytics & reporting
Analytics dashboard
Export (.csv format)
API & developer tools
REST API for workspace and
incident management
GitGuardian CLI for
developers (ggshield)
Quota
Other
Support
Onboarding program
Customer support
Support availability
Premium support
Available for teams of 200+ developers.
Coverage of GitHub
Detection
Real-time alerting
Threat hunting
Deployment
Authn/Authz
API
Support
Go all-the-way with GitGuardian and secure your perimeter inside out.
Boost your supply chain security at an affordable price. Reduce your attack surface and detect early intrusions.
Go all in with GitGuardian. Protect your software supply chain from exposed secrets, IaC security misconfigurations, and detect intruders.
Security app on the
GitHub marketplace
only available for gitguardian platform
build and rollout the most comprehensive secrets detection and remediation program.
Get support from a dedicated team of SREs for on-premise deployments
Design a phased rollout program with the help of our Solutions Engineering team
Train security and dev teams on vulnerability management and remediation
Schedule a 30-minute demo and get a complimentary report with your organization’s live incidents on GitHub.
GitGuardian platform 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.
Only GitGuardian Platform licenses can be acquired via AWS Marketplace. Please visit https://aws.amazon.com/marketplace to learn more.
If you are a large organization looking to acquire several hundred licenses, you can also request a private offer from the GitGuardian team. Please contact sales@gitguardian.com.
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 GitGuardian platform 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 both products!
For Public Monitoring: any publicly active developer who has made at least one public commit somewhere on GitHub.
For GitGuardian platform: any 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, 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 GitGuardian platform, 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.
Our GitGuardian platform 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.
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 10,000 calls/month on our free plans and 1M calls/month for our customers on the business plan. Those quotas can be fine tuned upon request.
We do! Please contact us.