When you install a web server, a database or a cloud service, its maker wants it to work in the first five minutes. So the defaults lean towards openness: a ready-made admin login, helpful error messages, every feature switched on, listening on every network address.
That is a sensible choice for a first demo and a poor one for a live system. This lesson follows a made-up shop at shop.example and shows how those defaults get found by strangers, then how hardening (removing what you do not need and tightening what is left) takes the opportunity away.
💡Good to know
Treat every default as a suggestion made by someone who had never met your system.