controls::enable server based authentication

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 srvcon_auth parameter specifies how and where authentication is to take place for incoming connections to the server. It is recommended that this parameter is not set to CLIENT.

Rationale

This parameter will take precedence over and override the authentication level. Authentication should be set on the server side.

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

Attributes

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