controls::nested roles
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 user-defined roles in DB2 can be nested in the same fashion as Windows security groups–a nested group has both its directly assigned permissions as well as the assigned group permissions. By nesting roles, the database administrator is saving time by only having to assign a group of users versus assigning them individually. Nesting roles properly can often ease the application of the security model if it’s kept fairly shallow, and if the roles are logically named. If these are all true, then nesting of roles is a good idea.
Rationale
As tracking multiple levels of permissions can result in unauthorized access to data resources, this capability should be restricted according to the needs of the business.
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::nested_roles: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content nested_roles 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 8.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.
