Skip to content
Puppet hardening using cis benchmark
Puppet HTML Shell Ruby Pascal
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc
lib/facter
manifests
templates/trusty64
.travis.yml
README.md
metadata.json

README.md

cis-benchmark Build Status

Puppet hardening module premised on cis benchmark:

Note: the puppet numbering scheme, matches the corresponding benchmark.

Dependency

The Puppetfile requires the following:

Execution

Specific rules can be nested under the following yaml keys, of a yaml file defined from the hiera.yaml, of the corresponding puppetserver:

  • [node-certificate]
  • cis_benchmark
  • trusty64

If the yaml key exists, by the name of the nodes certificate (delimited by underscores), then the corresponding cis rules will take precedence. Otherwise, if the cis_benchmark, or the trusty64 yaml key exists, it will load the respective rules.

The following is the Ubuntu 14.04 implementation:

cis_benchmark::trusty64:
    stig:
        cis_1_1_1_1: true
        cis_1_1_1_2: true
        cis_1_1_1_3: true

Note: the params.pp can be further reviewed in order to override default cis rules.

Similar rules can be defined directly in the environment's site.pp, as an alternative approach to the hiera implementation:

class { 'cis_benchmark':
    cis_1_1_1_1 => true,
    cis_1_1_1_2 => true,
    cis_1_1_1_3 => true,
}

Note: the params.pp can be further reviewed in order to override default cis rules.

You can’t perform that action at this time.