رونوشت 🔗
WEBVTT
00:00:00.239 --> 00:00:04.240
The Security Champions Podcast is brought to you by Security Journey.
00:00:04.320 --> 00:00:10.960
We help enterprises reduce vulnerabilities through application security education for developers and everyone in the SDLC.
00:00:11.119 --> 00:00:13.599
Learn more at SecurityJourney.com.
00:00:18.000 --> 00:00:23.920
Welcome back to another episode of the Security Champion Podcast.
00:00:24.320 --> 00:00:27.359
This one is a very special episode.
00:00:27.440 --> 00:00:30.399
I'm joined by my guest, Michael Urquet.
00:00:30.800 --> 00:00:34.000
Um, gonna be quite more than a guest on this episode.
00:00:34.240 --> 00:00:38.640
So we're gonna do a kind of an announcement for what we're gonna be doing today, right?
00:00:38.719 --> 00:00:39.359
What is the topic?
00:00:39.600 --> 00:00:41.679
Usually I talk about what are we gonna be talking about today?
00:00:41.759 --> 00:01:04.000
And actually, um, the topic is AI champions and actually a transition, uh a transition to the idea that uh Michael Irquet, um, one of our amazing security engineers at here at Security Journey, is going to be taking the lead as the host of the Security Champion podcast.
00:01:04.079 --> 00:01:08.719
Um, as I slowly change where my focus and work's gonna be.
00:01:08.959 --> 00:01:12.480
Um, as we kick this off, though, I think what we're gonna do is we're gonna start.
00:01:12.560 --> 00:01:22.640
I'm gonna do do a little bit of a reflection, a little talk about where we've come, how I've got to be where we are with the security champion podcast.
00:01:22.799 --> 00:01:30.239
And then I'm gonna have uh Mike share a little bit about himself and his journey, and then uh we'll kind of take it from there.
00:01:31.280 --> 00:01:38.000
As we kick it off, kind of talk about where I am, where I've gone, what what's what is this transition about, right?
00:01:38.079 --> 00:01:39.040
All this type of stuff.
00:01:39.120 --> 00:01:40.400
Um, let's talk about my story though.
00:01:40.480 --> 00:01:46.239
Let's I I think really it's not about my story, it's about a story about the podcast itself, is what it really is.
00:01:46.560 --> 00:01:53.040
Um interestingly, though, years ago now, it's actually surprising for me to say that now, it's been years.
00:01:53.200 --> 00:01:57.760
Um, Security Journey, the main had a podcast, right?
00:01:57.920 --> 00:01:59.920
And it was actually um led by Chris Romeo.
00:02:00.000 --> 00:02:04.799
He still runs that podcast, uh, an amazing podcast, the Application Security Podcast.
00:02:04.959 --> 00:02:08.400
If you ever get a chance to check it out, big kudos, a great program.
00:02:08.479 --> 00:02:14.879
I've been on, I've actually been on a guest there too, which was a great, great honor to be able to come in and talk about that, the type of stuff we did.
00:02:15.039 --> 00:02:23.199
Um, but when Security Journey was acquired, Chris Romeo kind of went on and started some other passion projects, continued with this podcast.
00:02:23.520 --> 00:02:27.360
But here in our in our world, we had a gap.
00:02:27.680 --> 00:02:44.319
And I had been super passionate about the space and the idea of podcasting and continuing that type of culture we had built of communicating with the rest of the world about the things that we think of and believe of, and enabling people to be champions.
00:02:44.400 --> 00:02:48.159
And the idea came around security champions.
00:02:48.240 --> 00:02:52.000
Uh, security journey has always had a special part place in their heart for champions.
00:02:52.080 --> 00:02:54.000
We have a part of our product that helps it.
00:02:54.159 --> 00:03:00.879
Um, we involved, work with a lot of our customers on their champion programs and building and educating and enabling them.
00:03:01.039 --> 00:03:08.240
So it seemed like the perfect fit to create a podcast around security champions.
00:03:08.560 --> 00:03:10.000
Um, so we started that out.
00:03:10.080 --> 00:03:18.400
It was just kind of a pilot idea, started, and the best part was my first actually, my very first guest was Chris Romeo himself.
00:03:18.560 --> 00:03:24.639
Um, and he had actually created a maturity framework around champion programs.
00:03:24.719 --> 00:03:26.879
He actually uh he has an open source project.
00:03:27.039 --> 00:03:31.039
You can actually go and look at the security champion framework that he developed.
00:03:31.199 --> 00:03:33.759
And we just got to jump in and have a conversation.
00:03:33.840 --> 00:03:38.960
And it was uh this kind of those, but actually, it was almost kind of in the same vein of what we're doing today, right?
00:03:39.039 --> 00:03:48.240
Is the fact is I was able to do my first podcast as kind of a handoff starting, tank in the mantle of starting this new brand around champions.
00:03:48.719 --> 00:03:50.800
Um, and and it grew from there.
00:03:50.879 --> 00:04:04.879
And the best part, and as I kind of look back and I think about all these, especially the early on conversations, is um, I got to reach out to my friends that were in the industry, that were thought leaders around defining what this stuff looks like.
00:04:05.039 --> 00:04:08.400
And I got to invite them on to have a conversation with me.
00:04:08.560 --> 00:04:10.879
Um, quite a few amazing people, right?
00:04:10.960 --> 00:04:13.840
I I think every one of the talks I had, I learned something.
00:04:14.000 --> 00:04:18.079
And one of the interesting things, it wasn't just learning more about being a champion.
00:04:18.240 --> 00:04:20.959
It was learning more about this, right?
00:04:21.279 --> 00:04:25.839
About running a podcast, finding the right people, having the right conversations.
00:04:26.000 --> 00:04:27.920
And some conversations were stronger than others.
00:04:28.079 --> 00:04:29.680
Uh, that's one of the things I realized before.
00:04:29.839 --> 00:04:31.199
They were all valuable, right?
00:04:31.360 --> 00:04:36.240
But it redefined
Load full transcript
the way I think of like, how do you find the right person that is passionate about this?
00:04:36.399 --> 00:04:43.680
Um, someone that isn't just selling a product or that just kind of wants the 30 seconds to be able to come up here and say something that's their message, right?
00:04:43.759 --> 00:04:47.040
That has a real passion about sharing knowledge.
00:04:47.199 --> 00:04:49.680
Um, that was the most exciting part.
00:04:49.839 --> 00:05:00.319
Like, whether it's people that had written books on the topic, um, some of my favorite people were people that had run champion programs in their own organizations that had stories to tell, or there were champions themselves.
00:05:00.480 --> 00:05:02.079
Um, we even branched out, right?
00:05:02.160 --> 00:05:04.399
When I first started, I was like, everything's gonna be champion.
00:05:04.480 --> 00:05:11.759
And one of the coolest, some of the coolest conversations actually came from stuff that had nothing to do with actual champions, it just was good app sec fun conversations.
00:05:12.000 --> 00:05:28.560
Um, whether we're talking, I've talked on quantum computing or um talking about other just passionate things around security testing, or what what does it mean to be a developer in the world of um champions and culture and change and its value.
00:05:29.120 --> 00:05:45.839
I think that was some of the best stuff that I kind of gained from from this experience is is not only learning about champ more about champion programs and bringing that passion to people that need it, but learning about how to communicate and build community and culture.
00:05:45.920 --> 00:05:50.800
And actually, founded one of my other favorite things that came out of this is we created the conference, right?
00:05:50.879 --> 00:06:00.079
The security champion conference last year was a direct growth from running this podcast, um, which is another one.
00:06:00.399 --> 00:06:10.399
And actually, like teaser, we're gonna be doing a call for papers here really soon for this coming year's in October Security Champion Summit that we're gonna be running again this year.
00:06:10.639 --> 00:06:14.639
Virtual conference, everybody should join and kind of be a part of that.
00:06:14.800 --> 00:06:19.279
Um, teaser, there will be an AI twist to some of the stuff that we're talking about.
00:06:19.360 --> 00:06:21.199
Um, big surprise, right?
00:06:22.560 --> 00:06:27.600
Um, but yeah, I mean that that's like I said, the valuable lessons learned, the amazing people that have been found.
00:06:27.839 --> 00:06:37.199
It's been such an amazing experience, and I'm very honored and humbled of all the people that take their time to actually listen to me talk about these topics and meet with people on this.
00:06:37.360 --> 00:06:48.000
Um, even and actually, and I got to throw a shout out to Dustin Lair, who for a while had come in and had brought his own like flavor and different people to share their stories and thoughts and everything else.
00:06:48.079 --> 00:06:55.040
So it's been it's been a multi-person project that's kind of changed and adapted over the years, depending on what's been going on.
00:06:55.279 --> 00:06:58.800
So that's been it's been a big, it's been a big, very passionate about this.
00:06:58.959 --> 00:07:03.360
Very uh a little heartbroken to be handing it off, but really excited to see what you're gonna be doing with it.
00:07:03.519 --> 00:07:18.959
Um, so I want to with all that said about me, Mike, I would love to like give you the moment in this stage to kind of talk about kind of you coming in as this educator and champion lead and kind of tell your story behind it.
00:07:19.439 --> 00:07:20.959
Yeah, no, appreciate it, Mike.
00:07:21.040 --> 00:07:31.519
And just another shout out to Dustin and Chris and just being associated with them and what they've built and really added to this podcast as you kind of take your direction forward.
00:07:31.839 --> 00:07:37.040
And, you know, myself, I've been here at Security Journey for a few years, worked under Mike.
00:07:37.120 --> 00:07:53.839
They just call me mini Mike sometimes because it's just we have similar background, but we have a very different kind of perspective on, you know, security champions, what that's meant in the past, and now, especially in the last 18 months, what it means in the future.
00:07:54.000 --> 00:07:57.040
Uh everyone's heard, you know, AI this, AI that.
00:07:57.439 --> 00:07:58.720
And it's very important.
00:07:58.959 --> 00:08:05.120
Obviously, we need to understand these concepts, but we need to also understand how it affects that person.
00:08:05.439 --> 00:08:09.920
And that's really where I want to kind of drive it through, because this is no longer just app sec.
00:08:10.399 --> 00:08:11.439
We're moving beyond it.
00:08:11.519 --> 00:08:26.480
We have, you know, cyber physical systems that are controlled by AI that affect real-world people, you know, from autonomous driving to satellite security, all the way throughout, you know, from literally up into space all the way down.
00:08:26.639 --> 00:08:31.120
So we're going to take a more diverse approach with these new episodes.
00:08:31.279 --> 00:08:38.720
But yeah, just a little bit about myself and really honored to be uh the new host and excited to take it somewhere new.
00:08:39.360 --> 00:08:42.799
And and you this isn't the first time you've been on the podcast, right?
00:08:43.120 --> 00:08:43.759
No, yeah.
00:08:43.919 --> 00:08:44.159
Yeah.
00:08:44.240 --> 00:08:48.000
We had a great talk, um, what was that, about eight months back or something.
00:08:48.159 --> 00:09:02.960
And yeah, it's just great to just have, you know, a platform to be able to just share your thoughts and then have people on to give counterpoints and kind of learning through it all together and not get caught up in a in a hype circle or vendor log.
00:09:03.120 --> 00:09:05.519
You know, it's just it's a great platform for
that.
00:09:05.600 --> 00:09:09.440
And I'm excited to kind of build that and the community around it.
00:09:10.159 --> 00:09:12.960
Yeah, I'm excited for a fresh perspective on this, right?
00:09:13.120 --> 00:09:14.799
Because uh I don't know if anyone's met me.
00:09:14.879 --> 00:09:16.639
I have a few opinions about things, right?
00:09:16.799 --> 00:09:18.879
And I'm pretty dug into my opinions.
00:09:19.200 --> 00:09:24.639
It'll be good to have a new lens to think about this and view this in for sure.
00:09:24.879 --> 00:09:28.639
Um, interesting part, like you kind of hint towards like similar backgrounds.
00:09:28.799 --> 00:09:29.759
I do want to call out.
00:09:29.840 --> 00:09:33.679
I'm kind of excited to hand off uh the podcast to another Green Beret.
00:09:34.000 --> 00:09:41.919
Uh so another someone from another very similar background uh coming from us, like just by chance happens to be the way it worked out.
00:09:42.240 --> 00:09:46.240
Um also as kind of that teaser of why, right?
00:09:46.320 --> 00:09:49.120
Why, why, why is some of this transition, right?
00:09:49.279 --> 00:09:55.679
Um, one of the big things, and uh kind of an announcement for the podcast, my role has changed with security journey.
00:09:55.840 --> 00:09:58.879
Um, I am no longer the director of application security.
00:09:58.960 --> 00:10:02.320
I'm now the VP of AI enablement and acceleration.
00:10:02.559 --> 00:10:05.279
Big emphasis on that enablement part, right?
00:10:05.919 --> 00:10:08.240
Um, which which is interesting, right?
00:10:08.320 --> 00:10:10.799
Because we talk about what's the AI impact on everything, right?
00:10:10.879 --> 00:10:17.200
Well, AI, AI has definitely had a huge impact here, the way we think about what we're doing at Security Journey.
00:10:17.279 --> 00:10:20.720
Um, but also at the idea of like, what is a security champion?
00:10:20.799 --> 00:10:21.759
How does all that work?
00:10:21.919 --> 00:10:22.879
Everything else, right?
00:10:23.039 --> 00:10:24.799
So it's very impactful.
00:10:24.960 --> 00:10:32.720
And as such, um, I'm gonna be leading on to drive some more of those AI efforts here um in the the near future.
00:10:33.200 --> 00:10:36.960
Um so yeah, I think uh I think that's an interesting part.
00:10:37.039 --> 00:10:38.480
So here's what I'm gonna do though, right?
00:10:38.559 --> 00:10:40.559
Because part of this is this is a transition.
00:10:40.720 --> 00:10:42.639
This is uh handing off the mantle.
00:10:42.720 --> 00:10:48.799
So so at almost this point, um, I don't know it's uh necessarily about me asking you questions, right?
00:10:48.960 --> 00:10:54.799
It's about you taking the driving seat and maybe you driving the questions, our conversation as we put this.
00:10:54.960 --> 00:10:58.000
By the way, I didn't prep Mike for this, so he's now in the hot seat.
00:10:58.159 --> 00:11:06.159
And now you you're gonna lead this transitional um podcast for us of moving into the future.
00:11:06.639 --> 00:11:09.679
Yeah, and I think that's really the best starting point.
00:11:09.840 --> 00:11:12.080
And I'm gonna share my view completely with you.
00:11:12.320 --> 00:11:21.120
I think from when you started and took over this podcast until now, the role of security champions has completely broadened out.
00:11:21.360 --> 00:11:28.399
I don't think it's, you know, that security focused developer on a small team or shifting left like we used to talk about.
00:11:28.639 --> 00:11:31.519
I think that's incredibly now opened up.
00:11:31.600 --> 00:11:40.799
And I want to hear kind of your opinion on that and maybe where some of these gaps are from that point to this point and really what we need to look at in the future.
00:11:41.440 --> 00:11:45.600
Well, the interesting part about that, right, is we bring up the the AI impact, right?
00:11:45.840 --> 00:11:50.320
And and why would that change the way we think about champions, right?
00:11:50.480 --> 00:11:57.120
And and fundamentally, um, part of that is is the that's like defining the original, right?
00:11:57.279 --> 00:12:03.200
The original champion is, and at least the way we use it here, is I have a team that does work.
00:12:03.919 --> 00:12:13.840
They aren't necessarily security experts, they're engineers, they solve problems, they might have some security knowledge, but that's not their primary focus.
00:12:14.000 --> 00:12:22.240
So, us as a security team, we find somebody on that team to evangelize about security and help embed security as part of the development workflow, right?
00:12:22.320 --> 00:12:27.360
And there's a lot of different strategies we talk about finding the right person, enabling, educating everything else.
00:12:27.600 --> 00:12:46.720
In a world, though, that worked in a world where the interaction was I had a human that wrote code and developed products, and I had another human that I wanted to help embed next to that one to help them better understand the security.
00:12:47.919 --> 00:13:07.919
In a world where the human now interacts with agents and um they have agent skills and workflows and all these other things that are that are actually having a even more impact on what code and security implementations are being built.
00:13:08.159 --> 00:13:10.960
I think the dynamic changes, right?
00:13:11.200 --> 00:13:15.200
Because it's no longer about just evangelizing the human.
00:13:15.279 --> 00:13:17.600
There's a new player on the field, right?
00:13:17.840 --> 00:13:30.559
It's a lot of the code quality has gone from human education gaps to how do I influence an agent and a human working together, right?
00:13:30.720 --> 00:13:38.399
There's a new, it's how do I influence that relationship that is being used to build a product?
00:13:38.559 --> 00:13:39.840
Because that's what the new world is.
00:13:39.919 --> 00:13:42.799
It's not human writing code, it's not even agent writing code.
00:13:43.039 --> 00:13:51.120
Because I mean, unless
you're on like one of these austere like campaigns where Anthropic says agents just write all our product and we don't look at it, like, I don't know.
00:13:51.519 --> 00:13:52.240
Right, okay.
00:13:52.399 --> 00:13:54.639
But that's not the way 99% of the world's gonna work.
00:13:54.720 --> 00:13:57.759
And I highly don't recommend that's the way anybody that we know works.
00:13:58.000 --> 00:14:10.000
But you now have this dynamic of a human and agent that are working together in parallel to accomplish a task and goal, and along the way, code's getting written, right?
00:14:10.159 --> 00:14:13.440
And that's that it's more I like people call intent development.
00:14:13.519 --> 00:14:15.279
I don't call intent development.
00:14:15.360 --> 00:14:19.600
It's it's it's a it's human-agent relationship development, right?
00:14:19.759 --> 00:14:29.440
It's and the way we affect the code quality isn't by necessarily finding tools that just affect the agent, and it's not just by educating and empowering the individual.
00:14:29.759 --> 00:14:41.679
You have to, you have to actually tackle the relationship between the agent and the human to affect the quality of the code being written, right?
00:14:41.840 --> 00:14:45.200
And so, what's the role of a champion in that dynamic, right?
00:14:45.360 --> 00:14:47.519
It it I think it completely changes, right?
00:14:47.600 --> 00:14:51.120
Uh like, does the same tactics we use before work?
00:14:51.279 --> 00:14:54.480
And I'm I'm saying this out of the side of like, I don't know the answer to these.
00:14:54.639 --> 00:15:01.120
This is kind of the emergent thought of this, but that does I'm guessing a lunch in learning isn't going to solve our problems here, right?
00:15:01.200 --> 00:15:02.879
That's a human dynamic, a tackle.
00:15:02.960 --> 00:15:06.000
That's where we all our champion effort was before.
00:15:06.320 --> 00:15:16.320
So I think the the the real question is, right, how do we redefine champions in a world where they have to influence more than the humans to be effective?
00:15:17.360 --> 00:15:21.360
Yeah, and you made a great point there from one, that relationship coming together.
00:15:21.440 --> 00:15:28.080
And I think of it now, and especially in the last six months, where we see a lot of these frontier models that are pretty good.
00:15:28.240 --> 00:15:34.320
Like at the end of the day, you can be a naysayer, you can have your opinions, but can't really argue at some of the results.
00:15:34.399 --> 00:15:44.879
And it's just really driving up a lot of new issues and you know, rising those to the surface, which brings in a security champion even more responsibility.
00:15:45.120 --> 00:15:48.639
But it also code is now just commoditized.
00:15:48.799 --> 00:15:59.759
You have an intent, you have an architecture, and the real security is around those not only agent-to-human relationships, but agent-to-agent and MCP.
00:16:00.000 --> 00:16:03.600
So it's kind of taking on, as
I was saying, a broader role.
00:16:03.840 --> 00:16:14.879
And personally, I think it needs to, we need to keep that same, you know, evangelize, enable, and recognize the people in the organization that are doing this great work.
00:16:15.039 --> 00:16:24.399
It's just that the game board has changed, the pieces have changed, but the core values and the core end like mission is still, still the same.
00:16:24.559 --> 00:16:27.600
Like we want to champion that security throughout.
00:16:27.840 --> 00:16:32.720
Because one of the biggest concerns I have now is really the velocity of code.
00:16:32.960 --> 00:16:40.639
Like, you know, I mean, if you have agents running or like you get rid of your whole dev team, this happens near instantaneously.
00:16:40.879 --> 00:16:44.879
And then you even push to, you know, prod without human oversight.
00:16:44.960 --> 00:16:59.440
Like, so this velocity is really going to bring a whole new, I'm not going to say burden, but a whole new bag for that security champion to carry and to carry for the organization and the new members of the team.
00:16:59.679 --> 00:17:13.279
So question to you is of all the conversations you've had, you know, from security champions to people in the industry that are kind of making that shift, maybe development teams aren't as built up.
00:17:13.680 --> 00:17:23.440
What do you feel that relationship and that responsibility of the ski security champion moving into a more strategic or architectural role?
00:17:23.599 --> 00:17:30.480
Or do you think they still need to be embedded on those small teams, you know, as they have been in the past?
00:17:31.039 --> 00:17:37.680
Yeah, I guess the the real world answer now goes back to, and I it's the same question I ask companies, right?
00:17:37.920 --> 00:17:43.359
When I come in and they're the company's like, I want to start a champion program, or I am running a champion program.
00:17:43.680 --> 00:17:45.599
Um, my first question is great.
00:17:45.920 --> 00:17:48.160
What is your end state goal?
00:17:48.319 --> 00:17:50.799
Like what's your what's your what's your business mission?
00:17:50.960 --> 00:17:52.559
What's your mission statement?
00:17:52.880 --> 00:17:58.720
What is the metrics that you're using to measure the impact that your champions are having?
00:17:59.039 --> 00:18:03.920
Um quite often it's I don't know, champions are showing up.
00:18:04.079 --> 00:18:08.559
Um interestingly, it's it's it's the same kind of actually conversation I'm having around of like AI, right?
00:18:08.640 --> 00:18:11.680
So I'll translate this to a lot of things I've been talking about recently.
00:18:11.839 --> 00:18:18.160
Um, a lot of companies I'm talking about with, they're like, oh, like what's what is my new title, VP of AI Enablement.
00:18:18.240 --> 00:18:21.279
What is or what are you doing in your organization for enablement, right?
00:18:21.759 --> 00:18:27.440
And the first response I get from company is, well, we bought a
bunch of people licenses and they have access to cloud.
00:18:27.680 --> 00:18:30.160
I'm like, that's cool, right?
00:18:30.400 --> 00:18:33.839
You've just explained to me what you're spending on AI.
00:18:34.079 --> 00:18:36.559
You didn't tell me what you're getting out of AI.
00:18:36.640 --> 00:18:41.279
You didn't tell me how you're preparing your workforce to use AI, right?
00:18:41.599 --> 00:18:45.680
Now we go back to the same transition lens of what a champion is, right?
00:18:45.839 --> 00:18:49.359
And quite often we run into this idea of, well, what is your champion program?
00:18:49.519 --> 00:18:52.240
Like, oh, well, I have this many champions.
00:18:52.400 --> 00:18:54.240
We do lunch and learns.
00:18:54.480 --> 00:18:59.519
Um, I uh I like, like, like I've I've I've enabled them and I've bought training for them.
00:18:59.599 --> 00:19:00.799
I'm like, that's great.
00:19:01.440 --> 00:19:11.920
You've told me all the money you're spending on your champions and the time they're giving up, but you still haven't translated to the impact you're measuring and hoping to get out of these champions.
00:19:12.079 --> 00:19:17.039
And a lot of time that's because that people are going, well, I know I need a champion program, it's the right thing.
00:19:17.200 --> 00:19:18.880
I think culture is important.
00:19:19.039 --> 00:19:25.759
I like the idea of being a force multiplier, but they still don't have the end state goal in mind.
00:19:25.920 --> 00:19:38.000
So when we rethink about the impact that we're having with our current champion audience and how how what our devs are doing are changing, maybe it's a question of what's the impact that we want the champions to have, right?
00:19:38.559 --> 00:19:41.839
Is the goal still to educate securely?
00:19:41.920 --> 00:19:53.119
And then maybe if that is the same goal, if we don't change, like if we look at the lens of maybe we don't change the approach, but we change the focus, that's where we get affected, right?
00:19:53.200 --> 00:19:58.319
So the champions are still educating and there to be, have the right answers.
00:19:58.480 --> 00:20:02.000
But now what we prepare the champion with has to change.
00:20:02.160 --> 00:20:12.400
Because before I teach them SQL injection, I teach them secure design and secure coding principles and these showing them how attacks can happen, right?
00:20:12.559 --> 00:20:14.319
Have that attacker mindset.
00:20:14.799 --> 00:20:22.319
But when the devs not writing the tool, I'm pretty sure that the lecture on concatenating strings is not going to fall dead.
00:20:22.559 --> 00:20:32.400
But maybe, maybe if we just now empower them with, hey, by the way, this is what a new secure development lifecycle looks like in an era of AI.
00:20:32.480 --> 00:20:38.720
And by the way, I've seen a bunch of little pop-ups of what people kind of say they think the new SDLC is with AI is.
00:20:38.880 --> 00:20:39.680
And guess what?
00:20:39.839 --> 00:20:40.799
None of them are right.
00:20:41.039 --> 00:20:43.519
All of them are useful, kind of like the way we think of models, right?
00:20:43.599 --> 00:20:44.480
Threat model, yeah, yeah.
00:20:44.640 --> 00:20:46.319
They're all they're all wrong, but they're all useful.
00:20:46.480 --> 00:20:48.640
Like anytime you represent it, represent anything.
00:20:48.799 --> 00:20:54.240
These new SDLCs are the same, and no one's unified the way that we did on the traditional SDLC, right?
00:20:54.640 --> 00:21:00.079
Um, because the way that people are using these tools, I haven't seen two companies that code the same, right?
00:21:00.240 --> 00:21:03.839
Like it's it's it's completely different now, right?
00:21:04.160 --> 00:21:17.519
So when we think about the the idea of the the champions, before I would say this to companies what your champions do in your organization is 100% dependent on what's important to your organization, right?
00:21:17.680 --> 00:21:19.200
What's your business uh model?
00:21:19.440 --> 00:21:27.519
How do you operate, and how can you make sure that what you're asking the champions to do are aligned to what your business is trying to achieve?
00:21:27.759 --> 00:21:29.200
Um, that was what we did.
00:21:29.279 --> 00:21:33.759
And that means what champions did from organization to organization were just different, right?
00:21:34.079 --> 00:21:43.680
Some people were literally like pair coders that were like part of the app sec team that did heavy, they set the SaaS tools and did the security scanning and threat modeling and a bunch of this stuff.
00:21:43.759 --> 00:21:49.920
I had other ones that were like, Oh, I just get some edu extra education sometimes and talk about security on a stand up every now and then, right?
00:21:50.079 --> 00:21:59.599
And for that organization, that might be the fit in this world where the the sprawl of the way people are writing software and leveraging these tools and different approaches.
00:22:00.160 --> 00:22:04.640
And by the way, every company thinks they have the most novel new approach to using AI to write code.
00:22:04.880 --> 00:22:05.839
Should see what we're doing.
00:22:05.920 --> 00:22:06.640
It's completely different.
00:22:06.799 --> 00:22:07.519
Well, yeah, all right.
00:22:07.599 --> 00:22:11.599
It's probably not that different to how another couple other dozen companies are thinking about doing it too.
00:22:11.680 --> 00:22:14.799
Just nobody's talking about it because they all think they got some big, great secret.
00:22:15.039 --> 00:22:17.440
Uh eventually in a couple of years, that'll die down.
00:22:17.599 --> 00:22:23.519
But that does mean that everyone's doing stuff a little bit different right now from kind of everyone else for a lot of the ways.
00:22:23.680 --> 00:22:31.759
So what your champions are going to do is gonna have to be completely aligned to the new way and workflow you're trying to do and the impact you're trying to have.
00:22:32.079 --> 00:22:32.400
Yeah.
00:22:32.480 --> 00:22:45.599
And even within like this modern champion that we're talking about, like they will continue and always be that secure code advocate, that overarching kind of signal to the team with that security focus.
00:22:45.839 --> 00:22:50.480
But now we're gonna ask them to, you know, be a workflow guide.
00:22:50.640 --> 00:23:03.920
They're gonna have to help people set up workflows, they're gonna have to do risk and risk signaling of different developers, as well as the organization as a whole, and then even serve as that, as I was saying, secure code advocate.
00:23:04.079 --> 00:23:07.359
Like you have to have someone look at the code before it goes through.
00:23:07.440 --> 00:23:08.720
Even I mean, no matter what.
00:23:08.880 --> 00:23:20.960
So they're gonna need engineering, product, data, like all these different fields and learnings all coming together to be able to be the best, you know, modern security champion that they can be.
00:23:21.119 --> 00:23:24.319
And then we got to throw in governance and compliance into that as well.
00:23:24.480 --> 00:23:28.319
Is like, do you think that should fall on, you know, a security champion?
00:23:29.119 --> 00:23:36.079
No and yes, but I think they should drive it, you know, and I I think that's what it really comes down to, and you hit the nail on the head.
00:23:36.400 --> 00:23:39.839
This role will differ between each organization.
00:23:40.240 --> 00:23:45.759
Each organization's in a different industry, different sector, different needs, and a different stage of maturity.
00:23:45.920 --> 00:24:20.720
So that's really what I wanted to kind of take this modern security champion term and approach and take these episodes in a in a broader direction where we're gonna look at those operations, those, you know, AI risk signals, those workflow guides, and bring in all these different aspects to really empower this modern security champion and hopefully security champion teams, where there's a group of people for these larger organizations to be able to influence it securely and not just throw it to the machines and because it goes quick and we can't find anything, it's good to go.
00:24:21.039 --> 00:24:32.960
It's just be machine on machine, and that's not the best future in my mind for both secure coding, especially as all of this code kind of comes into the physical world more and more.
00:24:33.519 --> 00:24:34.400
What are you talking about, man?
00:24:34.480 --> 00:24:35.920
I just have copilot review.
00:24:36.000 --> 00:24:36.960
This little button, right?
00:24:37.039 --> 00:24:39.920
I do a PR, it says copilot, we'll do my review, we're done.
00:24:40.400 --> 00:24:45.200
AI generated the code, AI reviewed it, I had AI host it and do the PR for me.
00:24:45.359 --> 00:24:47.839
Like I I don't even know why we have people anymore.
00:24:47.920 --> 00:24:50.400
Like we're kind of becoming obsolete as a product.
00:24:50.720 --> 00:24:59.759
Yeah, you just put
the effort to you know extra high, and that that'll make sure that everything, everything's good except, you know, your token cost at the end of the month when you get that bill.
00:24:59.839 --> 00:25:00.799
But okay.
00:25:00.880 --> 00:25:02.559
So so here's my proposal.
00:25:02.640 --> 00:25:04.400
We're gonna solve all the world's problems right now.
00:25:04.640 --> 00:25:06.480
All right, so here's what we're gonna do.
00:25:06.640 --> 00:25:10.640
I'm going to write a AI champion agent.
00:25:10.880 --> 00:25:20.640
I'm gonna hook it up to an MCP, and I'm just gonna I'm gonna put it directly to, I don't know, what would be a good connection there?
00:25:20.720 --> 00:25:28.000
Uh I'm gonna just I'm just gonna hook it up to all the clawed, open AI, I don't know, it's something.
00:25:28.079 --> 00:25:31.359
I'm gonna give it all the the good code and guidance and call it done, right?
00:25:31.680 --> 00:25:34.400
So, so interestingly, here as we think about this, right?
00:25:34.480 --> 00:25:36.400
I I'm talking facetiously, right?
00:25:36.480 --> 00:25:39.599
I'm joking here, but but realistically, right?
00:25:39.920 --> 00:25:50.799
Like in a world of AI enablement and AI first companies, and apparently AI is solving all our problems or making all of them, it's kind of hard to decide one day.
00:25:51.039 --> 00:25:56.079
Um, why why can't we just have an AI agent that's our champion, right?
00:25:56.160 --> 00:25:58.480
It's your secure coding co-pilot, right?
00:25:58.640 --> 00:26:06.000
And I I I've I've heard people, I've seen, I've looked at the LinkedIn's and a million other people building the the secure coding co-pilot or whatever it is.
00:26:06.240 --> 00:26:12.640
Like, I will say this code quality is going like interestingly, is going to change.
00:26:12.880 --> 00:26:16.720
Now, I didn't say better or worse because I don't know yet, right?
00:26:16.880 --> 00:26:20.319
We talk about these new like modern models like Fable.
00:26:20.720 --> 00:26:23.680
I've played with Fable, it's impressive.
00:26:23.839 --> 00:26:25.279
I'm gonna admit it, right?
00:26:25.519 --> 00:26:29.519
Yeah, don't ask anything about security or anything of that, and you'll just kind of get bumped off.
00:26:29.599 --> 00:26:30.240
But downgrades.
00:26:30.880 --> 00:26:42.559
Interestingly, you know, I saw a LinkedIn post, I was literally reading it today, and some guys like, I've hacked the way to bypass Fable's not more responsive security, and then just do this, and it'll answer your security questions, right?
00:26:42.720 --> 00:26:47.119
By the way, all these guardrails on AI, you can't guardrail AI.
00:26:47.200 --> 00:26:49.519
Like it just that's just not the way it works well.
00:26:49.599 --> 00:26:53.839
Like you can get like you can keep low stuff, but there's always gonna be failure points, right?
00:26:54.000 --> 00:26:55.759
But also, let me throw out this though.
00:26:55.839 --> 00:27:02.240
I don't know the last time anyone here's actually ran a task on Fable and looked at the dollar signs that comes behind that.
00:27:02.880 --> 00:27:08.559
But just because there's a powerful model does not mean I'm gonna have it doing my security reviews for me.
00:27:08.799 --> 00:27:17.759
Um, when when the model becomes more than the hourly wage I'm paying the person to write the code, at some point it starts getting ridiculous, right?
00:27:18.000 --> 00:27:23.440
You start having a hard time proving that I'm generating value versus all the cost I'm throwing out of this.
00:27:23.759 --> 00:27:24.000
Yeah.
00:27:24.160 --> 00:27:31.200
And my first claim, first podcast claim, is that that is gonna work like every other subscription model in the past.
00:27:31.359 --> 00:27:41.279
And those token costs are gonna continually increase, increase until you you hit that point that some of these large companies, you know, start losing customers because of that cost.
00:27:41.440 --> 00:27:45.440
So I think that's gonna continue to go up and up, at least for the foreseeable future.
00:27:45.839 --> 00:27:48.319
Well, you think about that too, though, and it goes back to this AI.
00:27:48.400 --> 00:28:03.119
So I I do think champions are like interestingly enough, I like the joke of an A champion agent isn't crazily far-fetched for maybe a tool that you get champions to use, right?
00:28:03.279 --> 00:28:09.279
Like, say you have internal policy and secure code practices and things you want your company to follow.
00:28:09.519 --> 00:28:15.920
There's no reason you can augment an agent with that data that could support your dev teams, right?
00:28:16.240 --> 00:28:18.400
Um, because here's what here's the problem, though.
00:28:18.480 --> 00:28:21.200
Here's what everyone's expecting, and here's where they're gonna run into the issue.
00:28:21.440 --> 00:28:26.480
They're hoping the foundational models will save solve all their problems, right?
00:28:26.720 --> 00:28:28.720
Eventually Cloud will be good enough.
00:28:28.960 --> 00:28:34.559
Eventually, Codecs will be good enough, eventually I'll be able to use curse or any of these things, right?
00:28:34.640 --> 00:28:36.240
And it'll be good enough, right?
00:28:36.480 --> 00:28:38.559
Um, copilot, whatever.
00:28:38.880 --> 00:28:45.359
But the problem is they're generalistic tools, right?
00:28:46.079 --> 00:28:48.400
They're meant for like they have the coding ones, right?
00:28:48.559 --> 00:28:54.400
You have your codecs or clawed code, but even so, like the companies are moving away from them being just coding tools.
00:28:54.480 --> 00:28:56.400
I don't know if you know like OpenAI, right?
00:28:56.559 --> 00:29:00.079
They put they have a new work tab, right, in your chat.
00:29:00.160 --> 00:29:10.319
And if you can go on chat or work, if you go to work, surprise, it's just codecs under the hood that they're now feeding to the workers to be able to do agentic work, right?
00:29:10.480 --> 00:29:12.160
It's just codecs,
right?
00:29:12.319 --> 00:29:15.359
It's just now been reframed as an engine to help them.
00:29:15.440 --> 00:29:17.279
Now don't quote me on that on specificity.
00:29:17.359 --> 00:29:19.920
Like I I heard it's a go-to-market person explaining it before.
00:29:20.000 --> 00:29:23.759
I just want to so if I'm a little inaccurate in the way you described that, like don't hold me to it.
00:29:23.920 --> 00:29:28.400
But but the reality of the way it was explained to me is it's just codecs under the hood, right?
00:29:28.880 --> 00:29:30.960
So when when this all changes, right?
00:29:31.039 --> 00:29:32.319
And that this is actually an interesting part.
00:29:32.400 --> 00:29:34.160
When we think about champions, right?
00:29:34.400 --> 00:29:38.720
Um, the ch traditional champion, you're talking about looking to the future, it changing.
00:29:38.960 --> 00:29:41.599
Um we've thought about just devs.
00:29:42.000 --> 00:29:50.720
I've always touched on, I even did an episode once with somebody that helped write the top 10 threats for low-code, no code, right?
00:29:50.799 --> 00:29:54.960
I remember that being a great episode and the person that runs that OAS project.
00:29:55.119 --> 00:30:02.720
Um, with the fact that citizen developers are a massive threat landscape and probably need the most championing um to be able to be effective.
00:30:02.799 --> 00:30:05.279
But now we have these AI citizen developers, right?
00:30:05.440 --> 00:30:18.240
Um, I'm interested to see how do you tap into that world and do you start finding citizen developers that are not necessarily like they don't understand code.
00:30:18.480 --> 00:30:25.039
I think in the new world, if you're gonna have that ecosystem, you're gonna have to find security champions in that group too.
00:30:25.359 --> 00:30:50.640
Interestingly enough, you might even find, and I say this like maybe incorrectly, but I might I have a weird feeling, you might find better, more passionate champions in the workforce than you would in the developer audience, the knowledge workers, because you have a lot of people that are really excited and passionate about the power of the tool they've gotten access to and they're hungry to learn.
00:30:50.880 --> 00:31:01.839
Where I will say a lot of the developers, like they're great, they're highly educated, and sometimes it's just harder to get them to care about security, just because it just is.
00:31:01.920 --> 00:31:03.119
It's just the nature of the beast.
00:31:03.200 --> 00:31:11.200
And if like I I've always been passionate that that's not a developer problem, that's a we're not reaching the developer the right way problem, that's a security team problem.
00:31:11.359 --> 00:31:15.039
Um, but the reality is it's just harder, it's just a harder problem to solve.
00:31:15.119 --> 00:31:20.160
And it might not be for the knowledge workers, especially right now, because everyone's so hungry to learn.
00:31:20.319 --> 00:31:29.839
Like this, I feel like
this is a perfect time to branch out to that audience and get as many champions as you can to embed with these new people that are using AI to write code that aren't devs.
00:31:30.880 --> 00:31:31.279
Yeah.
00:31:31.440 --> 00:31:36.000
And I I love talking and arguing with you and especially being right.
00:31:36.240 --> 00:31:49.200
But what you just did was you took my kind of perception of now the security champion is going to be in charge of all of these different aspects and coming together because that's what a security champion does.
00:31:49.359 --> 00:31:55.519
But I love what you just said about the empowerment to the rest of the organization and really what it comes down to.
00:31:55.599 --> 00:32:03.680
It's that hunger to learn and to continuously learn, as well as, you know, that desire and your own perspective of where you're coming from.
00:32:03.920 --> 00:32:15.839
So I I'm definitely gonna take that into the future, especially with some of our guests, on how more people can be security champions beyond just your dev team, your CS majors.
00:32:16.000 --> 00:32:23.279
And that that's a really great point to bring up because I think we're gonna see that very, very soon and love to hear more thoughts on that later.
00:32:23.359 --> 00:32:24.480
But that's really cool.
00:32:24.880 --> 00:32:26.240
Well, I think it directly aligns.
00:32:26.400 --> 00:32:28.079
Uh, I our CEO said this before.
00:32:28.160 --> 00:32:29.680
I'm stealing his quote here.
00:32:30.079 --> 00:32:43.119
Um not everyone's a coder anymore, but everyone has the power to be a developer because they asked have access to tools that can help them build software and well.
00:32:43.680 --> 00:32:47.359
Now, I didn't say good or bad or secure or insecure, right?
00:32:47.519 --> 00:32:50.640
Just the de facto you are because you have the capability.
00:32:50.799 --> 00:32:56.319
Whether you're doing that well or securely, yeah, that's a whole nother argument and string to pull on, right?
00:32:56.720 --> 00:33:01.440
Um, but that broadens our case that broadens our need for bigger champion programs, I think.
00:33:01.599 --> 00:33:13.200
I think that's so I'm very excited to see the the new angles you get to bring into this conversation and the people you get to bring in in this kind of new era, right?
00:33:14.240 --> 00:33:19.519
Um I'm gonna I'm gonna ping you on this, right?
00:33:19.599 --> 00:33:26.960
So what are you what like doing this transition, doing this handover, um what's your vision of the future for this?
00:33:27.119 --> 00:33:29.680
Like what's like you start touching, you're gonna broaden, right?
00:33:29.759 --> 00:33:38.960
You're gonna broaden, you're bringing some more people, you're gonna see some perspectives on technologies or areas that we just never touched on before, which I think is gonna be fresh, right?
00:33:39.039 --> 00:33:43.839
Something completely new, some some reason to come back instead of just hearing Mike talk about the
same stuff every time, right?
00:33:43.920 --> 00:33:45.200
I think I'm excited for that, right?
00:33:45.279 --> 00:33:48.000
Now you get to hear another Mike talk about something new this time.
00:33:48.799 --> 00:33:50.160
Really switching it up, yeah.
00:33:50.400 --> 00:33:52.480
Really, really changing things up here, right?
00:33:53.519 --> 00:34:00.319
Um but uh so but what do you see that future as for where where you're taking the direction of this?
00:34:01.119 --> 00:34:10.400
I really see it being an outreach, as you were saying, to all these different sectors, all these different teams within the organizations.
00:34:10.559 --> 00:34:27.039
Because now that everyone's a coder, now that code is commoditized and it can be thrown in all different directions into any product with the velocity to get that product into market, no matter what sector you're in, things are gonna be different.
00:34:27.280 --> 00:34:57.360
A lot of the same vulnerabilities will be the same, a lot of the different security champions' responsibilities will be similar, but we're gonna take all these different perspectives from, you know, we can we're gonna start talking, you know, robotics and then into satellite security, where the security champion is completely embedded throughout, you know, the entire development phase, the testing, all the things that go into, you know, satellite engineering, facing against radiation.
00:34:57.519 --> 00:35:04.559
But then once all that is done, the security champion did a great job, the team, it's launched and now it's in space.
00:35:04.880 --> 00:35:06.480
You can't update anything.
00:35:06.719 --> 00:35:10.800
You, you know, it takes a little bit more, there's FPGAs and different steps like that.
00:35:10.880 --> 00:35:22.800
But these are long-lived systems that are going to continuously operate with really out the ability to give updates and patch, and now they're all moving around and they're like chasing each other now.
00:35:22.880 --> 00:35:39.519
But that's just one example of that perspective on how this specific aerospace industry is gonna treat security champions completely different than from a drone perspective or an app sec, you know, perspective, which we'll always touch on as well.
00:35:39.760 --> 00:35:56.559
But just bringing in those different views, I think, will really be able to give the listener the ability to take that from something they would never have, you know, experience in or access to and bring in those lessons to their own team and their own organization.
00:35:56.880 --> 00:36:16.320
So it's going to be really about connecting that cybersecurity risk to the human, that security champion and security champion teams, to then be able to provide, you know, all the security features needed for that product, as well as experiment and drive the security as it happens.
00:36:16.480 --> 00:36:18.239
Because I keep going back into it.
00:36:18.400 --> 00:36:21.280
The velocity of this is pretty
mind-blowing to me.
00:36:21.360 --> 00:36:30.960
That you can, you know, have code pushed to prod automatically in seconds, no matter what, which probably leads to some of the outages we've seen in the recent past.
00:36:31.119 --> 00:36:43.519
But again, the speed is what I want to concentrate on and taking all those perspectives and bringing it back into the security champion because they're not just, you know, helping the product or the business.
00:36:43.679 --> 00:36:48.639
They're they're really helping everyone as all these new systems start interconnecting.
00:36:48.800 --> 00:36:53.199
You know, we'll move into telecom a little bit, 6G, AI ran.
00:36:53.519 --> 00:36:53.760
Yeah.
00:36:53.840 --> 00:36:57.280
So now we have AI attached to cell phone towers.
00:36:57.360 --> 00:36:59.760
You know, there's there's a lot of different things going on.
00:36:59.840 --> 00:37:15.360
And I think just being at that cutting edge, bringing in all these experts who are security champions in their fields, is gonna give the listener a more broad understanding and be able to have them continuously learn and drive their own experience.
00:37:17.519 --> 00:37:18.239
That's amazing.
00:37:18.480 --> 00:37:20.159
Yeah, well, you beat me to the draw on that one.
00:37:20.239 --> 00:37:37.039
I was gonna ping you on um from all the episodes you've done, from you know where you and Chris started to where you've brought it to now, what would you like to see actually be carried for, you know, carried forward and continually going along with this podcast?
00:37:37.199 --> 00:37:45.360
Because as I've said, I have my own opinions, my own perspective on how this will be so valuable, but what would you like to see kind of carry through?
00:37:45.679 --> 00:37:46.000
You know what?
00:37:46.159 --> 00:37:48.639
I think the most interesting, and I love the freshness, right?
00:37:48.719 --> 00:37:55.599
The idea is that you'll be hitting on tech and topics, I think, that were just gonna be interesting for people to understand.
00:37:55.679 --> 00:37:59.199
I think I'll always have a focus back to like, like how does this apply to me?
00:37:59.280 --> 00:38:02.639
But it's but it's new, it's a new perspective, new problems.
00:38:02.800 --> 00:38:04.639
That's that's that's a really exciting.
00:38:04.800 --> 00:38:10.239
Um my my only hope is that I continue you see passionate people come share passionate stories, right?
00:38:10.320 --> 00:38:17.679
I think as long as you we have that coming into this environment, um, I think it's be value and it's gonna be great to listen to.
00:38:17.840 --> 00:38:19.440
Um, I I'm excited about it.
00:38:19.519 --> 00:38:23.920
I'm excited to see who you get to kind of bring in and the type of conversations you're gonna be having.
00:38:24.079 --> 00:38:25.920
Um, because once again, something fresh.
00:38:26.000 --> 00:38:28.719
We've been doing one approach for for a while.
00:38:28.880 --> 00:38:35.199
Um really excited to see what what what you what you're gonna bring to the table and how you're gonna change it up for sure.
00:38:35.519 --> 00:38:38.000
Um other interesting thought too, right?
00:38:38.079 --> 00:38:43.280
And and as we're kind of kind of talking through this, I'm gonna do my pitch of why I'm leaving, right?
00:38:43.440 --> 00:38:48.639
So, so I mentioned that I moved in as the VP of AI enablement acceleration here, right?
00:38:48.719 --> 00:38:50.960
And what's what's that actually mean?
00:38:51.199 --> 00:38:56.400
And what what that actually means is I'm leaving the lens of just developers.
00:38:57.199 --> 00:38:59.599
AI, just what you brought up the citizen developers, right?
00:38:59.760 --> 00:39:01.440
That like as a new problem, right?
00:39:02.079 --> 00:39:13.599
The workforce has been given access to one of the most powerful generative tools on their everyday life.
00:39:14.239 --> 00:39:24.000
And the honest reality is 99% of them are using it to write fancy emails or make a nice PowerPoint deck.
00:39:24.719 --> 00:39:34.800
And and companies are struggling with proving ROI or value or what are we getting out of this, right?
00:39:34.960 --> 00:39:42.480
Um, because I'm gonna tell you right now, a fast written email or a fancy PowerPoint, 99% of the time isn't gonna lead to revenue, right?
00:39:42.719 --> 00:39:45.119
It's gonna reduce the work, right?
00:39:45.199 --> 00:39:47.280
It may feel easier for me to do.
00:39:47.440 --> 00:39:54.559
But here's the reality: if a PowerPoint was gonna take me five hours to make and I got AI to make it in like 10, that's great.
00:39:54.639 --> 00:39:58.079
But the reality is I probably wasn't gonna spend the five hours to make that PowerPoint.
00:39:58.320 --> 00:40:01.440
So did I gain, did I, did I really gain the value there?
00:40:01.519 --> 00:40:02.880
Unless I absolutely had to, right?
00:40:02.960 --> 00:40:09.840
It's gonna get for a few people, but most people would have just done a lower quality one for less time and accomplished the goal, right?
00:40:10.079 --> 00:40:15.119
So tying that type of change in work is it doesn't show value, right?
00:40:15.280 --> 00:40:20.480
What we have to do is we have to rethink what a workflow is.
00:40:20.719 --> 00:40:26.480
How do I go from point A to point B in my company where I have a signal I have to do work to the work is done?
00:40:26.639 --> 00:40:35.039
Developer word is feature request to delivering a feature in production that people are using, all the steps and things that went along the way, right?
00:40:35.199 --> 00:40:53.920
You have your ticket creation, you have your validating the ticket, you have uh a proposal and a breakdown, a meeting with the customer to align on the objectives, and then you take that same workflow, and all of a sudden you have to break it out into subtickets and do sprints on it and QA and deliveries and feedback on the feature.
00:40:54.079 --> 00:40:56.639
Like there's this whole workflow,
right?
00:40:56.960 --> 00:41:03.840
Being able to look at that workflow and optimize where AI fits in the best to generate real repeatable revenue.
00:41:03.920 --> 00:41:18.159
And by the way, not just looking at the workflow and adding AI in, but realizing you have a new capability and restructuring the workflow around that capability to optimize the revenue it generates.
00:41:18.559 --> 00:41:20.800
That's a way that most companies are struggling.
00:41:20.880 --> 00:41:21.679
They're the experiment.
00:41:21.760 --> 00:41:24.960
We bought licenses and everybody's just using AI.
00:41:25.360 --> 00:41:51.760
No, very, very few people are optimizing and rethinking their workflows and enabling everyone from Susie at HR all the way to sales, RevOps, like marketing, to be AI literate, AI capable, and generating value and solving business problems with AI rather than writing fancy emails, right?
00:41:51.920 --> 00:41:53.679
And that's where my entire focus is.
00:41:53.760 --> 00:42:24.480
And interestingly enough, um, we've launched an entire new part of the product and security journey that is just for that audience to solve that problem, to educate, enable and empower the workforce to become AI first capable workforce, to be to be on the frontier and able to leverage this tool that they have to generate revenue, value, and expand their capabilities in ways that they never thought possible.
00:42:24.719 --> 00:42:29.360
And that's where my entire new world focus is helping drive that lead.
00:42:29.599 --> 00:42:31.039
Um, but it's interesting, right?
00:42:31.119 --> 00:42:34.719
It's parallel because here's the part about that I think that we uniquely sit, right?
00:42:34.960 --> 00:42:40.320
Think about the idea of the security champion is with all that comes so much risk.
00:42:40.559 --> 00:42:46.159
So when can we at the moment we teach people and empower them to do this work?
00:42:46.480 --> 00:42:50.480
Can we just teach them, empower them to do it safely and right the first time?
00:42:50.719 --> 00:43:00.800
So, unlike the dev world where we basically have spent everyone teaching them capability and at the end, when they get to companies, try to patch on some security so we quit getting in trouble.
00:43:00.960 --> 00:43:06.239
Well, like, how about when I first time I teach you to use AI along the way?
00:43:06.480 --> 00:43:08.400
I I teach you where it fails.
00:43:08.559 --> 00:43:20.559
I teach you how the the vulnerabilities, so that when I call you AI capable, when I call you an AI first company, the security is just a de facto part of the way you do it.
00:43:20.719 --> 00:43:22.880
And it's not something we have to call out separate.
00:43:22.960 --> 00:43:26.559
It just is because it's not right if it's not secure.
00:43:26.880 --> 00:43:27.119
Yeah.
00:43:27.280 --> 00:43:30.400
And with AI, that that's so important now.
00:43:31.599 --> 00:43:34.960
I mean, it's probably how it always should have been.
00:43:35.119 --> 00:43:40.159
Um, but as you said, with AI now, it's it's kind of changed the playing field.
00:43:40.239 --> 00:43:44.079
And out of principle, I write all my emails myself.
00:43:44.320 --> 00:43:45.519
That is just for me.
00:43:45.679 --> 00:43:50.800
I know other people do it, but it's good to keep some human-to-human interaction.
00:43:50.880 --> 00:43:58.639
Like, and humans are really good at seeing what has been AI tweaked or recognizing those patterns within the system.
00:43:58.880 --> 00:44:02.480
But that's a question I'm going to be asking every single one of our guests.
00:44:02.639 --> 00:44:09.440
Like optimizing revenue, great for CEOs and shareholders, but it's about optimizing your workflow.
00:44:09.679 --> 00:44:28.079
So we'll be asking that to every guest and their discipline and what they have to deal with and what things were really helped by, you know, getting some AI involved, speeding up this process that allows you to use your own expertise in learning to concentrate on what matters in this piece.
00:44:28.239 --> 00:44:34.239
So it'll be a lot about optimizing that workflow throughout their individual experience and companies.
00:44:34.400 --> 00:44:35.840
So thanks for that one.
00:44:36.000 --> 00:44:37.199
I just came up with that there.
00:44:37.280 --> 00:44:39.360
That that'll be every question, every guess.
00:44:39.519 --> 00:44:56.159
So no, that's appreciate all that and all the stuff you're doing for AI enablement and really helping these organizations adopt it safely, securely, and so their whole, you know, life is more efficient to concentrate on things that matter.
00:44:57.280 --> 00:44:57.519
Yeah.
00:44:57.599 --> 00:45:00.960
And hey, Mike, I am so excited because I I think we're coming near the end.
00:45:01.039 --> 00:45:01.760
I've told the story.
00:45:01.840 --> 00:45:02.719
We're doing the handoff.
00:45:02.800 --> 00:45:04.079
We know what you're doing in the future.
00:45:04.159 --> 00:45:05.599
We know why I'm leaving.
00:45:05.920 --> 00:45:10.800
Um, this is, like I said, this is this has been such a passion project.
00:45:10.960 --> 00:45:11.679
No pressure.
00:45:11.920 --> 00:45:12.960
No pressure, right?
00:45:13.840 --> 00:45:17.599
Handing off the podcast, allow you to take the take the wheel.
00:45:17.760 --> 00:45:19.519
Uh don't mess it up.
00:45:19.679 --> 00:45:24.320
Uh I have every confidence in you that you're gonna, this is gonna be great.
00:45:24.400 --> 00:45:26.000
And by the way, I'm gonna be around.
00:45:26.159 --> 00:45:28.880
There's definitely times I probably come in and we talk again, right?
00:45:29.039 --> 00:45:32.079
Just uh that that'll be your driver now versus my driver.
00:45:32.320 --> 00:45:42.159
Yeah, I'll definitely drag you back in, especially on as we kind of develop, you know, what we're doing and that that workflow optimization is just so good for every single listener.
00:45:42.320 --> 00:45:48.719
So you want to do uh your one last closer and do my I'm gonna do my one, I'm gonna do the last closeout.
00:45:48.960 --> 00:45:54.000
My last security journey, security champion podcast closeout.
00:45:54.239 --> 00:45:56.880
Um, I want to thank you, Mike, for joining us.
00:45:57.039 --> 00:46:00.880
Uh I can't wait to see what you kind of take this and do with this.
00:46:01.039 --> 00:46:13.840
I want to thank all my guests that have been listening over the years, that have joined me for my security journey as we became champions for organizations in our for champions for security in our organization.
00:46:14.320 --> 00:46:20.719
And as I always end, and always to remember, um, security is a journey, not a destination.
00:46:21.039 --> 00:46:24.880
The Security Champions Podcast is brought to you by Security Journey.
00:46:25.119 --> 00:46:34.000
Security Journey is an enterprise class secure coding training platform with lessons that are built on learning science principles to deliver long term, measurable results.
00:46:34.159 --> 00:46:36.400
Learn more at securityjourney.com.