Interesting. It's the product analogy to corporate-level strategic self-disruption / s-curve jumping.

For those interested: www.amazon.com/CISO-Impact-...

I assume they were wearing suites while messaging, as that’s the important bit.

Where’s the circumspect about using systems not under government or personal control? What’s next… Facebook messenger? TikTok DMs?

The design *aesthetic* has been amazingly consistent over almost 30 years. But I remember from 2.1 to 6.2, waiting for the new distro to show up, often in part for slight changes to Beastie or fonts.

We dispensed with ‘owner’ right away. It was ambiguous, confusing, and subject to implicit reframe.

We chose: (data) steward, (data) custodian, (application) sponsor.

We redefined owner as always the subject (patient for patient data, company for company data).

And we don’t talk about it enough. We have poor language for it. Circa 2005, my first time CISO, I sat down with the director of corporate of strategy. We picked a set of ordinary words from English dictionary. Those words were key to having the conversations needed to addressing our challenges.

“Unhackable” — yeah, sure.

Reminds me of my FreeBSD CD distro days in the mid 90s. Good times.

This is such a great podcast series.

Certs help, but in the job, on the ground circumstances create a lot of erosion. Tech folk are not generally great at feedback - giving, asking for, receiving.