Logons that Cannot Follow Security Policy | Teradata Vantage - 17.10 - Auditing Logons by Clients that Cannot Automatically Follow Security Policy - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Administration
Security
Publication ID
B035-1100-171K
Language
English (United States)

The Teradata Vantage gateway can be configured to audit your system to identify the client interfaces or proxies that cannot automatically follow security policy. These are the client interfaces or proxies that need to be manually configured, upgraded, or replaced if RequireConfidentiality is to be set or network security policy is to be used. To audit for this, use the Gateway Control --secpcynotsupported log= flag to enable logging. For more information, see Teradata Vantage™ - Database Utilities, B035-1102 and Configuring the Gateway to Allow Logons from Older Interfaces or Proxies.

About the Default Setting for --secpcynotsupported log

The default setting for the --secpcynotsupported log flag is no, which means the gateway does not log a message to the gateway log files to identify older clients or proxies that are unable to automatically support security policy. To restore the default setting, use:

gtwcontrol --secpcynotsupported log=no