In this chapter, we looked at how to use Puppet to solve various compliance challenges. We looked at how to use Puppet manifests to document the system state. This can be unbelievably helpful in showing how a system is configured.

Additionally, we then looked at how version control can help you show the history of the system configuration, when various things changed, as well as possibly help us show who made the changes.

Finally, we looked at specific challenges that the PCI DSS creates, and how we can use Puppet to solve them, including several examples of the use of Puppet to automate some of the PCI DSS requirements.

Compliance is a journey, not a destination. As we learn more and get more familiar with the Puppet ecosystem, we will learn many more ways to use Puppet to assist us in our compliance needs. We'll explore some additional resources to review in Appendix, Going Forward.

In the meantime, in the next chapter, we'll move on and explore how we can use Puppet to generate security...