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

PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.

DISA Rule

SV-233515r617333_rule

Vulnerability Number

V-233515

Group Title

SRG-APP-000023-DB-000001

Rule Version

CD12-00-000500

Severity

CAT I

CCI(s)

• CCI-000015 - The organization employs automated mechanisms to support the information system account management functions.

Weight

10

Fix Recommendation

Note: The following instructions use the PGDATA environment variable. See supplementary content APPENDIX-F for instructions on configuring PGDATA.

Integrate PostgreSQL security with an organization-level authentication/access mechanism providing account management for all users, groups, roles, and any other principals.

As the database administrator (shown here as "postgres"), edit pg_hba.conf authentication file:

$ sudo su - postgres
$ vi ${PGDATA?}/pg_hba.conf

For each PostgreSQL-managed account that is not documented and approved, either transfer it to management by the external mechanism, or document the need for it and obtain approval, as appropriate.

Check Contents

Note: The following instructions use the PGDATA environment variable. See supplementary content APPENDIX-F for instructions on configuring PGDATA.

If all accounts are authenticated by the organization-level authentication/access mechanism, such as LDAP or Kerberos and not by PostgreSQL, this is not a finding.

As the database administrator (shown here as "postgres"), review pg_hba.conf authentication file settings:

$ sudo su - postgres
$ cat ${PGDATA?}/pg_hba.conf

All records must use an auth-method of gss, sspi, or ldap. For details on the specifics of these authentication methods see: http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html.

If there are any records with a different auth-method than gss, sspi, or ldap, review the system documentation for justification and approval of these records.

If there are any records with a different auth-method than gss, sspi, or ldap, that are not documented and approved, this is a finding.

Vulnerability Number

V-233515

Documentable

False

Rule Version

CD12-00-000500

Severity Override Guidance

Note: The following instructions use the PGDATA environment variable. See supplementary content APPENDIX-F for instructions on configuring PGDATA.

If all accounts are authenticated by the organization-level authentication/access mechanism, such as LDAP or Kerberos and not by PostgreSQL, this is not a finding.

As the database administrator (shown here as "postgres"), review pg_hba.conf authentication file settings:

$ sudo su - postgres
$ cat ${PGDATA?}/pg_hba.conf

All records must use an auth-method of gss, sspi, or ldap. For details on the specifics of these authentication methods see: http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html.

If there are any records with a different auth-method than gss, sspi, or ldap, review the system documentation for justification and approval of these records.

If there are any records with a different auth-method than gss, sspi, or ldap, that are not documented and approved, this is a finding.

Check Content Reference

M

Target Key

5254

Comments