When supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in storage.

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.

Check content

If security labeling is not required, this is not a finding. Query the system catalog to find out the existing security labels: DB2> SELECT * FROM SYSCAT.SECURITYLABELS If the required labels are not created in database this is a finding. Query the following catalog views find details of existing security labels: DB2> SELECT * FROM SYSCAT.SECURITYLABELACCESS DB2> SELECT * FROM SYSCAT.SECURITYLABELCOMPONENTELEMENTS DB2> SELECT * FROM SYSCAT.SECURITYLABELCOMPONENTS If the security labels are not defined as per organization security policies, this is a finding.

Fix text

Use Create security Label statement to create the security labels: See the following example to create the components, policy and then security labels: Create the components for Security labels: DB2> CREATE SECURITY LABEL COMPONENT LEVEL ARRAY ['Top Secret', 'Secret', 'Confidential', 'Unclassified']; DB2> CREATE SECURITY LABEL COMPONENT COMPARTMENTS SET {'Collection', 'Research', 'Analysis'}; Create the Policy: DB2> CREATE SECURITY POLICY DATA_ACCESS COMPONENTS LEVEL, COMPARTMENTS WITH DB2LBACRULES; Create Security Label: DB2> CREATE SECURITY LABEL DATA_ACCESS.EMPLOYEESECLABEL COMPONENT LEVEL 'Top Secret', COMPONENT COMPARTMENTS 'Research', 'Analysis' After creating the security labels, use one of the following statements to attach the labels to the table: DB2> CREATE TABLE Or DB2> ALTER TABLE For advice and examples, see the tutorial at: https://www.ibm.com/developerworks/data/tutorials/dm0605wong/ https://www.ibm.com/developerworks/data/tutorials/dm0605wong/section2.html Note: Select the following knowledgebase link for information regarding LBAC Details: http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.sec.doc/doc/c0021114.html Select the following knowledgebase link for information regarding Create Security Label: http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.sql.ref.doc/doc/r0020026.html?cp=SSEPGG_10.5.0%2F2-12-7-94

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

SV-89235r1_rule When supporting applications that require security labeling of data, DB2 must associate organization-defined types of security labels having organization-defined security label values with information in storage.

Vulnerability discussion

Check content

Fix text

Pro Tips