To make secret scanning easier to understand, we’re updating the names we use for our detector types to better reflect how each one finds secrets. This is a naming change…
To make secret scanning easier to understand, we’re updating the names we use for our detector types to better reflect how each one finds secrets. This is a naming change only; detection behavior is exactly the same.
Before
Now
Non-provider patterns
Generic patterns
Since our last pattern update, we’ve expanded secret scanning’s detection coverage with new partners, more patterns blocked by…
This week, we’re rolling out several improvements to secret scanning and public monitoring: Resend is now a GitHub secret…
Secret scanning now includes extended metadata for Replicate secrets, providing richer context for leaked credentials. Extended…
Secret scanning now runs validity checks on Asana, IBM, and MessageBird secrets so you can tell whether a leaked credential is…
To help you understand ownership and impact of a leaked secret, GitHub secret scanning surfaces enriched metadata for supported…
Alerts are more trustworthy and actionable when noise is reduced. See how we improved the verification step with context-aware…
