Category: Security, Infrastructure, apple, gitlab, automation

Security-as-code is the practice of “building security into DevOps tools and workflows by mapping out how changes to code and infrastructure are made and finding places to add security checks, tests, and gates without introducing unnecessary costs or delays,” according to tech publisher O’Reilly. In this latest “pancakes and podcast” special episode — recorded during a pancake breakfast at KubeCon + CloudNativeCon in October — we discuss how security-as-code can benefit emerging GitOps practices.

Alex Williams, founder and publisher of TNS, hosted the podcast.

The emergence of security-as-code signifies how the days of security teams holding deployments up are waning.

Security-as-code serves to both automate security for CI/CD with GitOps while also ensuring security processes are taking interconnectivity into account.

Related Articles