controls::authenticate federated users at the instance level

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 fed_noauth parameter determines whether federated authentication will be bypassed at the instance. It is recommended that this parameter be set to no.

Rationale

Setting fed_noauth to no will ensure that authentication is checked at the instance level. This will prevent any federated authentication from bypassing the client and the server.

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

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