The August Guardium Virtual User Group topic was Guardium Insights, focused on what's new in V3.4, presented by Matt Simons, IBM Program Director, Product Management for Data Security. The slide deck is attached.
Discussion Summary
Matt Simons gave an overview of Guardium Insights V3.4. Here are the main features:
-
The new system health dashboard centralizes information on the health of the full stack GI deployment(s), including OpenShift, in one location.
-
There's a new query monitor to see the status and progress of running jobs, cancel them if needed and help prevent system performance issues.
-
In the backend, we now store data in a new data warehouse schema that results in improvements for reporting and ingestion times.
-
We added a key feature from GDP, which we call external enrichment: you can bring in custom data from somewhere else and join it to native tables in GI to report on that.
-
You can now generate tasks out of customer-defined workflows.
-
We added a new way to globally filter your dashboards.
-
We now offer timestamp rollup for more usable reports; for a given report, you can choose which parts of the timestamp you want to pull out.
-
We now have integration with slack notifications.
-
Our machine learning model for risk event categorization has been enhanced.
-
We now have a compliance journey for GDPR.
-
GI offers various deployment options, including the first non-OCP version, which is EKS on AWS.
Q: What OCP level does V3.4 support?
A: 4.14 is the recommendation.
Q: There's slack integration...what about Teams?
A: We are working on it, in test now.
Q: Categorization has created a great deal of confusion for our customers and end users. Most common question, "How does IBM determine this is a Data Leak?" An unacceptable answer is "There's a magic genie inside of the code that decided that it was."
A: Yes, you're right. We're looking forward to your feedback on the new experience.
Q: Do you have a plan in future to certify and support GI product on odd release of OCP version like 4.15?
A: We don't; we are standardized on OpenShift extended support releases. We support the odd number releases once the plus one even version is certified.
Q: Is there any direction in the future for applying filters to chart builds? Example use case: Isolating specific data sources to specific customer roles and allowing them to build charts and graphs that only applies to *their* data source data.
A: Yes! Data level security is a requirement.
Q: So Edge will not be OCP? What's relationship of Edge and GI?
A: Edge will not be exclusively OCP, it will be 'bring your own Kubernetes.'
Edge is the satellite world from which you'll be able to do remote activities separate from mothership of GI regardless of where it runs.
--------
Next VUG meeting: Sept 24
--------