controls::set user extension is installed
Overview
Even when reducing and limiting the access to the superuser role as described earlier in this benchmark, it is still difficult to determine who accessed the superuser role and what actions were taken using that role. As such, it is ideal to prevent anyone from logging in as the superuser and forcing them to escalate their role. This model is used at the OS level by the use of sudo and should be emulated in the database. The set_user extension allows for this setup.
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:
- Postgres Database 13 CIS V1.0.0 - paragraph 4.7
- Postgres Database 13 CIS V1.1.0 - paragraph 4.6
- Postgres Database 14 CIS V1.0.0 - paragraph 4.6
- Postgres Database 14 CIS V1.1.0 - paragraph 4.6
- Postgres Database 15 CIS V1.0.0 - paragraph 4.6
- Postgres Database 15 CIS V1.1.0 - paragraph 4.6
- Postgres Database 16 CIS V1.0.0 - paragraph 4.6
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 pg_secured::controls::set_user_extension_is_installed: skip
to your hiera data. This will skip this control for ALL databases.
2) Add pg_secured::controls::set_user_extension_is_installed::dbname: skip
to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content set_user_extension_is_installed
to the array value pg_secured::skip_list
in your hiera data.
Attributes
Attribute Name | Short Description |
---|---|
title | The instance to apply the control to. |
title
The instance to apply the control to.
All controls need an instance to apply the control to. Here is a simple example:
pg_secured::controls::control_name { 'instance':}
In this example, the string instance
is the instance to apply the control to.
Back to overview of controls::set_user_extension_is_installed