controls::use non default account names

Overview

The DB2 service is installed with default accounts with well-known names such as db2admin, db2inst1, dasusr1, or db2fenc1. It is recommended that the use of these account names be avoided. The default accounts may be renamed and then used.

Rationale:

The use of default account names may increase the DB2 service’s susceptibility to unauthorized access by an attacker.

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 1.4

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::use_non_default_account_names: skip to your hiera data. This will skip this control for ALL databases.
2) Add db2_secured::controls::use_non_default_account_names::instance_name::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content use_non_default_account_names to the array value db2_secured::skip_list in your hiera data.

Attributes

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