@Brkdncr@lemmy.world to Technology@lemmy.worldEnglish • 10 months agoLet's blame the dev who pressed "Deploy"yieldcode.blogexternal-linkmessage-square68fedilinkarrow-up1280arrow-down113
arrow-up1267arrow-down1external-linkLet's blame the dev who pressed "Deploy"yieldcode.blog@Brkdncr@lemmy.world to Technology@lemmy.worldEnglish • 10 months agomessage-square68fedilink
minus-square@floofloof@lemmy.calinkfedilinkEnglish19•10 months agoReminds me of Microsoft’s response when one of their employees kept trying to get them to fix the vulnerability that ultimately led to the Solar Winds hack. https://www.propublica.org/article/microsoft-solarwinds-golden-saml-data-breach-russian-hackers
minus-squaremorriscoxlinkfedilinkEnglish7•10 months agoAnd the guy now works for CrowdStrike. That’s ironic.
minus-squareAmandalinkfedilinkEnglish3•10 months agoI’m imagining him going on to do the same thing there and just going “why am I the John McClain of cybersecurity? How can this happen AGAIN???”
minus-squaremorriscoxlinkfedilinkEnglish1•10 months agoHis next job might look at his job history and suddenly decide that the position is no longer available.
Reminds me of Microsoft’s response when one of their employees kept trying to get them to fix the vulnerability that ultimately led to the Solar Winds hack.
https://www.propublica.org/article/microsoft-solarwinds-golden-saml-data-breach-russian-hackers
And the guy now works for CrowdStrike. That’s ironic.
I’m imagining him going on to do the same thing there and just going “why am I the John McClain of cybersecurity? How can this happen AGAIN???”
His next job might look at his job history and suddenly decide that the position is no longer available.