controls::secure db2 runtime library
Overview
A DB2 software installation will place all executables under the default
Rationale:
The DB2 runtime is comprised of files that are executed as part of the DB2 service. If these resources are not secured, an attacker may alter them to execute arbitrary code.
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!
Benchmarks
This control is used in the following benchmarks:
- DB2 Database 10 CIS V1.1.0 - paragraph 2.1
- DB2 Database 11 CIS V1.0.0.draft - paragraph 3.3.1
Skipping
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::secure_db2_runtime_library: skip to your hiera data. This will skip this control for ALL databases.
2) Add db2_secured::controls::secure_db2_runtime_library::instance_name::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content secure_db2_runtime_library to the array value db2_secured::skip_list in your hiera data.
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.