IBM Security Join our 16,000+ members as we work together to overcome the toughest challenges of cybersecurity. Join the Community
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.
Thank you! It looks like an IDEA/RFE was just created and I voted for it!
Brand Technical Specialist
Global Sales, Financial Services
1 469 796 8337 Mobile
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?
NONCONFIDENTIAL // EXTERNAL
Then I am having an issue where Client IP is not mapping over cleanly, because we have a bunch of empty blanks in our Client IP field. Question, is the Sender IP field being mapped with this information?
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.
PERSONAL/NONWORK // EXTERNAL
We are on 3.2.4. Alright, we will upgrade.