GitGuardian says its leaked-secret findings now sync to Wiz daily

What happened

According to GitGuardian’s own blog post, the company has added an integration with Wiz. GitGuardian says it now sends open secret incidents from GitHub, GitLab, Bitbucket and Azure DevOps to Wiz once a day as native secret findings (GitGuardian: Your Leaked Secrets Now Show Up in Wiz). This is a product announcement, not a vulnerability or breach report, and the post is the only source. Wiz’s own documentation or statement is not in the sources, so Wiz’s side is not confirmed.

GitGuardian says each finding carries:

• the repository, file path and commit
• the detector that caught the secret
• whether the secret is still valid, and when that was last checked
• the incident severity, mapped to a Wiz severity
• a link back to the incident in GitGuardian

GitGuardian also says the secret value never leaves GitGuardian, and that Wiz receives only a SHA-256 hash plus metadata. If a secret appears several times in one repository, GitGuardian says Wiz gets the most recent occurrence.

On sync behaviour, GitGuardian says Wiz keeps a finding open while it appears in the latest upload. Resolved or ignored incidents drop out of the next sync. The post says new findings can take up to 24 hours to appear in Wiz and resolved ones can stay visible for up to 7 days.

To motivate the integration, GitGuardian cites the Verizon 2026 Data Breach Investigations Report, saying compromised credentials appeared in 39% of full breach chains. GitGuardian also says that more than 64% of the credentials it found valid in 2022 still worked in January 2026. These are GitGuardian’s statements, and the underlying reports are not among the sources provided.

Am I affected?

Only if you run both GitGuardian and Wiz, or are considering connecting them. According to GitGuardian, the integration covers only version control sources: GitHub, GitLab, Bitbucket and Azure DevOps. Findings from Slack, Jira, Confluence and developer machines stay in GitGuardian.

GitGuardian lists these limits:

• Custom detectors and Gerrit are not supported.
• Findings without a file path are skipped.
• Findings from detectors Wiz does not yet support are held back until Wiz adds them, which GitGuardian says usually takes a few days.

Pricing, availability by plan and any independent verification of these claims are not confirmed.

What to do now

1. Check whether your team uses both GitGuardian and Wiz. If not, no action is needed.
2. Confirm that a Wiz user who can add integrations is available. GitGuardian says the integration creates the service account for you.
3. Following GitGuardian’s instructions, open the GitGuardian integration page in Wiz to get the Client ID, Client secret, Authentication URL and API endpoint URL. GitGuardian warns that a token created manually in Wiz settings will not have the permissions the sync needs.
4. In GitGuardian, go to Settings > Integrations > Wiz, click Configure, paste the four values, and choose how to map the Info and Unknown severities, which Wiz does not have. GitGuardian says you can change this later and it takes effect at the next sync.
5. Expect first findings in Wiz within 24 hours, per GitGuardian, and review the vendor’s integration documentation for full details.

Sources

• GitGuardian: Your Leaked Secrets Now Show Up in Wiz