Sep 17, 2026 · 45 min · 10 segments
In 2005, Benny Czarny had a simple mission: build a cybersecurity language that helped products talk to each other. Twenty years later, that mission has evolved into something far bigger — protecting…
Benny CzarnyGuestBrianHostSo the first question I have for you is, Benny, the more I started to dig into OpsWatt and the founder story behind it, the more I just became really kind of glued to how you've fundamentally thought about building the business in the cybersecurity space and what you saw.
And before the call, you said to me, if you are thinking about a long-term solution to have an impact in an industry, you should start out with OEM.
I think what would be super helpful is if you can articulate maybe what you saw specifically in the cybersecurity industry and the maybe long-term mindset that you applied to how you went about uncovering the problems that you saw to eventually build a solution that would really change the industry.

So if you ask me this question today, I would answer you a completely different answer I would answer you 15 years ago.

So I'm running the company for more than 20 years and obviously it's more about evolution.

And after a few years of a very successful OEM business, managed to pivot the company into enterprise business.

So if you ask me today, what's the mission? The mission today is to protect the world's critical infrastructure.

And what drives me is to be the company that protect critical infrastructure, the company to provide the platform, the company that provide the training and the purpose to build technologies to protect our way of life.

And the, Going back to the question about if you'd asked me this question in 2005, I would answer you something completely different.

I would tell you my mission is to create a cybersecurity language that enables cybersecurity products to better communicate.
shift, huh?

Think about that from a cybersecurity language to critical infrastructure protection.
So you're saying that the shift of, you see it today at the enterprise level of building critical infrastructure, but when you were thinking primarily entering the space, it was a bit different or maybe the vision hadn't fully formed in the way it has today.
Is that what I'm hearing from you?

Initially it was, let's build cybersecurity language that enables, you know, Cisco, Palo Alto Networks, HP, everybody to communicate with hundreds of antiviruses, hundreds of encryption devices, hundreds of... a peripheral media security patch management solution.

That evolved through kind of deep, kind of first testing, some of that by leveraging existing businesses and trying to do more, trying to keep kind of challenging yourself and everybody surrounding me.
So the first question I have for you is, Benny, the more I started to dig into OpsWatt and the founder story behind it, the more I just became really kind of glued to how you've fundamentally thought about building the business in the cybersecurity space and what you saw.
And before the call, you said to me, if you are thinking about a long-term solution to have an impact in an industry, you should start out with OEM.
I think what would be super helpful is if you can articulate maybe what you saw specifically in the cybersecurity industry and the maybe long-term mindset that you applied to how you went about uncovering the problems that you saw to eventually build a solution that would really change the industry.

So if you ask me this question today, I would answer you a completely different answer I would answer you 15 years ago.

So I'm running the company for more than 20 years and obviously it's more about evolution.

And after a few years of a very successful OEM business, managed to pivot the company into enterprise business.

So if you ask me today, what's the mission? The mission today is to protect the world's critical infrastructure.

And what drives me is to be the company that protect critical infrastructure, the company to provide the platform, the company that provide the training and the purpose to build technologies to protect our way of life.

And the, Going back to the question about if you'd asked me this question in 2005, I would answer you something completely different.

I would tell you my mission is to create a cybersecurity language that enables cybersecurity products to better communicate.
shift, huh?

Think about that from a cybersecurity language to critical infrastructure protection.
So you're saying that the shift of, you see it today at the enterprise level of building critical infrastructure, but when you were thinking primarily entering the space, it was a bit different or maybe the vision hadn't fully formed in the way it has today.
Is that what I'm hearing from you?

Initially it was, let's build cybersecurity language that enables, you know, Cisco, Palo Alto Networks, HP, everybody to communicate with hundreds of antiviruses, hundreds of encryption devices, hundreds of... a peripheral media security patch management solution.

That evolved through kind of deep, kind of first testing, some of that by leveraging existing businesses and trying to do more, trying to keep kind of challenging yourself and everybody surrounding me.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.