I have seen that the tool's installation phase has some problems regarding the versions, specifically the version of SQL. Trustwave DbProtect doesn't accept some versions of SQL. Some credentials when you are installing give some problems, but all of them did pass through the installation phase but gave a certain amount of hard work to be done during the installation phase. The aforementioned area needs to be considered for improvement.

The pain points with Trustwave DbProtect were about the installation and problems with the different versions not being accepted. A more compatible version of the product with other databases and operating systems should be possible.

As the product is quite old, it needs to be migrated to more up-to-date solutions. However, this tends to take a long time and it would be very convenient if it could be done more quickly. The other main disadvantage is that the product does not have encryption or data masking, unlike other companies' versions.

In the next release, I would like to see the return of support for target databases that the product has discontinued support for.

I think that they can do a lot more in terms of being able to control, or enforce policy, on a database. Right now they are really amazing when it comes to monitoring, but for control it is limited. I can see exactly what is going on, but I can't take action. This is true for the competition, as well.

I would like to see more coordination for incident response. We have not been able to integrate this product with a lot of standard incident response solutions, so an open API would help in this regard. Today we have to be able to take action within seconds, and this has to be done through talking to other solutions.

I think that it would also be good if they had a network-based solution because what they have right now is an endpoint-based solution. Adding this would allow them to compete better.

A better interface to understand what network is going to be scanned.

Also, when we had two instances where we thought that the scheduled scanning was turned off and it went active, causing some network issues.

Asset Management, Analytics, and Reporting. The reason why these need room for improvement is that some assets in the report sometimes report the wrong operating system names. Therefore, they give slightly inaccurate results.

Its improvement levels are not technically related, but rather marketing related.

They need a better study of the needs of other markets with respect to DbProtect. They can't just hope that a DbProtect suite made for US markets will also fit into an African market. The market indices are not always the same.