• Trainguyrom@reddthat.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        I’ve had some workplaces where they instituted overly heavy-handed crackdowns through IT Policy then rolled them back after a couple of weeks because someone in upper-manglement needed to see the impacts in the real world that they already were already warned of before they could be convinced that their genius new policy wasn’t such a good idea

  • shalafi@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    My last boss got rid of the pfSense routers because “open source is not secure”. I argued that pfSense has been vetted over and over and over again. Nope. “Everyone can see the source code.” That’s the fucking point!

    TBF, pfSense isn’t the fastest routing, but at our small company is was more than sufficient.

  • DickFiasco@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    Worked for a company that had a similar policy against free software, but simultaneously encouraged employees to use open-source software to save money. I don’t think upper management was talking to the IT department.

  • radix@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    “If you’re not paying for the product, then you are the product.”

    The phrase has its uses, but shit like this is what happens when it’s taken to the extreme.

  • neidu3@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 months ago

    My previous employer was bought by a huge company. I liked it in the small company, because I had freedom to do what was needed without much questions, and I was trusted to make the relevant decisions and purchases. Kind of a “Costs be damned, get it done in a reasonable amount of time” kind of arrangement.

    When we came under the big corpo, we got an email instructing us to list all the software we used/needed, so that it could be added to the whitelist that big corpo worked with. Anything not in the whitelist simply couldn’t run.

    I gave them the list, but spoke to my on-shore It guy that out in the field we often needed to install something that we didn’t need before on short notice, and waiting for a ticket to be resolved for an administrative matter had the potential to stop production.

    They found it easier just to make an exception for my work PC. I just had to promise not to VPN in to the office while running “weird” stuff, otherwise the higher ups would get upset.

    That’s fine. I had my own VPN for only the stuff I needed anyway. I VPNed into offshore production systems on a daily basis. I needed to VPN I to the office once or twice. Plus in my book, the “main” VPN client is what I consider weird software. My shit was basically a wrapper around openvpn.

    EDIT: To be fair, the huge corpo employer wasn’t unreasonable. It was just so large with so many employees that strct security implementations were needed for IT to have some sort of control. I was technically also IT, but I only dealt with field equipment, so that IT could focus on “normal” stuff. They trusted me to handle my end, they handled theirs, and we usually cooperated fairly well when our systems “met”.

  • psmgx@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    It’s not more secure, it’s so they can offload blame and have people to sue if/when something ugly happens. Liability control, essentially.

    We had to pay for fucking Docker container licenses at my last job because we needed an escalation to the vendor in case our SMEs couldnt handle things (they could), and so we had a vendor to blame if something out of our control happened. And that happened: we sued Mirantis when shit broke.