What is our primary use case?
The primary use cases for IBM Security Guardium include onboarding and offboarding of the servers and working on alerts, such as troubleshooting if any S-TAP goes down. We also have Sonar, which means Imperva DSF. We evaluate the reports or logs, and we set up a justify workflow there. We have set up alerts on the basis of logs; if we get many failed logins, high failed logins, or high SQL errors, then we get the alerts. I'm working on those alerts as well.
For real-time alerts in the alerter, we set up multiple types of alerts such as high failed logins in IBM Security Guardium. We have set up one group, and in that group, we mention users of a particular DB. If any other user tries to access or run any command, then we get the alert on a real-time basis. We then reach out to the server-side or DB team to evaluate those alerts.
In IBM Security Guardium, we use data discovery to discover the complete detail of the databases, which helps us understand the database and all the required details. We use data classification jobs for sensitive information, which run on the basis of data sources. We run the data classification job on the basis of data sources, and we get all the table names and column names, after which we classify them as critical or not.
We use a PowerShell script for some parts of running the data mart jobs in IBM Security Guardium. We have added multiple functionalities in that PowerShell script. For example, four or five months ago, we needed to migrate our data source user into CyberArk. It was very hard to replace the data source setting and add the users one by one because we have a very large environment here in MetLife. So, we added an API in the same script, and through that script, we replaced all the data source users.
What is most valuable?
In IBM Security Guardium, Sniffer is the main feature, which makes it very special because Sniffer filters out the logs on the basis of policies. In policies, we define what we want to capture. Sniffer is the main and most important part of IBM Security Guardium.
What needs improvement?
IBM Security Guardium can be improved in terms of several aspects. One is for the inspection engine. They define in the documentation that the inspection engines are auto-discover, but when we try to discover them, they are not discovered fully. They skip some of the databases. In this scenario, they need to work on this so that we can capture the complete database logs from any server.
Policies are another area that needs improvement. We used some skip-logging policies for particular commands in IBM Security Guardium. We have applied the whitelisting in our environment. We have created one group and defined everything in that group, but when we check the logs, those logs are still present. We have worked multiple times with IBM on this issue.
To capture the logs from Azure servers and cloud servers, we require a secondary tool. If they combined something and built functionality to capture cloud server logs within IBM Security Guardium, that would be beneficial. The license cost would be different, but we could capture the logs in the same environment. They could also provide more policies or compliances for users. IBM is working on an AI tool to replace the complete IBM Security Guardium product. According to documentation, IBM Security Guardium might be replaced by an AI-based solution in the next five to ten years.
For how long have I used the solution?
I have been using IBM Security Guardium for more than four years.
How are customer service and support?
IBM support is good. If you raise an issue, they will respond accordingly. This is also good compared to other products' support. These are some of the points that make IBM Security Guardium superior in the market right now.
How would you rate customer service and support?
How was the initial setup?
The initial setup of IBM Security Guardium is not complex; it is easy.
What's my experience with pricing, setup cost, and licensing?
Pricing for IBM Security Guardium is very high. When comparing it in the market, IBM Security Guardium is significantly higher than other tools such as Imperva DSF. Imperva SecureSphere is less expensive compared to IBM Security Guardium.
What other advice do I have?
I am still working on IBM Security Guardium.
I have not worked with IBM Security Guardium dashboards because we have Imperva J Sonar. We have complete data of IBM Security Guardium. We send all the data in Imperva J Sonar data mart jobs and set up the dashboard there. In IBM Security Guardium, there is a limitation of storing data. In collectors, we store a minimum time of data, approximately 15 to 30 days, due to high login activities. That is why we send all the data to the data mart in Imperva J Sonar. We do analysis there, where the purge time is in months, so we can analyze the last year's complete data.
I use the feature for real-time alerts in IBM Security Guardium and work simultaneously with IBM Security Guardium and SonarQube. My SonarQube is on-premises. I work with IBM Security Guardium mainly and with other products as well.
I rate IBM Security Guardium 4.5 out of 5.
Which deployment model are you using for this solution?
On-premises