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 Db2 instance owner’s .profile file in Linux sets the environment variables and the settings for the user. This file is specific to the Korn shell and BASH shell, and other shells may have a different file.


The umask value should be set to 022 for the owner of the Db2 software at all times to ensure files are not created with unnecessary privileges.


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::set_umask_value_in_the_db2_instance_owners_profile: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content set_umask_value_in_the_db2_instance_owners_profile to the array value db2_secured::skip_list in your hiera data.


This control is used in the following benchmarks:


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


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::set_umask_value_in_the_db2_instance_owners_profile