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 table function SYSPROC.AUTH_LIST_GROUPS_FOR_AUTHID returns the groups for the specified authorization ID. In a non-restrictive database this table function has EXECUTE granted to public. It is recommended that public should not be able to execute this routine.


A malicious user may use this function to conduct information gathering regarding the groups that users belong to.


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


This control is used in the following benchmarks:


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