Core concepts
GitGuardian's Public Monitoring continuously scans public sources like GitHub to detect exposed secrets related to your organization and developers. This proactive monitoring helps you identify and remediate security risks before they can be exploited by malicious actors.
Public Monitoring is an enterprise feature that requires a specific license. Contact us for availability and pricing information.
Public Monitoring complements Internal Monitoring by extending your security coverage to developer activity outside your direct control.
How Public Monitoring works
Public Monitoring operates through the following approach:
1. Define your company's public perimeter
GitGuardian maps your attack surface on public GitHub by defining exactly where to monitor for leaked secrets. Your company public perimeter includes:
- Monitored GitHub developers attached to your company
- Company-owned GitHub organizations
- Secret graspers - company-specific keywords that help identify relevant secrets
2. Continuous secret scanning
Using our Secret Detection Engine, GitGuardian scans all activity within your defined perimeter to detect any occurrence of secrets and immediately alerts you.
3. Incident management and remediation
When secrets are detected, GitGuardian creates public secret incidents that provide detailed context for investigation and remediation.
Getting started
- Review your perimeter: Navigate to Perimeter > Public sources to review your monitored perimeter
- Configure detection settings: Customize which secret types to monitor and set up custom hosts for validity checking
- Explore incidents: Visit Public Monitoring > Public secret incidents to see detected issues
Key benefits
- Proactive risk detection: Identify exposed secrets before they can be exploited
- Comprehensive coverage: Monitor both current and former employees' public activity
- Contextual intelligence: Understand the scope and severity of each incident
- Streamlined remediation: Get actionable insights to quickly resolve security issues
