Use Case for Configuring Global and Local Security Policies - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

A single global security policy structure usually meets company security needs. However, some companies may need to configure both global and local policies. For example:

Assume that a company has three semi-independent divisions, Human Resources, Development, and Marketing.

All three divisions store information on the same Teradata Vantage system.

Each division has a dedicated directory service to independently manage its users.

Human Resources deals with sensitive information about employees and needs to enforce a strict, local QOP (encryption) policy on their users.

Development and Marketing share security policy requirements so they can share the same global policy structure, whereas Human Resources requires a separate local policy structure.