Teradata Generic Security Services | Teradata Vantage - Setting Up TDGSS - Analytics Database - Teradata Vantage

Security Administration

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
2024-04-05
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

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

Additional setup of TDGSS configuration files may be required on Analytics Database nodes, and Business Continuity Manager, depending on the features you implement.

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 Business Continuity Manager and the gateway, enable channel bindings on the managed Vantage servers. Use Gateway Control to enable channel binding:

gtwcontrol -j yes

The domain component (DC) of a Business Continuity Manager certificate for the PROXY mechanism must contain the name of the machine where Business Continuity Manager runs, but the name is not validated by default. Use channel bindings to validate and enforce that one of the IP addresses for the host name 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 Teradata Vantage™ - Database Utilities, B035-1102.