Defining Security Labels for Users/Rows | Teradata Vantage - 17.10 - Defining Security Labels for Users and Rows - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.ditaval
dita:id
zuy1472246340572
Before implementing row level security, you should define the security classification systems and associated labels required to support your site security policy.
  1. Define each classification system and identify the labels in the system.

    Each system is the basis for a security CONSTRAINT object, which defines a set of access controls. Each user can be assigned up to 6 hierarchical and 2 non-hierarchical constraints.

  2. For each table requiring RLS protection, determine which of the classification system (security constraints) should apply to the range of users who access the table.

    A table can contain up to 5 constraint columns.

  3. Identify how security labels for each system should apply to table rows, and define the user access level required to perform each SQL operation (INSERT, SELECT, UPDATE, and DELETE).

    You can use this analysis to help:

    • Determine the level of protection required for each row
    • Define the SQL access rules used in creating security constraint UDFs
    • Determine which UDFs should be used in a security CONSTRAINT object