Skip to main content

How It Works

Enable Secrets Detection in full scans or pull request scans to look for credentials committed in code. Open Issues → Secrets to review the affected file, credential type, and verification evidence. Use the Verified live secrets filter to focus on credentials confirmed active at detection. Full scans combine and deduplicate candidates from multiple detectors. ZeroPath can confirm a credential directly when a detector verifies it with the provider. It reviews other detections in context to distinguish likely secrets from examples, test fixtures, public keys, and other non-secret values.

Detected Secret Types

ZeroPath detects a wide range of secret types across all major cloud providers and services. Some of which are:
  • AWS access keys and secret keys
  • Google Cloud service account keys
  • Azure credentials and connection strings
  • DigitalOcean tokens
  • Heroku API keys

Scan Modes

Full Repository Scan

Full scans check files in the repository or partition in scope. Review any partial scan warning before relying on the results.

PR Scan

PR scans check changed files and evaluate detections on changed lines. Findings that meet the configured thresholds can appear as inline comments and affect the PR check.

Verification

Provider verification can confirm whether a credential was active at detection. Review that result alongside the finding’s validation:
  • Verified live — the provider confirmed the credential was active at detection.
  • Unverified — ZeroPath has no provider confirmation. Review the available evidence and check the credential in the provider.
  • False positive — validation rejected the finding, for example because it is a test value or placeholder.
If validation errors or reaches its budget, candidates without a verdict are withheld from the active findings queue. A later scan can evaluate those detections again.

Partial Scan Warning

One full-scan detector excludes large files when possible, with a default threshold of 5 MiB. Check the scan log for exclusions. If the detector times out, ZeroPath warns that secrets coverage is partial. Findings from the other detector can still appear, and previously recorded findings are kept. Review the warning and affected scope before relying on the scan.

Remediation Guidance

Each detected secret includes:
  • Redacted secret preview — a masked version showing only enough to identify the credential (such as the last four characters, or the algorithm label for key material) without exposing the full value. Secret values are masked on every surface — including the dashboard, the API, webhook payloads, notifications, exports, and integration tickets — for all callers.
  • Redacted finding title — for secret findings, the vulnerability title is automatically replaced with a deterministic, location-based title that does not contain the secret value. This applies everywhere the title appears, including webhook payloads (such as VULNERABILITY_PATCHED and PATCH_PR_DENIED events), notification messages, and API responses.
  • Redacted false-positive reasoning — when a secret finding is marked as a false positive, the reasoning text is not stored. Because the validation agent’s reasoning can quote the credential it was asked to judge, this prevents the secret value from being persisted in or served through the false-positive reasoning field.
  • Rotation guide — platform-specific instructions for rotating the compromised credential (e.g., how to regenerate an AWS access key, revoke a GitHub token, or rotate a Stripe API key).
  • Detector information — the type of secret detected and how it was identified.
  • File location — the exact file and line where the secret was found.
Even if a secret was only briefly committed, treat it as compromised. Git history preserves all committed data.
1

Rotate the Credential

Generate a new secret/key in the affected service and revoke the old one.
2

Remove from Code

Move the secret to environment variables, a secrets manager (AWS Secrets Manager, HashiCorp Vault, etc.), or your CI/CD system’s secret storage.
3

Audit Access Logs

Check the associated service for unauthorized access during the exposure window.
4

Prevent Future Leaks

Add configuration files containing secrets to .gitignore to prevent accidental commits.

Exposure Snapshot

For hardcoded credential findings, you can view a point-in-time exposure snapshot that captures the credential’s exposure state at the time of detection. The snapshot is available on the finding’s detail page for users with the appropriate permissions. Organization admins, MSP members, and organization-wide (service or MSP) API tokens can view the full snapshot details. Other users who can view the finding see only “An exposure snapshot exists. Org admins can view it.” The snapshot has two sections:
  • Readers on the VCS — who could read the repository on the version control provider at the time the secret was detected. For repositories on GitHub or GitLab, this includes the repository’s visibility setting and a roster of users with access, showing each user’s login, display name, permission level (e.g. “maintain” or “Developer”), how access was granted (direct, team, organization role, organization base permission, inherited group, or outside collaborator), and which teams or organization roles provided it. The roster may be complete, partial (when some access sources could not be read, such as organization roles or base permissions), or unavailable (when ZeroPath’s credentials could not read the repository’s access data). For repositories on other providers (Bitbucket, Azure DevOps, Gerrit, or a generic Git remote) and for uploaded repositories, ZeroPath does not record a roster, so this section always shows as unavailable.
  • Viewers in ZeroPath — which ZeroPath principals could view the finding at that time. This includes organization members, MSP members, service tokens, and MSP tokens, along with each viewer’s kind and the basis for their access (such as organization admin, team grants scoped to the repository or its tags, or disabled access control). The API response also records each viewer’s role and whether the organization’s secret masking setting was active; the app does not show these.
When Readers on the VCS has a roster, choose Export CSV to download readers matching the current search, including those on other pages.

Configuration

Secrets scanning is controlled through scanner settings with org/tag/repo-level inheritance: Secrets scanning runs as part of the broader scanning pipeline and shares the same scheduling, notification, and integration configurations as SAST findings.

Organization-Level Secret Masking

Organization admins can click Hide Descriptions under Settings → General → Secret Masking, in the Repositories & data section. When descriptions are hidden, the AI-generated description and exploit walkthrough for secret findings are redacted on every surface — including the dashboard, API responses, webhook payloads, notifications, and exported tickets — so that prose that might quote the secret value is never shown. The code snippet and finding title are always masked regardless of this setting; the organization toggle controls only the narrative fields (description and exploit walkthrough). This setting is useful for organizations that want to ensure secret values cannot be inferred from finding descriptions, even by authenticated dashboard users. Developers who need the actual value can open the file in the repository via the permalink on the finding.