The EDB Postgres Advanced Server must enforce authorized access to all PKI private keys stored/utilized by the EDB Postgres Advanced Server.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-68953	PPS9-00-004600	SV-83557r1_rule		High

Description
The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the DBMS-stored private keys are used to authenticate the DBMS to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the DBMS system and its clients. Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-2 validated cryptographic modules. All access to the private key(s) of the DBMS must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the DBMS's private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.

Description

The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key. If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the DBMS-stored private keys are used to authenticate the DBMS to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the DBMS system and its clients. Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-2 validated cryptographic modules. All access to the private key(s) of the DBMS must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the DBMS's private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.

STIG	Date
EDB Postgres Advanced Server Security Technical Implementation Guide	2017-11-17

Details

Check Text ( C-69425r3_chk )
Verify User ownership, Group ownership, and permissions on the “server.key” file: > ls –alL /server.key If the User owner is not “enterprisedb”, this is a finding If the Group owner is not “enterprisedb”, this is a finding. If the file is more permissive than 600, this is a finding. (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Check Text ( C-69425r3_chk )

Verify User ownership, Group ownership, and permissions on the “server.key” file:
> ls –alL /server.key
If the User owner is not “enterprisedb”, this is a finding
If the Group owner is not “enterprisedb”, this is a finding.
If the file is more permissive than 600, this is a finding.

(The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)

Fix Text (F-75137r1_fix)
Run these commands: 1) "chown enterprisedb /server.key" 2) "chgrp enterprisedb /server.key" 3) "chmod 600 /server.key" (The default path for the postgresql data directory is /var/lib/ppas/9.5/data, but this will vary according to local circumstances.)