16.10 - Setting Up TDGSS - Teradata Database

Teradata Database Security Administration

Teradata Database
Release Number
Release Date
June 2017
Content Type
Publication ID
English (United States)

No special setup is required if you use the default Teradata Database authentication.

Additional setup of TDGSS configuration files may be required on Teradata Database Nodes and on Unity, depending on the features you implement. See the chapters in this book that describe implementation.

TDGSS Channel Binding

TDGSS channel binding enables binding TDGSS authentication mechanisms to secure channels at lower network layers for those mechanisms that support channel binding, such as the PROXY mechanism. Channel binding verifies the endpoints of the lower level network layers to eliminate man-in-the-middle attacks. In the case of the PROXY mechanism, channel binding also makes it more difficult to use stolen certificates to pretend to be a legitimate endpoint. For increased security between Unity and the gateway, enable channel bindings on the managed Teradata Database servers. Use Gateway Control to enable channel binding:

gtwcontrol -j yes

The domain component (DC) of a Unity certificate for the PROXY mechanism is required to contain the name of the machine where Unity runs, but the name is not validated by default. Channel bindings can be used to validate and enforce that one of the IP addresses for the host name actually matches the IP address of the peer.

Enabling this option may impact logon performance due to host name resolution, depending on the customer host name lookup configuration.

For information on Gateway Control, see Utilities.