Defense-in-Depth, Least Privilege, Assume Breach

Medieval cities did not survive on one wall. They had moats, outer walls, inner walls, gates with guards, and a keep at the center — because every builder knew that any single barrier eventually fails. Defense in depth is that same wisdom applied to your digital city: a firewall at the perimeter, segmentation between districts, protection on every endpoint, MFA on every door, and monitoring over all of it. The layers are independent on purpose, so the failure of one does not unlock the rest.

Least privilege answers a different question: who holds keys, and to what? In a city where every resident carries a master key, one pickpocketed key opens everything. Least privilege issues each person only the keys their role requires — marketing cannot open the vault, the intern cannot rewire the power grid, and a service account that only reads one database cannot write to any other. The payoff appears on the worst day: when an account is inevitably phished, the attacker inherits only that account's small world, not the whole city. The discipline is ongoing, because access accumulates silently — people change roles and keep old keys — so privileges must be reviewed and revoked, not just granted.

Assume breach is the hardest mental shift and the most defining one. Traditional security imagined a hard shell keeping all attackers outside. Modern defense assumes some attacker, someday, gets in — through a zero-day, a convincing phish, or a careless insider — and asks: would we notice? how fast? what would they reach? This single assumption justifies internal monitoring, segmentation, and rehearsed incident response. It is not pessimism; it is the difference between a city that only builds walls and one that also runs a watch.