Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

AI Security Table

AI Security Table artwork

Security Champions as the Answer to Engineering Hating Security

Aug 1, 202344 minAudio
ShareXLinkedInFacebookWhatsAppEmail

What happens when engineers transform into security champions? Is this beneficial, and what are the implications of this transformation? Izar reveals his transition from a naysayer to a supporter of security champions, and Chris and Matt seek to understand his current position. They explore the position of Security Champion and discuss the components of a good security champion program. Matt defines security champions as developers with influence who can be a bridge between security and engineering. They receive advanced training and bring resources to their team to lead them to effective threat modeling. While security champion programs may have potential pitfalls, such as overloading team members, good security champion programs should benefit the individual and the business. Chris emphasizes the importance of providing opportunities for growth, learning, and networking to make the program appealing to potential champions. With the potential issue of champions leaving an organization, they highlight the need for companies to keep up with salary expectations as champions grow in their roles. They also touch on the challenge of preventing security champions from being disliked by their team once they transition from being developers. There are several resources for those interested in building a Champions program, including Dustin Lehr's Security Champion Success Guide and Chris Romeo's Security Champion Framework available on GitHub. The episode concludes with a call for listener feedback and input, emphasizing the hosts' desire for an interactive and engaging conversation with their audience. Follow AI Security Table: ➜ Home: https://securitytable.ai/ ➜ X: https://x.com/SecTablePodcast ➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/ ➜ YouTube: https://www.youtube.com/@AISecurityTable

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Claude Code Said ‘Don’t Ask Again.’ Then It Leaked Your Secrets to GitHub

    Nov 18, 202642 minAudio

    Click “Yes, and don’t ask again” in Claude Code and it saves the exact command you approved, password and all, into a local settings file that keeps turning up in public GitHub repos. We start by admitting we all run...

    Credit the people on this episode

  2. Stop Patching Bugs, Just Rewrite It… Says the Guy Selling the Tokens

    Nov 11, 202650 minAudio

    Cisco's president handed a 27 year old engineer unlimited AI tokens and 24 months to rewrite 98 percent of the company's legacy code, and Sam Altman now says we can no longer just patch all the bugs. Chris sees a step...

    Credit the people on this episode

  3. You Don't Trust AI. So Why Are You Shipping Its Code?

    Nov 4, 202650 minAudio

    Sam Altman told a Stanford audience he no longer thinks we can just patch all the bugs, and the AI Security Table can't agree on whether that is news. Chris argues a swarm of subagents can tear through a repo and drive...

    Credit the people on this episode

  4. Anthropic Ditched Git. Here’s Why Your Agents Will Too

    Oct 28, 202645 minAudio

    Anthropic got tired of Git. With merges jumping from about 2,500 a day in May to more than 30,000 by September, a seven person team built Scion, a centralized, always online source control system designed for agents...

    Credit the people on this episode

  5. Don't Yell at Claude

    Oct 21, 202644 minAudio

    The White House has ordered federal agencies to stop saying AI and start saying Super Intelligence, and the hosts want to know whether anything actually changed overnight. Matt walks through the executive order and the...

    Credit the people on this episode