5 ms·
> Since individuals rarely have a complete overview of the entire system. I think the key phrase you are missing which is repeated many places in the timeline
by gklitz 2y ago
> Since individuals rarely have a complete overview of the entire system.
I think the key phrase you are missing which is repeated many places in the timeline is “Engineering was not consulted”.
His failure wasn’t that he doesn’t know the entire system, it was that he kept engineering in the dark, “investigated” on his own, and made conclusions to disregard the persistent researcher who kept banging at the door saying “there is an issue” despite him disregarding it again and again, notably without consulting engineering.
You don’t need to know the entire system as CISO, but you certainly do need to know that you don’t know the entire system as CISO. This wasn’t an institutional failure, it was a personal failure at a very high level.
I’m not arguing that the guy had to resign, merely pointing out that the narrative used to argue against his resignation is flawed.
- throwaway7ahgb 2y agoAgreed here, and how can you thoroughly investigate without engineering involved? Unless you suspect your own team somehow it doesn't make sense.
- braiamp 2y agoWhen I said "overview" I mostly meant both vision (as in observability) and understanding of everything. I would have said overseer, but then I would ask for the reader to crack the thesaurus. To not digress anymore, CISO not only need to have proper knowledge of what happens, but understand why happens, how happens and in the several contexts that happens. And that's hard.