controls::restrict access to syscat roleauth

Overview

The SYSCAT.ROLEAUTH view contains information on all roles and their respective grantees. It is recommended that the PUBLIC role be restricted from accessing this view.

Rationale:

PUBLIC should not have access to see the grants of the roles because this could be used as a point of exploit.

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:

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

Back to overview of controls::restrict_access_to_syscat_roleauth