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

A DB2 software installation will place all executables under the default \sqllib directory. This directory needs to be secured so it grants only the necessary access to authorized users and administrators.

Rationale

The DB2 runtime is comprised of files that are executed as part of the DB2 service. If these resources are not secured, an attacker may alter them to execute arbitrary code.

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_db2_runtime_library: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content secure_db2_runtime_library 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_db2_runtime_library