controls::restrict access to syscat events
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 SYSCAT.EVENTS view contains all types of events that the database is currently monitoring. It is recommended that the PUBLIC role be restricted from accessing this view.
Rationale
The types of events that the database is monitoring should not be made readily available to the public.
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::restrict_access_to_syscat_events: skip to your hiera data. This will skip this control for ALL systems.
3) Add an entry with the content restrict_access_to_syscat_events 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 6.5
- db11 CIS V1.0.0 - paragraph 4.2.12
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::restrict_access_to_syscat_events
