this post was submitted on 19 Jan 2024
59 points (84.7% liked)
Technology
59589 readers
2936 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 another!
- 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
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The title is bad. One scan that generates thousands of alerts is generally considered one event. Companies that have a massive footprint naturally get many thousands of scans a day. It's normal.
Also, +60,000 people and $16 billion dollars is misleading. The people they pay the most are the ones that generally don't know shit about IT. Sure, some of those technologists are probably top-tier, but actual security experts don't usually come in large groups. There are exceptions, of course.
Large companies pay way too much for generic security solutions. In some ways they are forced, because their infrastructure is massive and they need tons of customization but there is always a fuck ton of waste.
Using big numbers sounds cool, unless you are in the industry and understand that there is a ton of fluff involved.
Honestly as a engineer, I sometimes uses puff pieces like this to get my company to act. How many times have I called out a vulnerability that the company goes, "Meh not important".
It's an art form to get people to give a shit about security. Sometimes puff pieces work, sometimes they don't. Dull numbers are usually more effective: A vulnerability needs to have a specific risk, is easy/hard to execute and could cost the company x dollars if exploited and would only cost x dollars to fix in x amount of time.
You have to summarize the risk and cost to the organization instead of trying to explain the problem in all its detail.
You probably knew that, but just passing along how I have had to cope over the years.