Hello, everybody. Welcome to the ThoughtWorks podcast. My name is Rebecca Parsons. I'm the

Chief Technology Officer for ThoughtWorks. And my name is Mike Mason. I'm head of technology

with ThoughtWorks, and I work closely with Rebecca in her office of the CTO,

and together we're co-hosts for the ThoughtWorks podcast. Today we're joined by two of our security experts,

Cade and Ken, to talk about DevSecOps. So, Cade, would you like to introduce yourself? Sure. I'm

Kate Cairns. I'm a principal technologist here at ThoughtWorks. I've a very, fairly long career

in IT spanning a lot of development roles and also a pretty good blend of security. These days,

I'm more focused on the intersection of the two.

And Ken, could you say hi and introduce us off?

Sure. So I'm Ken McGrage.

I am a technology advocate for ThoughtWorks products.

I've been working with Kenner's delivery for quite some number of years,

nine or ten years now.

I'm also a global organizer for a

conference series called DevOps Days, which is where the term DevOps came from. Thank you, Kate.

Thank you, Ken. I'd like to start to talk a little bit about DevOps in general and, you know,

some of these notions that are floating around devsec ops some of the other

it seems like dev followed by the kitchen sink followed by ops is is one of those memes going around

but ken can you tell us a little bit about uh devops and and how you see uh security and aspects

of security and dev of security in DevOps?

Sure, happy to.

So first off, I think I like to think of DevOps as a portmendo of two verbs instead of nouns.

...