@paul_ipv6 @jerry
That's the great thing about the word "cyber" – it means whatever the speaker wants it toean.
That's also the awful thing about the word "security."

@jerry too fastidious.
Just say "3.0" at some point.
Go with the SANS retro-encabulator video and then ask for questions 😉
@da_667 @jerry Yes, indeed. Especially the bean counters need to have an NPV waved at them!
But the rest of the board should also care about reputational risk.
So the lesson is that while CxO should care about data security and operational integrity - and the tech and training that that implies - it may need to be translated into money and shame to be salient...
@Viss @DamonHD @jerry I had a music major as my datacenter ops manager.
I want you to understand, I know that sometimes, someone changing majors and/or professions sometimes happens and that these people can be quite good in a totally difference space (edit:clarification), but this dude paid for a cleaning service that does datacenters to come and clean the datacenter. It didn't really need it, and was genuinely a waste.
Now, us replacing all of our network fabric, and re-doing our cable management, which was another huge endeavor, was a big win.
@jerry The importance of being able to marry technical jargon and precision with a layperson's understanding.
I have had so many senior leadership/Board discussions and it always boils down to being able to have a depth of understanding that allows for that ELI5 type of communication.
@jerry Knowing Corporate only gets you that far, at some point you must know the Individuals.
Risk perception and appetite is a deeply personal trait.
just enjoying the idea of referring to senior leadership as the blue screen of death 💀
@jerry I'd suggest two things: a) Ethics - should you do something, or should you say something when you discover a problem?
b) A couple of stories about why security researchers/sysadmins can be like magicians - because we will spend an inordinate amount of time on doing some tiny thing to absolute perfection in order to find out something that is bugging us:
1/ Clifford Stoll found an unauthorized user who had apparently used nine seconds/75cents of computer time and not paid for it. It was a KGB Hacker. Oh, and "The Cuckoos Egg" had a nice cookie recipe too.
2/ The XZ Backdoor was found by a user, testing SSH, who saw that logins were taking too long.....
@jerry Understand what the personal risks are for the board. Usually it is tied to shareholder value and/or profit loss.
Play on that. In for-profits, nothing else will work.
Sorry to sound so cynical.
GIVE THIS PERSON AN AWARD!!!
🎖️🏅🥇
@simplenomad @jerry it’s amusing to me that LLMs are better then the average security bug hunter
But they also can’t write secure code
@jerry relaying how their org is doing when compared with their peers. I get asked that on the weekly. Understanding the risk completely and how that impacts the org is really important too, and being able to explain that risk. Don't misspeak either, especially in consulting roles.
Don't be that nervous. They're just people at the end of the day who (hopefully) want to see their org mitigating future attacks. This one I notice a large difference between internal and consulting roles.