- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Microsoft finally explains cause of Azure breach: An engineer’s account was hacked::Other failures along the way included a signing key improperly appearing in a crash dump.
Microsoft finally explains cause of Azure breach: An engineer’s account was hacked::Other failures along the way included a signing key improperly appearing in a crash dump.
Man, I’d hate to be that guy.
I wonder if there are repercussions for them? Like, eventually corporate hacking is going to be so sophisticated that even the most tech savvy will be vulnerable.
Successful credential theft can really never be blamed on a single individual unless it can be proved to be malice. It’s always a systemic failure, even in cases where the user didn’t follow a process because of X. The issue was the X in the process and another user would have done the same thing eventually.
And in this case we’re talking about technologically savvy person, an engineer (systems or software idk)
Well… we can’t always assume the engineers are technologically savvy, I’ve met some pretty bad ones.
Okay I’m just assuming the best from humanity. Probably shouldn’t always
Why would corporate hacking get sophisticated when the most efficient way to get access is still a simple phishing email?
The human is always the weakest cog in the machine… just wait until we’re all replaced.
Ideally your company follows the swiss cheese model of incidents. It’s not the people, but the processes in place that brought us there.
The only company I worked where that model didn’t follow was run by a moron who micromanaged, blamed people and was a Big fucking baby. That company went bankrupt after 3 years.
Probably only if he was found to be grossly negligent. Otherwise, it’s really more of a methodology/procedural failing on the company’s part
*are