Question & Answer
Question
We noticed Teradata failed login is not exported from collector to aggregator. Is this expected behavior ?
Answer
It is expected custom table is not included in the export. Teradata failed login is pull from database server via custom table and is not captured in the traffic via policy exception rules.
If you want to see custom table data on the aggregator, you can define custom table upload on the aggregator directly.
How to capture Teradata failed login events in Guardium?
If Teradata ATAP is used, failed login is captured by sniffer. In that case it would be contained in export.
Setup Teradata ATAP
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"10.1;10.1.2;10.1.3;10.1.4;9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22014213