What is secrets validation?

Checking whether a detected secret is actually live, usually by calling the provider, instead of just reporting that it looks like a key.

By Cláudia FernandesUpdated

A repository can hold hundreds of strings shaped like credentials, such as expired keys, test fixtures, rotated tokens and documentation examples. Validation queries the issuing provider to sort the genuinely active ones from the noise.

This is the difference between a list of 400 possible secrets and a list of 6 that need rotating this afternoon. It is a comparatively rare capability, and worth checking which providers a tool can actually verify against.

What to look for

  • Which providers can be verified, since coverage is usually partial
  • Whether validation happens automatically or on demand
  • How the tool avoids leaking the secret further while checking it
  • Whether inactive findings are suppressed or just deprioritized

Best 6 code quality, security and code review tools with secrets validation

Every tool in the directory whose documentation covers this, 3 fully and 3 partially. Full support is shown first. Shown in a random order that changes on every visit, so no tool gets an advantage from its position.

Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

FAQ

What is secrets validation?

Checking whether a detected secret is actually live, usually by calling the provider, instead of just reporting that it looks like a key.

How many tools in the directory offer secrets validation?

6 of the 20 tools in this directory offer secrets validation, 3 fully and 3 partially:

Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.

What should you check when comparing tools with secrets validation?

Four things:

  • Which providers can be verified, since coverage is usually partial
  • Whether validation happens automatically or on demand
  • How the tool avoids leaking the secret further while checking it
  • Whether inactive findings are suppressed or just deprioritized