Then it ain't IT's ass that should be on the line.
Still. Right, wrong, or in-between, the buck stops there.
I say this because I'm sure we've both been in situations where someone was throwing their weight around to get something really stupid (like a 3 character password) put in place.
Been there. And if that's the case, you document what was done, memo it along with your caveats, and copy relevant parties. Doing that saved my butt on at least three occasions in my career. Never leave yourself being the only one without a chair (and at the mercy of a bout of "corporate amnesia") when the music stops.
Doesn't look like any of that happened much at Sony though. It mostly looks like they ran a very
loose ship when you consider the variety and number
of absolutely bonehead things they we allowing to happen. Or possibly simply ignoring when they did. If it were one obscure bug, or some crazy zero-day exploit that cracked them, I'd be much more sympathetic. But these people weren't consistently
doing even the basic stuff they teach you in tech school, let alone what seasoned professionals should be aware of - and be doing.
If you ain't part of the solution, you're part of the problem. And in my experience, if you play along without objection, you'll be one of the first they let go when things go sideways. Because like it or not, as IT people, it is
our responsibility. And there's just no getting around that
Or so I think.