TRUFFLEHOG

COMPANY

RESOURCES

TRUFFLEHOG ENTERPRISE + GITHUB ADVANCED SECURITY

Keep push protection. Clean up what already got out.

GitHub Advanced Security stops secrets at the moment of commit, and most teams should keep it. TruffleHog Enterprise finds the secrets that are already out, confirms which still work, and proves the access is gone.

Where secrets go

New commit to GitHub

BLOCKED BY GHAS

ALREADY OUT, PAST THE GATE

Slack

LIVE

Jira ticket

NOT LIVE

CI log

LIVE

Old commit history

LIVE

Cloud bucket

REVOKED

Confluence page

NOT LIVE

TRUFFLEHOG

Finds them, verifies them, routes them, retests them.

TRUSTED BY SECURITY TEAMS AT

  • HashiCorp logo
  • Lambda logo
  • Cursor logo
  • Tickmill logo
  • HiBob logo

DIFFERENT JOBS, SAME PROBLEM

What each one does

GitHub Advanced Security

Sits where code is written and stops new secrets at the gate. Push protection in the developer flow is the right control.

TruffleHog Enterprise

Covers what already got out, across the places it spread, and proves each secret is dead.

WHAT A GATE CAN’T REACH

Three places the gate doesn’t help

01

Secrets don’t stay in GitHub.

They land in Slack, Jira, and Confluence, in CI logs, in cloud storage, on laptops, in vaults, and on the public internet. 53% of the secrets we find sit outside code entirely.

Slack

Jira

Confluence

CI logs

Cloud storage

Laptops

Vaults

Public internet

53%

of the secrets we find are outside code

02

A block at the gate doesn’t reach what’s already out.

Years of commit history, deleted and force-pushed commits, forks, and every copy pasted somewhere else are already past it.

2023 commit

Force-pushed

Fork

GATE

New commit

Everything left of the gate was already out before it existed.

02

A block at the gate doesn’t reach what’s already out.

Years of commit history, deleted and force-pushed commits, forks, and every copy pasted somewhere else are already past it.

03

Blocking isn’t revoking.

Push protection stops a new secret from landing. It doesn’t tell you whether the one from eighteen months ago still authenticates, who can turn it off, or what it opens.

BLOCKED

New secret, at push

Never lands in the repo.

STILL LIVE

Old secret, 18 months out

Still authenticates until someone revokes it.

80.9%

80.9%

FROM OUR RESEARCH

Most exposed secrets are still live six months later.

That’s why TruffleHog retests each secret after the fix and records the result, so you have proof the access is gone.

Of 22,000+ verified secrets we found in public GitLab and Bitbucket repositories, 80.9% were still live six months after our first scan.

BETTER TOGETHER

GHAS keeps secrets from entering GitHub. TruffleHog Enterprise finds the ones already out, confirms which still work, routes each to whoever can revoke it, and proves the access is gone. Keep both.

Not another console to watch.

Findings flow into the tools your team already uses, like ticketing, chat, and your response automation.

See what’s already out

We’ll show you what TruffleHog Enterprise finds beyond GitHub, and which of those secrets still work.

GitHub and GitHub Advanced Security are trademarks of GitHub, Inc. This page reflects publicly available information as of November 2026.

infra