ISO 27001: security as a system, not a firewall
The next five cases turn to ISO 27001, information security — the standard most likely to be mistaken for an IT project. It is not. It is a management system that happens to protect information.
The tell is who owns it. Where 27001 is run by IT alone, it becomes a pile of technical controls defending against yesterday's threats while the real exposures — a careless process, an over-privileged contractor, a supplier with your data — sit untouched, because they aren't IT's to fix.
Read properly, 27001 starts not with firewalls but with a question: what information matters, what could go wrong with it, and what will we do about each risk — accept, mitigate, transfer or avoid? The Annex A controls come after that analysis, chosen because a risk demanded them, not because a checklist listed them.
Four cases follow: a risk nobody owned, continuity tested for real, the human layer, and Annex A controls that actually fit the business instead of strangling it.