The New Stack Podcast

Infrastructure as Code is a Movement Ready to Boom

Episode Summary

Prisma Cloud from Palo Alto Networks sponsored this podcast. Infrastructure as code is a movement ready to boom. It’s also emerging as one of the three pillars in cloud security that are bringing DevOps and security together in the evolving DevSecOps market, said Varun Badhwar, senior vice president, Prisma Cloud at Palo Alto Networks, in this episode of The New Stack Makers hosted by TNS Founder and Publisher Alex Williams. Infrastructure as code is also a major component of the DevOps’ trend to shift left. “Shift left security now means application security, it means software composition analysis and it means infrastructure as code scanning — and all of that now is available for DevOps teams to do in the pipeline,” Badhwar explained. “And in an ideal situation,” he continued, “you want to tie all of that to the tools that your infosec teams want to use in runtime in production, such that you have one set of policies globally recognized in your enterprise. And you’re working against the same standards — it’s just a matter of fact about where you’re deploying those tools in your lifecycle.”

Episode Notes

Prisma Cloud from Palo Alto Networks sponsored this podcast.

Infrastructure as code is a movement ready to boom. It’s also emerging as one of the three pillars in cloud security that are bringing DevOps and security together in the evolving DevSecOps market, said Varun Badhwar, senior vice president, Prisma Cloud at Palo Alto Networks, in this episode of The New Stack Makers hosted by TNS Founder and Publisher Alex Williams.

Infrastructure as code is also a major component of the DevOps’ trend to shift left. “Shift left security now means application security, it means software composition analysis and it means infrastructure as code scanning — and all of that now is available for DevOps teams to do in the pipeline,” Badhwar explained.

“And in an ideal situation,” he continued, “you want to tie all of that to the tools that your infosec teams want to use in runtime in production, such that you have one set of policies globally recognized in your enterprise. And you’re working against the same standards — it’s just a matter of fact about where you’re deploying those tools in your lifecycle.”