All Tools View Categories About Contact Privacy

Secret Exposure Scanner

Scan a pasted Pod or workload for Secrets exposed via environment variables vs mounted as volumes.

Runs entirely in your browser - nothing is uploaded and no cluster connection is made.
0
env exposures
0
volume mounts
Your secret exposure scan will appear here.

About Secret Exposure Scanner

Secrets injected as environment variables are easy to leak, while Secrets mounted as volumes are the recommended pattern. The Secret Exposure Scanner parses a pasted Pod or workload and reports every Secret reference, classifying env-based usage as high exposure and volume mounts as recommended.

It detects env.valueFrom.secretKeyRef, envFrom.secretRef and volume mounts of Secret-type volumes. The pod template is extracted automatically from Deployments/StatefulSets/DaemonSets.

Parsing uses a small tolerant YAML reader (no external dependency). Nothing is uploaded. Everything runs locally.

Features

  • Env detection - secretKeyRef and envFrom.secretRef flagged as exposure.
  • Volume detection - Secret volumes mounted (recommended).
  • Severity - high for env, low for volume mounts.
  • Workload aware - extracts pod spec from common workloads.
  • Copy / Download / Print - take the report anywhere.

How to Use

  1. Paste a Pod or workload YAML.
  2. Run the scan and review findings.
  3. Copy or download the report.

Examples

Example 1 - env exposure. DB_PASSWORD via secretKeyRef -> high.

Example 2 - volume mount. tls Secret mounted -> recommended.

Benefits

  • Visibility - see every Secret reference.
  • Guidance - env flagged, volumes praised.
  • Private - all in the browser.
  • Fast - instant client-side scan.
  • Copy, download or print - take it anywhere.

Frequently Asked Questions

Why is a Secret in an env var a problem?
Environment variables are easy to leak: they show up in crash dumps, logs, `kubectl describe`, child processes and some debug endpoints. Mounting a Secret as a volume keeps it out of the environment.
What does this scanner find?
It parses the manifest and reports every Secret used via env/valueFrom.secretKeyRef or envFrom.secretRef (flagged as exposure) and every Secret mounted as a volume (the recommended approach).
What input does it accept?
A Pod, or a workload with a pod template (Deployment, StatefulSet, DaemonSet, Job/CronJob).
Does it read my secrets?
No. It only reads the references (names/keys) in the YAML you paste; nothing is sent anywhere.
Does this connect to a cluster?
No. Everything runs in your browser and nothing is uploaded.
Can I copy the report?
Yes. Copy, download or print the scan results.