David Spark

And so I think if we want to stop being the afterthought, it needs to go from you should do these things to we have already done these things for you.

that we become a service model and we think of ourselves as enablers, that we will make your system secure before you even have to think about it.

I'm usually not on the receiving end, but... You get to go second on the bright side.

I have to answer first.

At least you, I suspect it wasn't even designed safe.

Let's be honest.

People are going to ignore your design style.

I mean, I really want to know what could possibly be worse than this because you're basically useless, but let's see.

Okay.

Cause the second one sounds pretty bad, but I have to bring it, bring up the near rule because anybody listening is like, well, if I get to change, which one would I rather inherit?

You probably want to inherit the first one.

Cause you're like, well, I can walk.

lock in and do enforcement if I've got a coherent, like everybody does it the same way.

But here's the reality.

Nobody will ever do it that way because the near rule says we don't get to change the near future.

We're stuck with this.

So either I have an on paper, beautiful architecture that nobody actually implements, which means

They have no security architecture at all.

Or in the second one, sure, I don't even know what my architecture is, but at least I have one.

And generally, it's pretty decent.