controls::review system tablespaces
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
System tablespaces store all system object data within that database. It is recommended that system tablespaces are used to stored system data only and not user data.
Rationale
Users should not have privileges to create user data objects within the system tablespaces. User data objects created within the system tablespaces should be removed.
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::review_system_tablespaces: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content review_system_tablespaces 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 9.3
- db11 CIS V1.0.0 - paragraph 4.5.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.
