Threat profile
Misconfiguration and exposed services
A correct product set up unsafely: a public storage bucket, a database open to the internet, a default password, a debug page left on.
How it works
Most large data exposures involve no clever attack; the data was simply reachable. Cloud services are easy to open and easy to forget, and automated scanners find exposed services within hours of them appearing.
What to look for
- Services listening on the internet that nobody can explain.
- Default administrator accounts that still work.
- Storage or database settings marked public.
What reduces the risk
- Keep an inventory of what is exposed to the internet and review it regularly.
- Deny by default: open a port or share only with a stated reason and owner.
- Change every default credential during setup and disable debug features in production.
- Check HTTP security headers and cloud settings automatically on every release.
Related tool
Sources
Related threats
This section is for defence and learning. Do not test systems you do not own or have written permission to test: unlawful access to an information system is an offence (Turkish Penal Code, Article 243).