Hey, cyber listeners, Matthew here.

This episode is supported by Code Comments, an original podcast from Red Hat.

You know when you're working on a project and you leave behind a small note in the code,

a code comment to help others learn what isn't clear in the code?

This podcast features technologists who've been through tech transitions and share how their

teams survived the journey.

There's a lot of work required to bring a project from purchase to production,

and the documentation doesn't cover changing team dynamics.

The host, Jamie Parker, is a redhatter and an experienced engineer.

In each episode, Jamie recounts the stories of experienced technologists from across the industry

who share what they've learned from implementing new technology.

Episodes are available anywhere you list to podcasts and at redhat.com slash code comments podcast.

I listened to Season 2, Episode 5, you can't automate the difficult decisions, which is all about

security, an automating security,

an AI insecurity. It was pretty fascinating. Did you know that 52% of companies are sacrificing

security for speed? I didn't until I listened to this podcast. So should you automate security,

what can you get away with automating? Should you shift security to the left, as they say? Well, take a listen.

On the surface, security seems like an obvious candidate for automation. IT systems are complex conglomerations of components, most of which are potential vectors for attack.

Proper configuration, constant vigilance, and rapid response are essential elements of an

effective security system. Automation helps security teams be more effective with those, and more.

And yet, when security is an afterthought, or even just considered late in the development cycle,

the odds of avoidable catastrophic breaches go up.

...