The initial setup of the solution is simple. However, we have some problems with the capacity. There is a limitation in the amount of locally available storage. However, the limitation is mentioned in the documentation.

The deployment took four to five days.

The implementation time for Oracle Audit Vault varies based on customer needs and requirements. Typically, it can take a minimum of two weeks, but the process may extend up to six months or longer, depending on customization and additional features requested by the customer, such as integration with SysLog or other servers.

The initial setup is not complex at all and can be deployed in a hybrid environment, depending on the needs of different customers. The deployment took over a day.

to be honest the installation & configuration it's needs a lot of work and reading, the more server you have to audit the more complex and extra work you will have. 

The installation is handled by a different department, but I haven't received any complaints about it.

It is complex because there are two servers. It would be best to have one server to make it easy to configure and install. Currently, it is not at all easy because it is an appliance, but it is self-configured. When you run it, it configures on its own based on its need for shared memory for all other background processes. Because it's an appliance, you cannot modify it during the installation. Everything is done directly, which is a good idea because sometimes, a person can make some mistakes during the configuration.

Its deployment duration varies. Sometimes, it took me almost two weeks because of some issues. After I have installed the software on the server, they need to put it on the network. At the time of putting the software, many problems come out with security because you need to take care of the security between the servers and the network. It was not at all easy.

Initial setup is very simple. There are not many components. Our only worry was the collector process, which runs on the target environment. Also, management of the same is a bit tedious, as remote agent start/stop is not available.

This product is not very easy to set up. You set up separate machines and it's isolated from the production environment and the other system which you're auditing. After that, you just point the IP addresses on which production cybers are running. Then it starts monitoring them. 

Sometimes there have to be additional changes within the database, within the production server, and some other basic configurations. For example, in 12C you have unified audit trail, and in other versions of Oracle like 9-9, 10G, 11G, you don't have the unified auditing. Unified auditing in 12C is a bit complex so you have to configure it to log the traffic activities. Another example is doing what we call a 'petition auditing' whereby you use triggers to audit.

If a client wants to capture all database traffic to all the servers for both successful logins and unsuccessful logins and store a complete audit trail data and that cannot be tampered with by the administrators, this takes additional setup. Assigning user privileges can take some time to do correctly so users cannot misuse their privileges.

Generation of distributional reports, tracking the sign off of those reports, encryption of tentative data in the database all need to be configured since Oracle has other features such as Transparent Database Encryption, TDE. 

Because of my experience with the solution, I am able to deploy within three to five days. But the whole system needs to be considered. Machines must have enough processing power and the storage for the audit trail data because that data can grow rapidly if not monitored well. Storage can become a challenge. 

With deep knowledge and understanding of these technologies, I can seamlessly and quickly deploy the solution. It will be far more difficult for users who are not already familiar with the solution.

It has an appliance setup which is not supported on Amazon or any other third party cloud, making the process very cumbersome.

The initial setup was straightforward and easy.

We had problems installing the old version, and since it did not have a lot of resources, the setup took a few days, but there are a lot of radical changes in the new version. Audit Vault's own database and its own operating system come in a single .iso file. There is good documentation out there that describes the process step-by-step and you will not have much difficulty, even in the first installation.

The installation itself is quite straightforward, but the configuration does not happen at the same time. We have fine-tuned our configuration over the past year or two, which has reduced the high number of false positives. We now only receive clear, actionable alerts. Most of these kinds of tools require a lot of fine-tuning to be done, based on your environment. It all depends on how fast you can do it, based on your database requirements.

It took approximately three months to deploy this solution and bring it into production.

It was very straightforward to set up, not too complex.

It is a little bit complex. The installation, implementation and policy defining should be done by experienced technical staff.

The initial set up was straightforward. It wasn't challenging. The implementation strategy for new customers doesn't take long. 

Our strategy is to increase the value of the software.

Initial setup was not straightforward, because we should have considered the network environment when we decided the policy configuration. The complexity of AVDF depends on the system (network) environment. If the number of DBs to be protected is high, you should consider organizing the network environment.

This initial setup of this solution is straightforward.

Setting up the appliance for the first time can be a little bit difficult. Knowledge of Oracle database setup and use is required.

The installation took a blank server and installed Oracle Linux, Oracle Database 11.2.0.4, and the web-based application at once. Setting it up was an adventure and the documentation was poor.

I would say that the initial setup was of medium difficulty.

Installation and configuration of Oracle Audit Vault and Database Security is very simple and a server can be deployed in a matter of minutes once the media is in hand.

Initial setup was complicated. Earlier, when I started working on the product, at that time, there were a lot of bugs in it and even the support and documentation was also not available. Now, things are better but still sometimes a few of the installation steps create confusion.

The initial setup was a bit complex for versions 10-11. However, the setup for version 12 is straightforward.

The setup was complex because you have to understand which data needs protection.

Audit Vault was very easy to install, but not with the DB firewall. That's why we have dropped the DB firewall.

The setup for Audit Vault is relatively simple.

However, configuring personalized reports is a nasty task. There are many variables involved and the documentation is not very good. The way the reports can be personalized must be more visual and requires a drag-and-drop feature rather than creating it in a rudimentary manner.