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

Use an IP address rather than a hostname to connect to the host of the DB2 instance.

Rationale

Using a hostname to connect to a DB2 instance can display useful information about the host to an attacker. For example, hostnames for DB2 instances often contain the DB2 version number, host type, or operating system type

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