Logons that Cannot Follow Security Policy | Teradata Vantage - Auditing Logons by Clients that Cannot Automatically Follow Security Policy - 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
2023-11-02
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

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.

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