STIGQter: STIG Summary: Crunchy Data PostgreSQL Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 20 Nov 2020:

PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission.

DISA Rule

SV-233521r617333_rule

Vulnerability Number

V-233521

Group Title

SRG-APP-000314-DB-000310

Rule Version

CD12-00-001100

Severity

CAT II

CCI(s)

• CCI-002264 - The organization provides the means to associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.

Weight

10

Fix Recommendation

In addition to the SQL-standard privilege system available through GRANT, tables can have row security policies that restrict, on a per-user basis, which rows can be returned by normal queries or inserted, updated, or deleted by data modification commands. This feature is also known as Row-Level Security (RLS).

RLS policies can be very different depending on their use case. For one example of using RLS for Security Labels, see supplementary content APPENDIX-D.

Check Contents

If security labeling is not required, this is not a finding.

First, as the database administrator (shown here as "postgres"), run the following SQL against each table that requires security labels:

$ sudo su - postgres
$ psql -c "\d+ <schema_name>.<table_name>"

If security labeling is required and the results of the SQL above do not show a policy attached to the table, this is a finding.

If security labeling is required and not implemented according to the system documentation, such as SSP, this is a finding.

If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.

Vulnerability Number

V-233521

Documentable

False

Rule Version

CD12-00-001100

Severity Override Guidance

If security labeling is not required, this is not a finding.

First, as the database administrator (shown here as "postgres"), run the following SQL against each table that requires security labels:

$ sudo su - postgres
$ psql -c "\d+ <schema_name>.<table_name>"

If security labeling is required and the results of the SQL above do not show a policy attached to the table, this is a finding.

If security labeling is required and not implemented according to the system documentation, such as SSP, this is a finding.

If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.

Check Content Reference

M

Target Key

5254

Comments