controls::excessive function privileges are revoked

Overview

In certain situations, to provide required functionality, PostgreSQL needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by their organization. This is known as privilege elevation. Privilege elevation must be utilized only where necessary. Execute privileges for application functions should be restricted to authorized users only.

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

Attributes

Attribute Name Short Description
exclude  
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::excessive_function_privileges_are_revoked

exclude

The objects to exclude from the control actions. Type: Array

Default:pg_secured::lookup_setting('exclude', [])

Back to overview of controls::excessive_function_privileges_are_revoked