• Configuration
Security Misconfiguration
Security misconfiguration is the broad class of wrong defaults and forgotten hardenings — verbose errors, open admin panels, missing headers, debug modes, and cloud buckets left public.
How attackers abuse it
Recon quickly finds default credentials on admin consoles, directory listings, exposed .git or backup files, and stack traces that leak paths and versions.
Missing security headers and loose CORS widen XSS and clickjacking impact. Public object storage and overly permissive IAM turn “config drift” into data breaches.
Attackers automate fingerprinting: they do not need a novel 0-day when staging is exposed with debug enabled.
What proof looks like
Proof is a concrete, reproducible exposure: a URL returning directory contents, a debug endpoint without auth, a public bucket object, or a header/policy state that enables a specific attack path — tied to impact, not a laundry list of every missing header.
In PandaONE, this class maps to the Configuration finding category. Alerts ship only with evidence — never as unverified scanner noise.
How to prevent it
- Maintain hardened baseline images and infrastructure-as-code with peer review.
- Disable debug/admin interfaces in production; require SSO for operational consoles.
- Automate checks for public storage, open security groups, and default credentials.
- Set intentional security headers (CSP, HSTS, frame protections) and verify with tooling.
- Separate staging from production networks; never reuse production secrets in lower envs.
Hunt this class with proof
Or scan your domain.