• Exposure
Sensitive Data Exposure
Sensitive data exposure means secrets, PII, or credentials leave the systems that should protect them — in responses, logs, repos, client bundles, or cleartext channels.
How attackers abuse it
Attackers scrape JS bundles for API keys, mine error messages for tokens, and pull backups or .env files from misconfigured hosts. Passive recon of public Git history remains devastatingly effective.
APIs that return excess fields (internal notes, hashed passwords, government IDs) leak data to any authorized-looking client. Mobile apps embedding secrets are reverse-engineered routinely.
Once secrets leak, attackers pivot: cloud keys, payment credentials, or session cookies become the real breach.
What proof looks like
Proof shows the sensitive value (redacted in customer UI as needed) appearing in a response, artifact, or repository path under test, with clear sensitivity rationale — not a theoretical “you might log PII someday.”
In PandaONE, this class maps to the Exposure finding category. Alerts ship only with evidence — never as unverified scanner noise.
How to prevent it
- Classify data; minimize fields returned by APIs; mask in logs and support tools.
- Store secrets in a vault; rotate on exposure; never commit secrets to git.
- Use TLS everywhere; disable cleartext fallbacks.
- Scan repos and CI logs for accidental secret commits.
- Apply retention limits and access controls on backups and analytics pipelines.
Hunt this class with proof
Or scan your domain.