I recently learned that my company prefers closed-source tools for privacy and security.

I don’t know whether the person who said that was just confused, but I am trying to come up with reasons to opt to closed-source for privacy.

  • Libb ( Libb@jlai.lu ) 
    link
    fedilink
    English
    arrow-up
    22
    ·
    2 years ago

    I recently learned that my company prefers closed-source tools for privacy and security.

    I will suggest that same logic to my banker too: a vault whose key they won’t own, but I will. Don’t worry, all your money will be safe with me, it’s a promise 😇

  • wizardbeard ( wizardbeard@lemmy.dbzer0.com ) 
    link
    fedilink
    English
    arrow-up
    21
    ·
    2 years ago

    In my experience the “privacy and security” argument is a smokescreen.

    The real reason is that it makes someone else responsible for zero-days occuring, for the security of the tool, and for fixing security problems in the tool’s code. With open source tools the responsibility shifts to your cybersecurity team to at least audit the code.

    I don’t know about your workplace, but there’s no one qualified for that at my workplace.


    A good analogy: If you build your house yourself, you’re responsible for it meeting local building codes. If you pay someone else to build it, you can still have the same problems, but it’s the builder’s responsibility.

    • jim3692 ( jim3692@discuss.online ) OP
      link
      fedilink
      arrow-up
      6
      ·
      2 years ago

      That smokescreen argument makes a lot of sense. Both the company and our clients, tend to opt for ready out-of-the-box proprietary solutions, instead of taking responsibility of the maintenance.

      It doesn’t matter how bad or limiting that proprietary option is. As long as it somewhat fits our scenario and requires less code, it’s fine.

      • 0x0 ( 0x0@programming.dev ) 
        link
        fedilink
        arrow-up
        7
        ·
        2 years ago

        instead of taking responsibility

        This is why, they prefer to shift the blame in case it hits the fan. That’s all, that’s it.
        They don’t care about code quality, maintainability or whatever.

      • Ulrich ( Ulrich@feddit.org ) 
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 years ago

        That smokescreen argument makes a lot of sense.

        I don’t think it does. Remember the Crowdstrike blunder? Remember how many people blamed Windows?

        People don’t know or care who is managing your security.

  • navi ( navi@lemmy.tespia.org ) 
    link
    fedilink
    arrow-up
    11
    ·
    2 years ago

    Security through obscurity isn’t security.

    The classic example:

    I have a website with no authentication which displays data that really should be locked down. But it’s OK because I never told anyone else the URL so no one will find it.

    • jim3692 ( jim3692@discuss.online ) OP
      link
      fedilink
      arrow-up
      3
      ·
      2 years ago

      I don’t understand this mindset.

      In open source, both malicious actors and contributors will try to find problems.

      In closed source, the development team is paid by hour (and probably don’t care about the product quality) and the only motivated people to find real issues are malicious actors.

      But people still consider closed source safer.