controls::authentication type for incoming connections at the server srvcon auth
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 defines where and how user authentication is done for incoming connections at the server. If no value is used, DB2 uses the database manager configuration parameter authentication.
Rationale
Incoming connections to the DB2 server must follow an authentication protocol. The srvcon_auth server configuration parameter defines how and where user authentication is done.
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::authentication_type_for_incoming_connections_at_the_server_srvcon_auth: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content authentication_type_for_incoming_connections_at_the_server_srvcon_auth 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.2.3
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::authentication_type_for_incoming_connections_at_the_server_srvcon_auth
