Sign up to save your podcasts
Or
Share Security is not a Checkbox
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Security is not a Checkbox
Episode Summary
In this episode, Dr. KJ sits down with Kimberly, a product and engineering leader in the insurance industry, to talk about what it really takes to build secure products at enterprise scale. From managing security consistency across legacy and cloud applications to rolling out AI responsibly in a highly regulated environment, Kimberly brings a practitioner's perspective grounded in transparency, least privilege, and bringing people along on the journey. The conversation covers the tension between shipping fast and staying secure, the role of AI in transforming insurance products, and the leadership principles that make security culture stick.
What You'll Learn
In this episode, you will learn how a seasoned product leader approaches security consistency across applications of different ages and architectures, why least privilege is not just a technical control but a cultural practice, how to lead a phased AI rollout in a regulated industry while keeping InfoSec at the table from day one, what it looks like when security design reviews become a celebration rather than a checkpoint, and how to translate technical vulnerabilities into business risk language that resonates with stakeholders and leadership.
Top 3 Takeaways
Security has to be built in from the start. Treating it as a checklist item at the end of a development cycle creates inconsistency and opens the door to costly exposures. The why matters more than the what. Whether you are enforcing least privilege, rearchitecting vendor integrations, or rolling out AI, helping your team understand the reasoning behind a decision is what prevents corner-cutting and builds lasting security culture. AI is an accelerator, not a free pass. Organizations that are seeing real value from AI are the ones that stage their rollouts, measure outcomes, and keep security embedded in the design process from the beginning.
Memorable Quotes
"A small book could turn into a $5 million bigger issue."
"I don't look at security as the last thing that we do when we're getting ready to ship."
"There's no role or no space that's small. Security impacts every role."
"We catch security flaws early and design phases are celebrated — it's a win for all of us."
Connect with the Guest
Connect with Kimberly on LinkedIn: https://www.linkedin.com/in/kimberly-w-4841923aa/
Listen & Subscribe
Like, follow, and subscribe to Secured with Dr. KJ: https://swdrkj.riverside.com
Apple Podcasts: https://podcasts.apple.com/us/podcast/secured-with-dr-kj/id1805058517 Spotify: Search Secured with Dr. KJ YouTube: Search Secured with Dr. KJ
Support the Show
If this episode added value, share it with a colleague, leave a review, and help grow the Secured with Dr. KJ community. Every share puts these conversations in front of the practitioners who need them most.
Securing tomorrow, one episode at a time.
View all episodes
By Kenneth JohnsonEpisode Summary
In this episode, Dr. KJ sits down with Kimberly, a product and engineering leader in the insurance industry, to talk about what it really takes to build secure products at enterprise scale. From managing security consistency across legacy and cloud applications to rolling out AI responsibly in a highly regulated environment, Kimberly brings a practitioner's perspective grounded in transparency, least privilege, and bringing people along on the journey. The conversation covers the tension between shipping fast and staying secure, the role of AI in transforming insurance products, and the leadership principles that make security culture stick.
What You'll Learn
In this episode, you will learn how a seasoned product leader approaches security consistency across applications of different ages and architectures, why least privilege is not just a technical control but a cultural practice, how to lead a phased AI rollout in a regulated industry while keeping InfoSec at the table from day one, what it looks like when security design reviews become a celebration rather than a checkpoint, and how to translate technical vulnerabilities into business risk language that resonates with stakeholders and leadership.
Top 3 Takeaways
Security has to be built in from the start. Treating it as a checklist item at the end of a development cycle creates inconsistency and opens the door to costly exposures. The why matters more than the what. Whether you are enforcing least privilege, rearchitecting vendor integrations, or rolling out AI, helping your team understand the reasoning behind a decision is what prevents corner-cutting and builds lasting security culture. AI is an accelerator, not a free pass. Organizations that are seeing real value from AI are the ones that stage their rollouts, measure outcomes, and keep security embedded in the design process from the beginning.
Memorable Quotes
"A small book could turn into a $5 million bigger issue."
"I don't look at security as the last thing that we do when we're getting ready to ship."
"There's no role or no space that's small. Security impacts every role."
"We catch security flaws early and design phases are celebrated — it's a win for all of us."
Connect with the Guest
Connect with Kimberly on LinkedIn: https://www.linkedin.com/in/kimberly-w-4841923aa/
Listen & Subscribe
Like, follow, and subscribe to Secured with Dr. KJ: https://swdrkj.riverside.com
Apple Podcasts: https://podcasts.apple.com/us/podcast/secured-with-dr-kj/id1805058517 Spotify: Search Secured with Dr. KJ YouTube: Search Secured with Dr. KJ
Support the Show
If this episode added value, share it with a colleague, leave a review, and help grow the Secured with Dr. KJ community. Every share puts these conversations in front of the practitioners who need them most.
Securing tomorrow, one episode at a time.