Confidentiality and Integrity QOP Policy | Teradata Vantage - 17.20 - Confidentiality and Integrity QOP Policy - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

The quality of protection (QOP) defines the strength of the encryption algorithms the system uses when transmitting messages between Teradata Vantage and its clients.

There are two types of policy subject to Quality of Protection (QOP):
  • An integrity QOP determines the strength of the algorithm the system uses for calculating the checksum that guarantees message integrity.
  • A confidentiality QOP determines the strength of the algorithm for encrypting a message exchange between a client and Vantage. In the absence of a confidentiality QOP policy, client requests for confidentiality use the DEFAULT QOP. See Encryption.
You can assign confidentiality and integrity policies by:
  • Database user name or directory user name
  • Database profile
  • Client IP address
Users who access the database through a middle-tier application that uses pooled sessions are subject to the security policies assigned to the application logon user, rather than the policies assigned to them as individuals.

You can also enforce use of the DEFAULT confidentiality QOP by host group ID. See Requiring Confidentiality.

Java clients do not support encryption stronger than AES-128 without installation of a special security policy package. See QOP Configuration Change Guidelines.