Chris Griffin, who has volunteered with the Open Source Security Testing Methodology Manual for two decades, explains where Zero Trust works well and where it falls short. He cautions against rushing adoption, especially outside cloud environments where gaps remain.
I have been a volunteer with the Open Source Security Testing Methodology Manual for 20 years this year. Nice.
Completely volunteer position. Volunteer.
So they doubled your salary of zero.
Yes. It's nice.
At least the pay increase is steady.
Yeah. Right.
Awesome. Chris, so tell me about Steve, man. Let's unpack some things here. So I'm here. I wanted, I'm all on zero trust. I'm saying I'm ready to put it in tomorrow. What are you saying to stop me or give me some, give me some details.
I say that if you're doing it for the cloud, it can make sense if done right. Everything else, it leaves a lot of gaping holes that not only does it not try to fill, it completely ignores. There's a lot of neglect when it comes to, a lot of blind trust, frankly, when it comes to certain aspects of security, when their motto is never trust, always verify.
