16.10 - QOP Configuration Options - Teradata Database

Teradata Database Security Administration

Product
Teradata Database
Release Number
16.10
Release Date
June 2017
Content Type
Administration
Security
Publication ID
B035-1100-161K
Language
English (United States)

You can enable QOP strength options in the TD2, PROXY, and LDAP mechanisms, to use in enforcing QOP security policy. For information about how QOP strength options are used in QOP security policy, see Chapter 25 Network Security Policy.

For users authenticated by Kerberos (KRB5 or SPNEGO mechanism) who enable message encryption or are subject to a confidentiality QOP policy, the system uses the encryption method and strength automatically negotiated by Kerberos. See Message Encryption for Kerberos Authentication.

The following table describes QOP configuration options for each element in the QOP section of the TDGSS configuration file.

Configuration File Element Configuration Options
LEGACY QOP Legacy QOP is the default for Release13.10 and previous.

You can disable the Legacy QOP to force stronger encryption, but if the Legacy QOP is disabled, users cannot log on from clients running TTU releases prior to 14.0.

DEFAULT QOP You can edit the DEFAULT QOP to a different encryption strength.
  • AES-128 (default)
  • AES-192
  • AES-256
  • LOW SECURITY QOP
  • MEDIUM SECURITY QOP
  • HIGH SECURITY QOP
If you plan on configuring QOP security policies, you can:
  • Enable the LOW, MEDIUM, and HIGH SECURITY QOP entries for use in confidentiality and integrity policies.
  • Optionally edit the LOW, MEDIUM, and HIGH SECURITY QOP entries to specify a different encryption strength.