UCF STIG Viewer Logo

The EDB Postgres Advanced Server must associate organization-defined types of security labels having organization-defined security label values with information in storage.


Finding ID Version Rule ID IA Controls Severity
V-213614 PPS9-00-006900 SV-213614r508024_rule Medium
Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. One example includes marking data as classified or FOUO. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise. The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.
EDB Postgres Advanced Server Security Technical Implementation Guide 2022-06-13


Check Text ( C-14836r290154_chk )
If security labeling is not required, this is not applicable (NA).

If security labeling requirements have been specified, execute the following SQL as enterprisedb:


If a policy is not enabled for the table requiring security labeling, this is a finding.
Fix Text (F-14834r290155_fix)
Create a row-level policy for all required tables as defined here: