Too much data can be a good or bad thing.
Use Cases and Deployment Scope
We are using the product across the entire organization for all of our SQL database servers. We use it primarily as a compliance tool for reporting and HiTrust certification. Our organization standards mandate that any new SQL database being configured has the Imperva Data Security agent installed on the system. We also ensure that our systems are configured with failover so that we do not lose any audit data.
Pros
- The options available for auditing are outstanding.
- The system has very good reliability and tuning options for the agents on the servers.
- The data gathered is fantastic and presented in a format that is easily readable for auditors.
- For on prem usage our servers have had no issues. The Linux is extremely resilient and we have no issues with the boxes.
Cons
- Navigation of the menus can get confusing pretty quickly. Since there are so many, it is extremely easy to get lost. Almost too many options and data.
- Configuring the agents can be very difficult if you are new to it. Having to save after every single change made to an agent during a configuration can be very tedious. Also having to make sure certain options are checked off in two separate places for a single option is very annoying.
- Navigation of the menus is not always intuitive and not very obvious that the option you are looking change is located in that menu.
Likelihood to Recommend
Compliance to audits and HiTrust certification. It is key in ensuring that our audits are completed in a timely manner with no repeats of data requests and that we also are HiTrust certified at our organization. Personally while the data obfuscation is available I am not sure I would fully trust that the data is completely sanitized if need be. It's not against the Imperva product but more of issue of data being used.