controls::correct syslog facility is selected

Overview

The syslog_facility setting specifies the syslog “facility” to be used when logging to syslog is enabled. You can choose from any of the ‘local’ facilities: • LOCAL0 • LOCAL1 • LOCAL2 • LOCAL3 • LOCAL4 • LOCAL5 • LOCAL6 • LOCAL7 Your organization’s logging policy should dictate which facility to use based on the syslog daemon in use.

Excelent Compliance Solution.

Puppet is an excellent solution to ensure your databases are CIS or STIG compliant. Now you’re looking at information about only one compliance control, but managing total compliance isn’t hard either!

If you you like he prospect of easy way into continuous compliancy with minimal fuss and bother, we suggest taking a look at our solution as your go-to option. Plus, our team can help you get up and running so that you can focus on other areas of your business. What are you waiting for? Get started today!

Benchmarks

This control is used in the following benchmarks:

Skipping

To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:

1) Add pg_secured::controls::correct_syslog_facility_is_selected: skip to your hiera data. This will skip this control for ALL databases.
2) Add pg_secured::controls::correct_syslog_facility_is_selected::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content correct_syslog_facility_is_selected to the array value pg_secured::skip_list in your hiera data.

Attributes

Attribute Name Short Description
title The instance to apply the control to.

title

The instance to apply the control to.

All controls need an instance to apply the control to. Here is a simple example:

pg_secured::controls::control_name { 'instance':}

In this example, the string instance is the instance to apply the control to.

Back to overview of controls::correct_syslog_facility_is_selected