controls::secure permissions for the log mirror location
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 mirrorlogpath parameter specifies the type of media and the location used to store the mirror copy of the logs. It is recommended that the directory used for the mirror copy of the logs be set to full access for DB2 administrator accounts and read and execute only for all other accounts.
Rationale
A mirror log path should not be empty and it should be a valid path. The mirror log path stores a second copy of the active log files. Access to the directory pointed to by that path should be restricted through permissions to help ensure that the confidentiality, integrity, and availability of the mirror logs are protected.
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_the_log_mirror_location: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content secure_permissions_for_the_log_mirror_location to the array value db2_secured::skip_list in your hiera data.
Benchmarks
This control is used in the following benchmarks:
- db10 CIS V1.1.0 - paragraph 3.1.20
- db11 CIS V1.0.0 - paragraph 4.1.8
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_the_log_mirror_location
