cybersecurity A field note by Vikrant Sharma
When the blame game reaches the top
The White House removed its cyber-security chief after a string of tech failures. That is not how incident response works.
The White House fired its cyber-security chief after several high-profile tech outages. The BBC report does not specify which outages triggered the decision, but the timing suggests mounting political pressure to show accountability. This is backwards. Firing the person responsible for incident response after incidents happen is like firing your smoke alarm for detecting smoke. The job description is literally to manage failures when they occur. Cyber-security chiefs do not write the vulnerable code. They do not architect the legacy systems that fail under load. They build detection, coordinate response, and push for fixes that product teams defer because features ship faster than patches. When an outage happens, they are the ones running the war room at 3am while executives draft the apology email. The incentive structure this creates is obvious. The next person in that role will under-report, classify incidents as maintenance windows, and bury post-mortems. If your performance review depends on zero visible failures, you do not build resilient systems. You build opaque ones. I have seen this in smaller organisations. A detection system flags a credential leak. The security team escalates. Leadership asks why the credentials were accessible in the first place, then blames the team that found the problem instead of the team that left S3 buckets public. Next quarter, fewer alerts get escalated. Government IT is hard. Legacy systems, procurement rules, clearance delays, political turnover. The constraints are real. But firing the person tasked with managing those constraints does not fix the constraints. It just means the next outage will be quieter until it is too big to hide. What I would do differently: establish a no-blame incident review process before the first major failure. Document what broke, why it broke, and what budget or policy change would prevent recurrence. When leadership asks who is responsible, hand them the system design, not a resignation letter.
Source: White House removes cyber-security chief after series of tech outages