Features

Secrets in images Secrets, including the ones you deleted

scancontainer finds credentials anywhere in a container image, including layers where the file was later deleted, and shows them masked.

What it finds

  • Cloud keys for AWS, GCP and Azure
  • Tokens for CI/CD, GitHub, GitLab and package registries
  • Messaging and payment keys such as Slack and Stripe
  • Database credentials and private keys in all their formats
  • Secrets in environment variables and in the build history
  • Secrets in deleted layers, which are still in the image

What you get

  • The masked secret, its type and where it is
  • Whether it is still present in a deleted layer
  • Its context: production, test or example

What makes it different

A secret is validated without the network: by its structure, its built-in checksum, its expiry and public lists of compromised keys. It is never tried against the provider, so it does not travel anywhere.

Which plan includes it

Skipper and above. Compare plans.

FAQ

Questions about this feature

Why is a deleted secret still a problem?

Each layer of an image is kept. Deleting a file in a later layer hides it but does not remove it from the earlier one.

Do you test the secret against the provider?

No. Validation is offline, so the secret is never sent to a third party.

More features

Scan yours before the next deploy.