controls::secure permissions for all diagnostic logs

Overview

Puppet controls are Puppet defined types that ensure a certain security control is implemented. Puppet changes the system in order to make the system compliant.

Description of the control

The diagpath parameter specifies the location of the diagnostic files for the DB2 instance. The directory at this location should be secured so that users have read and execute privileges only (no write privileges). All DB2 administrators should have full access to the directory.

Rationale

Securing the directory will ensure that the confidentiality, integrity, and availability of the diagnostic files contained in the directory are preserved.

Skipping

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

1) Add db2_secured::controls::secure_permissions_for_all_diagnostic_logs: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content secure_permissions_for_all_diagnostic_logs to the array value db2_secured::skip_list in your hiera data.

Benchmarks

This control is used in the following benchmarks:

Attributes

Attribute Name Short Description
title The database identifier to apply the control to.

title

The database identifier to apply the control to.

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

db2_secured::controls::control_name { 'db2inst1/MYDB':}

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

Back to overview of controls::secure_permissions_for_all_diagnostic_logs