IBM Security Guardium

Analyzed Client IP is not available in Guardium Insights, which is a major issue when you utilize ATAP, because only Analyzed Client IP is populated with a valid client IP.  This is a major oversight that cripples Guardium Insights for any customer using ATAP.

Analyzed Client IP is not available in Guardium Insights, which is a major issue when you utilize ATAP, because only Analyzed Client IP is populated with a valid client IP.  This is a major oversight that cripples Guardium Insights for any customer using ATAP.

Hey Robert.  Analyzed Client IP gets mapped to Client IP field in GI when we do the data mart extract on the collectors.  So the Analyzed Client IP is present in GI, but we need to do a better job communicating that this mapping happened.  I've opened bug to get our tooltip updated to communicate this mapping.  It'll say something like: "Client IP address. Note: 'Analyzed Client IP Address' is automatically mapped to this field."  Do you think this will fix the miscommunication for other customers?

Analyzed Client IP is not available in Guardium Insights, which is a major issue when you utilize ATAP, because only Analyzed Client IP is populated with a valid client IP.  This is a major oversight that cripples Guardium Insights for any customer using ATAP.

Hey Robert.  Analyzed Client IP gets mapped to Client IP field in GI when we do the data mart extract on the collectors.  So the Analyzed Client IP is present in GI, but we need to do a better job communicating that this mapping happened.  I've opened bug to get our tooltip updated to communicate this mapping.  It'll say something like: "Client IP address. Note: 'Analyzed Client IP Address' is automatically mapped to this field."  Do you think this will fix the miscommunication for other customers?

Analyzed Client IP is not available in Guardium Insights, which is a major issue when you utilize ATAP, because only Analyzed Client IP is populated with a valid client IP.  This is a major oversight that cripples Guardium Insights for any customer using ATAP.

There was a bug that was fixed in 3.2.5 where the Client IP was not being populating in GI.  Which version are you on now?  You may be hitting that same bug.

Hey Robert.  Analyzed Client IP gets mapped to Client IP field in GI when we do the data mart extract on the collectors.  So the Analyzed Client IP is present in GI, but we need to do a better job communicating that this mapping happened.  I've opened bug to get our tooltip updated to communicate this mapping.  It'll say something like: "Client IP address. Note: 'Analyzed Client IP Address' is automatically mapped to this field."  Do you think this will fix the miscommunication for other customers?

Analyzed Client IP is not available in Guardium Insights, which is a major issue when you utilize ATAP, because only Analyzed Client IP is populated with a valid client IP.  This is a major oversight that cripples Guardium Insights for any customer using ATAP.