controls::set umask value in the db2 instance owners profile

Overview

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.

Rationale:

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.

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 db2_secured::controls::set_umask_value_in_the_db2_instance_owners_profile: skip to your hiera data. This will skip this control for ALL databases.
2) Add db2_secured::controls::set_umask_value_in_the_db2_instance_owners_profile::instance_name::dbname: skip to your hiera data. This will skip this control for specified database only.
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.

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