this post was submitted on 22 Sep 2023
93 points (94.3% liked)
Technology
61850 readers
2313 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think as more gen z enters the workforce we’re going to start seeing more breaches because they’re not going to give a shit when they see someone in the csuite making 1000x what an average person makes. Especially when they can barely afford to eat and need 5 roommates.
If these places want to stop that from happening the best way is to pay your staff EXTREMELY well and setup things like pensions and profit sharing.
I guess you didn't read the article or think about what you're saying?
They aren't phishing low tier workers. They're getting executives and people high up in companies to the data they're after. They aren't getting in by using an hourly employees info.
It's the low tier employees that usually monitor for breaches and anomalies and they just won't give a shit.
And “tech debt” (which I’m sure said execs would lump refactoring infrastructural security under) isn’t a new feature that generates money, so it’ll get consistently deprioritized.
Source: am software+devops engineer
Cyber gets paid but help desk folks, ops managers, general help staff, and the little people with too much least privilege who actually get shit done usually aren’t.
Source: am executive with compliance history
The article explicitly talks about social engineering. If you’ve solved social engineering for the positions I listed, you have effectively ended the need for most security solutions. Yes, we can mitigate its effects, but no, watching doesn’t prevent it which was the context of this thread.
You have to define adversary objectives then separate those from normal behavior. Again, you haven’t solved the problem raised in the thread. How are you, a highly paid cyber security professional, going to prevent social engineering from allowing privilege escalation and negative outcomes ranging from fraudulent invoices to knowledgeable, intentional use of applications following expected behavior?
Read the article.