IsDavisLuEnabledInActiveDirectory? Not any more. IsDavisLuGuilty? Yes. IsDavisLuFacingJail? Also yes A federal jury in Cleveland has found a senior software developer guilty of sabotaging his employer’s systems – and he’s now facing a potential ten years behind bars.…

  • archonet@lemy.lol
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    And that, kids, is why you leave breadcrumbs going to someone else if you’re going to do something stupid like this.

  • Taleya@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    Silly davis. Shoulda put a key element reliant on alerting his email address like most devs

  • jjjalljs@ttrpg.network
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    I’m reminded of some garbage post I saw in the hell known as LinkedIn. Some soulless suit was saying “Don’t do PRs - just let your team merge directly to production.” I didn’t engage with it because I hate everything about LinkedIn and its clickbait trash feed, but “it protects you from a lone disgruntled employee” was one of the reasons I thought about.

  • CosmicTurtle0@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    If this dev had this much access and his work didn’t do any sort of code review, I don’t understand how their CSOC or ISO isn’t on trial along with him.

    This is terrible OpSec.

    In order for me to create an IAM role, I have to have two different people to approve it, along with the access control team, along with a change review on what the role does and how it will authenticate.

    Dev teams cannot access production. Prod teams cannot access code directly. Only machine roles can access databases directly.

    We have so many checks and balances that it’s amazing we get anything done.

    • homura1650@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 days ago

      I work in a high security industry. You’d be amazed at what you can do if you are willing to ignore the process. Our real defense against insider threats is attribution, law enforcement, and incident recovery. By the sounds of it, that is exactly what happened.

    • ReluctantMuskrat@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 days ago

      Honestly remarkably stupid. His scheme had no way for him to claim plausible deniability. So while he got to gloat a little bit on the way out the door, he’s suffering far worse consequences than just being out of a job and I’m sure the legal fees he’s paying are ridiculous too.

      Also company would have suffered the same fate if he died also. So even if he got promoted and the company treated him well, the company and his coworkers would have suffered if he got hit by a bus. Dude was a selfish idiot.

      • harryprayiv@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 days ago

        I mostly agree but from the article, it’s clear that he only hatched his little stupid scheme when he got demoted.

    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 days ago

      Nah.

      We saw this happen in the 90’s when controls were practically non-existant.

      This behaviour (and his lack of concealing it), just reinforces you don’t want him as an employee - partly because he never considered the implications of his actions.

      Now he gets to deal with the legal consequences of this - court alone is going to be stressful and expensive, then jail time. Dude ended his career doing this.