The key point to note is that the whole process is automated and configuration flags determine which environments (test, staging or production) to target. Additionally, CI / CD workflows are put in place to track code commit to trigger build, deploy and test phases. How security teams can leverage ```Terraform``` and the Palo Alto Networks ```Terraform provider``` to leverage CI / CD workflows to keep pace with line of business requirements.Īpplication teams leverage repositories such as github and others, to not only store and backup the code-base, but also for the purpose of change management.How app teams and security teams can leverage code repositories such as github to store both application artifacts and security policies as code.These capabilities enable enterprises as a whole to succeed by deploying the line of business application in a timely and more importantly, a secure manner. However, Palo Alto Networks has built out a slew of automation capabilities that provide security teams with the capabilities and tools to demonstrate the same agility as the app teams. Consequently, quite often this results in security teams slowing down the deployment of apps into production environments. ![]() ![]() The agility of the dev teams puts a lot of pressure on the infrastructure and security teams to keep pace. The objective of this blog is to describe and demonstrate the use of Terraform deployment and configuration templates to build out CI / CD workflows.Īpplication developers working in agile teams have the need to push and deploy code numerous times a day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |