The TRUST_ALLCLNTS database manager configuration parameter is only active when the authentication parameter is set to CLIENT which is not a recommended setting as discussed in the authentication parameter section. If the parameter is set to YES, the server assumes that the client side is handling authentication to the database. If the parameter is set to NO, the client must provide authentication to the server on behalf of the user.

The recommended value for this parameter is NO.


If the server trusts the client to authenticate the connecting user, a malicious user can connect to the database as any user including a database administrator by simply creating that user on the client system.

Excelent Compliance Solution.

Puppet is an excellent solution to ensure your databases are CIS or STIG compliant. Now you’re looking at information about only one compliance control, but managing total compliance isn’t hard either!

If you you like he prospect of easy way into continuous compliancy with minimal fuss and bother, we suggest taking a look at our solution as your go-to option. Plus, our team can help you get up and running so that you can focus on other areas of your business. What are you waiting for? Get started today!


This control is used in the following benchmarks:


To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:

1) Add db2_secured::controls::database_manager_configuration_parameter_trust_allclnts: skip to your hiera data. This will skip this control for ALL databases.
2) Add db2_secured::controls::database_manager_configuration_parameter_trust_allclnts::instance_name::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content database_manager_configuration_parameter_trust_allclnts to the array value db2_secured::skip_list in your hiera data.


Attribute Name Short Description
title The database identifier to apply the control to.


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