Default passwords, open admin panels, verbose errors, and public cloud storage are misconfigurations—not exotic exploits.
Checklist
- Disable debug mode in production
- Remove default accounts and sample apps
- Block public access on storage (S3 Block Public Access)
- Harden headers (HSTS, CSP, X-Frame-Options)
- Automate config scanning in CI
Important interview questions and answers
- Q: Verbose errors?
A: Stack traces leak paths and versions—generic messages to users. - Q: HSTS?
A: Forces HTTPS in supporting browsers.
Self-check
- Name three misconfiguration examples.
- Why disable debug in production?
Tip: Run automated scanner on staging weekly—catch debug=true early.
Interview prep
- Debug in prod?
Leaks internals—disable and generic errors.