• Avid Amoeba
    link
    fedilink
    461 year ago

    I just came to note that seeing Mastodon inserts instead of Twitter in an Ars article makes me feel warm and fuzzy.

    • BrikoXOP
      link
      fedilink
      English
      221 year ago

      That’s where infosec people are these days.

  • sadreality
    link
    fedilink
    181 year ago

    The old trope is so tired I am still amazed corporate propaganda shills it… it just looks even worse… iT wuZ aN InTerN, ExeC DiNDu NufIn

  • AutoTL;DRB
    link
    fedilink
    English
    121 year ago

    This is the best summary I could come up with:


    While the postmortem emphasizes the transgressions of an employee logging into a personal Google account on a work device, the biggest contributing factor was something the company understated: a badly configured service account.

    In a post, Okta chief security officer David Bradbury said that the most likely way the threat actor behind the attack gained access to parts of his company’s customer support system was by first compromising an employee’s personal device or personal Google account and, from there, obtaining the username and password for a special form of account, known as a service account, used for connecting to the support segment of the Okta network.

    “During our investigation into suspicious use of this account, Okta Security identified that an employee had signed-in to their personal Google profile on the Chrome browser of their Okta-managed laptop,” Bradbury wrote.

    Accessing personal accounts at a company like Okta has long been known to be a huge no-no.

    Unlike standard user accounts, which are accessed by humans, service accounts are mostly reserved for automating machine-to-machine functions, such as performing data backups or antivirus scans every night at a particular time.

    The breach, however, underscores several faults that didn’t get the attention they deserved in Friday’s post.


    The original article contains 473 words, the summary contains 203 words. Saved 57%. I’m a bot and I’m open source!

  • @kill_dash_nine@lemm.ee
    link
    fedilink
    English
    61 year ago

    How does Okta not have systems like support systems like what was breached with the credentials behind a VPN as well? A system like that really ought to be on a secured network. We have so many systems at work that are VPN required and it’s mostly those where sensitive data lives.

  • @quicken@aussie.zone
    link
    fedilink
    51 year ago

    I could see my own company falling victim to this kind of attack. I guess for a targeted attack all personal Google accounts or other password managers are a vulnerability. I’d cry if my work blocked the chrome password manager.

    • @linearchaos@lemmy.world
      link
      fedilink
      English
      11 year ago

      I stopped using browser built in password managers a long time ago. Third party password managers that require 2FA on a timeout are where it’s at. All of my passwords are available on all web browsers and my mobile device as necessary

    • @library_napper
      link
      1
      edit-2
      1 year ago

      Dont bind to IP or other browser fingerprinting.

      For security and privacy, my IP address and browser fingerprint change every 60 seconds. Its so fucking annoying when I get false-positive logged out every minute “for my security”

      • ISometimesAdmin
        link
        fedilink
        21 year ago

        I hesitate to ask, but, why do you have your IP change every minute? You seem to have a very atypical usecase

        • @library_napper
          link
          21 year ago

          I was oversimplifying. So the user agent and other browser setting change every 60 seconds using the chameleon add-on.

          The IP doesn’t automaticallychanges, but I use a VPN. Often on shitty internet where packet loss routinely spikes to 30% (considered normal for most ISPs), I often have to disconnect and reconnect to the VPN, which causes the IP to change.