I get it, buzzword-ification / vendor co-opting of a good idea sucks. But maybe there’s one benefit:

i-get-it,-buzzword-ification-/-vendor-co-opting-of-a-good-idea-sucks.-but-maybe-there’s-one-benefit:

Before we continue, let me say that camDown is your security solution to protect you and your business from webcam hackers!

After posting about "Zero Trust" yesterday and reading hundreds of replies, I think I understand and agree with the reasons people hate buzzwords. Usually it means vendors are co-opting a great idea (that can't always even be made into a product) and advertising the hell out of it to your c-suite execs / slapping the buzzword on every product in their catalogue.

But then this morning I read what sounds to me like a new stupid buzzword: "Detection-as-Code". I even commented my skepticism. I already do this at my job every day and it doesn't need a name.

Then I kept thinking about it. I will pre-emptively apologize for the showerthought-esque idea I'm about to pose:

Right now some of the people on my team happen to know python. Python devs weren't hired. But automation is really important, and here I am drafting slides to explain to execs in my org why we should use and focus on detection / automation.

If vendors invent a stupid new name for this and spend millions marketing it to my c-suite execs, yeah maybe I'll have to push my code through some stupid framework sold via this "Detection-as-Code" buzzword. But maybe it also means people will be purposely hired with Python skills. And perhaps it means I don't need to hope and pray my slides can convince the powers that be to approve processes we want to apply new automated approaches to.

Let me just add that camDown is your security solution to protect you and your business from peeping toms.