• BorgDrone@feddit.nl
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 hours ago

    If you’ve ever used it you can see how easily it can happen.

    How could this happen easily? A regular developer shouldn’t even have access to production outside of exceptional circumstances (e.g. diagnosing a production issue). Certainly not as part of the normal dev process.

    • tempest@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      They shouldn’t and we know that but this is hardly the first time that story has been told even before LLMs. Usually it was blamed on “the intern” or whatever.

      • BorgDrone@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 hours ago

        This isn’t just an issue with a developer putting too much trust into an LLM though. This is a failure at the organizational level. So many things have to be wrong for this to happen.

        If an ‘intern’ can access a production database then you have some serious problems. No one should have access to that in normal operations.

        • tempest@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          2 hours ago

          Sure, I’m not telling you how it should be, I’m telling you how it is.

          The LLM just increases the damage done because it can do more damage faster before someone figures out they fucked up.

          This is the last big one I remembered offhand but I know it happens a couple times a year and probably more just goes unreported.

          https://www.cnn.com/2021/02/26/politics/solarwinds123-password-intern

          Why would an intern be given prod supply chain credentials, who knows. People fuck up all the time.