Imperva is a highly technical solution to set up. It took about two weeks to set it up the first time, but I think nowadays, people could set up Imperva in a week. There has been some improvement. We don't have a lot of technically proficient people in our region, so I've been trying to drive up the competence and technical certification. 

More training in Africa would help increase those skills. If you're in Zambia, you need to hire someone from South Africa or the United Arab Emirates to come in and set it up, so you have to pay the cost of transporting that person. Having a network of locally certified partners would be lucrative for Imperva and better for the customers. 

The the setup itself is not too complex, it's conceptual. You have to understand at least the basics of the database. That's it. You don't have to be a DB admin, however, as a security engineer, you just need some small knowledge of a database, for example, what the database is, what the table is, et cetera.

The initial setup of Imperva SecureSphere Database Security is straightforward if you have the experience. If you are able to configure the solution well it can be implemented in one day.

Imperva SecureSphere Database Security was simple for our engineers to implement. It is easier than other similar solutions. The full deployment took a few weeks.

Setting up Imperva SecureSphere was very simple, and configuration was easy.

The initial setup is actually quite easy. It's not something hard to do, but having some experience with the product is helpful.

If it's only the deployment, it takes around two to three days. But if we consider tuning and ongoing processes, the time for deployment varies.

The initial setup was straightforward, and the deployment took between one and two weeks.

The initial setup was straightforward. We normally use Imperva's professional services, so that makes it very easy to deploy. We build on the knowledge gained in previous deployments, which makes it easier still. 

In the deployment, we want to get up as soon as possible. We know that for a typical deployment that it is usually two weeks. 

The initial setup was straightforward. At first, we were unable to find the application user tracking and our main target was to track specific user privileges, activity and who was making changes inside the database from the console. It was a minor setback.

There are two types of deployment. The first one is for the solution to integrate the database which took about three days. For the usage, identifying the queries and creating rules, it took longer. The whole was complete within 15 days or 20 days, I think.

We have three operators and two administrators. The administrator role is to make the policies, install the agent, do the integration with the gateway and enable the auditing on the specific tables and the specific columns.

The operator generates reports on users and activity based on the areas we need to monitor. If a user is doing any activity outside of the normal time, the operator's responsibility is to report users to the DVR admin and the security feed.

One guy was enough for the deployment. We have only integrated one database, so in our environment is simple.

Another thing I want to highlight is that you can adjust the permissions from anywhere.

The initial setup was reasonably straightforward. The deployment took about three months and we had some external assistance. 

Setup was complex. We had to deploy hundreds of gateway appliances to gather audit data and deploy thousands of agents to different OSs. This was not an easy task, as there were no simple solutions to do that. There were also challenges to configuring auditing rules and monitoring rules to work with all kinds of databases and different kind of requirements relating to them.

The initial setup was straightforward. Each and every step is clearly mentioned in the manual. After the initial setup, it becomes a bit tricky.

We are a large organization with about 100 critical heterogeneous database servers. This means that one configuration does not fit all, and that made the implementation very complex. Combined with protection of sensitive information that could be logged by the solution.

While I didn't handle the initial deployment myself, from the training I have done, it is my understanding that the implementation process would not be that hard. 

I'm not sure how many people were involved in the deployment. 

I handle any maintenance myself with the sales provider. There might be six people available to maintain the product. There would be about three from the customer side and two from the service provider's side.

The initial setup and configuration for this solution were very simple and straightforward.

Deployment in our environment took approximately one week. We begin by deploying it in a test environment. After performing some tests, we moved it to the operational environment.

Two technical staff are required for deployment and maintenance, and we have about six people, in different roles, who manage this solution.

The installation was quite complex. We had to integrated lots of external systems in order to make it work right.

The initial setup was easy, but some of the specific requirements we had required some work. Deploying the hardware during the initial setup did not require and specific customisation for our organisation. The audit policies and assessments obviously did require customisation, but it was relatively simple. Later on, we did find some issues that were due to the setup of the site hierarchy that was not brought to our attention until one to two years later.

The setup can be a little complicated.

Complexity really depends on the client's environment, but I would say the initial set up for basic deployment of the components should take roughly six working days. It has to be integrated with everything. Installing links to all the other databases could take maybe another 10 work days, so around two weeks. I do the deployment. 

The initial setup is moderately difficult. You have to understand the database and how the database communicates and also some knowledge about the platform. For example, if you have got the Unix environment you have got to understand how to work with that together with the product.  

The solution is very simple and straightforward. It's not too difficult or complex. 

It is straightforward, but it depends on the organizational policies and rules in terms of the infrastructure. For example, when you deploy it in an environment like Oracle, it is probably fine, but in other environments like Cisco, there could be some issues that you have to troubleshoot. It is more of an infrastructural or environmental issue.

We started with the PoC. It was implemented within two days. We are now doing monitoring to ensure everything is still fine.

A bit complex, but following the instructions and the manual guide is enough for the initial setup. A little knowledge helps.

Setup is actually complex due to the nature of the product and needs deep knowledge of the solution to get things working with minor effort. If you don't know exactly what kind of solution are you deploying or even the installation steps to get the environment fully working, you won't be able to install it easily.

Initial setup was straightforward and it was simple/easy to install and customize.

Initial setup was complex, but security is not that easy to be figured out in simple clicks, so I guess it’s okay.

It is very easy and very straightforward. There are no complications.

As mentioned above, Imperva was already set up in our Enterprise environment and we only had to add on the Database Assessment module license to our setup.

This is a complex system, and all other in the same league are just as complex. There are no workarounds to simplify it.

The initial setup was really easy. This product has a friendly wizard and in a few simple steps, we implemented it without troubles.

The initial setup for this solution is very easy. Just start it up, log in, and the instructions are there. It is launched from an FTP server and takes four or five hours.

I supported NGN when SecureSphere was set up. Although I only experienced this setup process once, I can now setup SecureSphere DAM and agents on my own. I mean, it was easy and feasible with guidance.

No issues noted in the implementation reports.

The initial setup for this solution is straightforward.

I am not using the entire solution, so the deployment time was very short. There were five people involved in the installation.

The initial setup of this solution is complex. However, I understand the complexity.

The length of the time it takes for deployment depends on the customer and their environment. It can take up to three months.

The installation is straightforward.

The initial setup is not straightforward for a single person or IT administrator. However, when many IT administrators get together then they can resolve all of the issues.

The initial setup is easy. It took us four weeks to deploy it.

The setup was pretty straightforward as right away, I was very familiar with the architecture.

The initial setup was very straightforward; not complex at all.

Deployment time varies, but in terms of implementation, it's a very good product. There is no hectic environment during the implementation. It is a very straightforward implementation.

The initial setup was really easy. It took us two hours to deploy. 

Initial setup was pretty straightforward.

The initial setup was straightforward.

Initial setup was straighforward.