STIGQter: STIG Summary: Crunchy Data Postgres 16 Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 01 Jul 2026:

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/PostgreSQL principals authorized for ownership.

DISA Rule

SV-261884r1000657_rule

Vulnerability Number

V-261884

Group Title

SRG-APP-000133-DB-000200

Rule Version

CD16-00-002900

Severity

CAT II

CCI(s)

CCI-001499 - Limit privileges to change software resident within software libraries.

Weight

Fix Recommendation

Assign ownership of authorized objects to authorized object owner accounts.

#### Schema Owner

To create a schema owned by the user "bob", run the following SQL:

$ sudo su - postgres
$ psql -c "CREATE SCHEMA test AUTHORIZATION bob"

To alter the ownership of an existing object to be owned by the user "bob", run the following SQL:

$ sudo su - postgres
$ psql -c "ALTER SCHEMA test OWNER TO bob"

Check Contents

Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s).

If any database objects are found to be owned by users not authorized to own database objects, this is a finding.

To check the ownership of objects in the database, as the database administrator, run the following SQL:

$ sudo su - postgres
$ psql -X -c '\dnS'
$ psql -x -c "\dt *.*"
$ psql -X -c '\dsS'
$ psql -x -c "\dv *.*"
$ psql -x -c "\df+ *.*"

If any object is not owned by an authorized role for ownership, this is a finding.

Vulnerability Number

V-261884

Documentable

False

Rule Version

CD16-00-002900

Severity Override Guidance

Check Content Reference

Target Key

5598