• bassomitron@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    5 months ago

    I’ve worked in IT for 15 years and it’s the first time I’ve heard SMS phishing condensed to smishing. But I specialize in servers and server security, so I’m not too surprised it’s a thing.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      We’re forced to take a cybersecurity online course every year, and I’m constantly confused at what the terms are supposed to mean. Like why is spear phishing a thing? Why do we need specialized terms for every conceivable variation of a concept?

      Let’s just stick with basic terms:

      • malware - malicious software
      • social engineering - covers calls, texts, emails, etc designed to get access to something they shouldn’t
      • cracking - breaking cryptography
      • security hacking - breaking secure systems by exploiting bugs, such as zero-days or unpatched systems, usually to get privilege escalation

      I may be missing a couple, but I think most cybersecurity concepts can fit in one of those categories.

      • bassomitron@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        Well, I’m not a cybersec specialist, but my job requires us to comply with NIST cyber security frameworks, including going through external audits every year. In my opinion, your basic generalities are fine for those not working in that field specifically.

        However, for cyber security analysts and other specialists, I think specific subcategories are necessary. The reason being, IT is an absolutely massive field that contains a ton of specialties. As such, that means there are roughly an equal variety of malicious actors in the same field.

        There’s no such thing really as a general “hacker” anymore. Especially when you take into consideration the rapid expansion of state sponsored cyber attacks/warfare. You’ll have specialists for various types of:

        • phishing (e.g. targeting general pop/employees, or those going for specific people)
        • cryptography (e.g. those who try to compromise an org’s PKI, or people finding vulns to exploit expired certs like what happened with Azure last year)
        • vuln hunters/exploiters (e.g. people that monitor known vulnerabilities and probe orgs’ defenses to see if those vulns are present/unpatched/unmitigated, or even people who try to discover new ones)
        • malware engineers (e.g. fairly self explanatory, but malware is a very broad term and can come in numerous shapes and sizes, like even using infected images on a website to conduct RCE on mobile devices like what happened a year or two ago)

        Sorry, tangent is getting a bit long-winded now. Anyway, tldr; general terms are fine for laymen or non-specialists, but more precise terms are beneficial for experts in that field.

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          Sure, specialists can and should use specialized terms. But that’s not what articles like this are targeting. Keep that to symposiums and whatnot, and keep the general public vernacular simple to avoid confusion. That’s all I’m saying.

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 months ago

              I suppose, but the article has nothing to do with data centers and is written like any other news article on regular news sites. It’s a little more tech focused, but still very accessible.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      5 months ago

      Open Source Security Podcast with Josh Bresher and Kurt Sigfried. It’s a pretty good source of news and discussion from a sysadmin perspective.