IT administrators are struggling to deal with the ongoing fallout from the faulty CrowdStrike update. One spoke to The Register to share what it is like at the coalface.

Speaking on condition of anonymity, the administrator, who is responsible for a fleet of devices, many of which are used within warehouses, told us: “It is very disturbing that a single AV update can take down more machines than a global denial of service attack. I know some businesses that have hundreds of machines down. For me, it was about 25 percent of our PCs and 10 percent of servers.”

He isn’t alone. An administrator on Reddit said 40 percent of servers were affected, along with 70 percent of client computers stuck in a bootloop, or approximately 1,000 endpoints.

Sadly, for our administrator, things are less than ideal.

Another Redditor posted: "They sent us a patch but it required we boot into safe mode.

"We can’t boot into safe mode because our BitLocker keys are stored inside of a service that we can’t login to because our AD is down.

  • JasonDJ@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 months ago

    I get storing bitlocker keys in AD, but as a net admin and not a server admin…what do you do with the DCs keys? USB storage in a sealed envelope in a safe (or at worst, locked file cabinet drawer in the IT managers office)?

    Or do people forego running bitlocker on servers since encrypting data-at-rest can be compensated by physical security in the data center?

    Or DCs run on SEDs?

      • modeler@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 months ago

        You need at least two copies in two different places - places that will not burn down/explode/flood/collapse/be locked down by the police at the same time.

        An enterprise is going to be commissioning new computers or reformatting existing ones at least once per day. This means the bitlocker key list would need printouts at least every day in two places.

        Given the above, it’s easy to see that this process will fail from time to time, in ways like accicentally leaking a document with all these keys.

        • JasonDJ@lemmy.zip
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 months ago

          I think the idea is to store most of the keys in AD. Then you just have to worry about restoring your DCs.

    • catloaf@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      When I set it up at one company, the recovery keys were printed out and kept separately.