• lad@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    Professionals in software development do not mean professionals in cyber security.

    Same way you don’t expect a geologist to be a mason

    • prof@infosec.pub
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 months ago

      That’s a bad take. Unless you get your knowledge purely from shady tutorials or have a fast track bootcamp education, it’s unlikely you never touch on security basics.

      I’m a software design undergrad and had to take IT Sec classes. Other profs also touched on how to safely handle dependencies and such.

      While IT Security is its own specialisation, blindly trusting source code others provide you with is something a good programmer shouldn’t do.

      If you need a metaphor: Just because a woodworker specialises in tables, doesn’t mean they can’t build a chair.

      • lad@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        I graduated in CS in this century and we never touched on security. If not for my own curiosity and obligatory annual compliance education on the job (and only on the last one) I would have known near nothing

      • expr@programming.dev
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        In my experience, your average software developer has absolutely terrible security hygiene. It’s why you see countless instances of private keys copy/pasted into public GitHub repos or the seemingly daily occurrences of massive data breaches.

        My undergrad in CS (which I should point out, is still by far the most common major for software engineers) did not require a security course, and I’m fairly confident that this is pretty typical. To be honest, I wouldn’t have trusted any of my CS professors to know the first thing about security. It’s a completely different field and something that generally requires a lot of practical experience. The closest we ever got was an explanation of asymmetric vs. symmetric encryption. There was certainly no discussion of even basic things like how to properly manage secrets or authn best practices.

        Everything I know now as a senior software engineer about software security has come from experience on the job. I’ve been very fortunate to work at some places that take it very seriously (including a government contractor writing cybersecurity software for the Department of Defense) and learned a lot there. But a lot of shops don’t have a culture that promotes good security hygiene, and it shows in the litany of insecure software out in the wild today.

      • Dra@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        6 months ago

        You are young and blissfully naive. Sec being included with development is a recent thing