V-259271

Discussion

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 CUI. 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.

Check Content

If security labeling is not required, this is not applicable.

If security labeling requirements have been specified, execute the following SQL as the "enterprisedb" operating system user:

> psql edb -c "SELECT * from ALL_POLICIES where OBJECT_NAME = '<object_name>'"

If a policy is not enabled for the table requiring security labeling, this is a finding.