3. Puppet for Compliance | Learning Puppet Security

Using manifests to document the system state

One of the strongest tools in the Puppet compliance tool chest is the concept of the manifest. Since the manifest represents the system's desired state, we can use the data found in it to show what the system looks like.

Consider the following example: you have an audit requirement that says key security-related services and software must be kept up to date. Working with your security team, you've identified a list of packages that fall under this. For the purposes of our example, we'll say they're openssh, kerberos, and openssl.

We can write a manifest that looks like the following, to ensure that this is the case:

class compliance(
  $ensure   = latest,
  $packages = ['openssh', 'kerberos', 'openssl']
)  {
  package { $packages:
    ensure => $ensure,
  }
}

Note

As we noted earlier, normal practice would dictate that to use the preceding pattern, you would be sourcing these packages from your own local repository and would promote them after testing...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Learning Puppet Security

By : Jason Slagle

Learning Puppet Security

By: Jason Slagle

Overview of this book

Using manifests to document the system state

Note

Learning Puppet Security

By : Jason Slagle

Learning Puppet Security

By: Jason Slagle

Overview of this book

Using manifests to document the system state

Note

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access