controls::secure permissions for alternate diagnostic log path
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 ALT_DIAGPATH parameter specifies an alternative location of the diagnostic files for the Db2 instance if the primary location specified by DIAGPATH is unavailable. 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_alternate_diagnostic_log_path: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content secure_permissions_for_alternate_diagnostic_log_path to the array value db2_secured::skip_list in your hiera data.
Benchmarks
This control is used in the following benchmarks:
- db11 CIS V1.0.0 - paragraph 3.1.5
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_alternate_diagnostic_log_path
