The initial setup or installation of HCL AppScan is easy.

Maybe two or three hours are required to deploy, install, and configure the product.

About seven or eight engineers and architects may be required to deploy the product.

The solution is deployed on the cloud.

The initial setup is very straightforward. Moreover, it's actually a quite nice solution because we don't require a lot of technical staff for deployment and maintenance.

The initial setup is very easy. The deployment takes a couple of weeks including customer training as well. I rate it ten out of ten.

The initial setup is not straightforward. It involved a couple of tweaks and changes within the environment itself. A couple of reinstallations were also required for us to get it working. It was not a click-and-run kind of a product.

Given that we have been using HCL AppScan for many years, I think the setup process is not difficult at all. Sometimes, some issues stop or prevent my company from moving forward with the product's setup phase. We have to call HCL's support team and engage in long discussions to smoothly carry out the setup phase. In general, the product's setup phase is not difficult in our company.

The solution is deployed on an on-premises model. The licenses for the solution are available only on cloud deployments nowadays.

The solution is already installed in our environment. Every time a new release or software comes out from HCL, our company does a scan, which takes maybe a day or two.

The initial setup process is complex. The time taken depends on specific use cases and integration requirements. It might take ten days to a month to complete.

It is easy to implement and set up for users.

The initial setup with most of the products, particularly the Burp Suite and the HCL AppScan, is straightforward. The only difference is that when it is customized to your specific requirements, that is when the key part comes into play. We have to engage the professional services of the product team, or the vendor team, which is where the headache begins. That is a common challenge shared by the all vendor team.

Deployment and installation of AppScan take approximately three hours, or less than that if you have all of the necessary prerequisites, hardware, a database, and everything is in place, then three hours is all you need.

We put our application into maintenance mode during the version upgrade.

We require one person for the administration of this product.

The initial setup is not difficult. I rate the ease of setup a seven out of ten.

The solution is easy to install. I would rate the product's setup between six to seven out of ten. The deployment time depends on the applications that need to be scanned. We have a development and operations team to take care of the product's maintenance. 

The initial setup is straightforward. This is a great advantage of HCL, as we can just download, install and run it to identify potential vulnerabilities. Furthermore, the graphical user interface is also simplified.

The implementation didn't take a lot of time; setting up the cloud was just a matter of making my account and getting familiar with the features. After that, we were all logged in and ready to go with no major changes required.

We do not have to manage the setup. It is a managed cloud offering. There is no implementation process. We just need to upload the applications. It doesn't take any time at all. Everything is automatic. 

The installation was easy for me. It took a few hours. A senior employee helped me deploy the tool. The solution was deployed on the cloud.

The initial setup of HCL AppScan is easy.

HCL AppScan is easy to deploy and can be done in one to two hours. 

I didn't really do the actual setup once it got moved into the cloud. I don't know how easy the cloud set up was. However, it's my understanding that it is now potentially easier than it was before, which wasn't too bad. 

There is a licensing partner. Sometimes, it is required to install a server. I must remove that license and then eject a new one on a different server. It becomes a bit harder for beginners if they do not have enough experience to install Zoho software.

Deployment takes around an hour, and one person can do it.

I rate the initial setup a six and a half out of ten, where one is difficult and ten is easy.

I didn't do the work but I directed it.

There were a couple of steps where we had to have some help. But at the same time, we just put in an engagement for a Professional Services to do it quicker, do the integration, to make it tighter for us. We're just waiting for the final part of that to be signed so we can actually move forward.

The initial setup is pretty simple and straightforward. It's not an overly complex or difficult process. 

It took about one day to deploy the solution.

I give the initial setup a seven out of ten. The implementation took a few weeks.

The initial setup was complex and took about a day and a half.

It's complex. Our main client is Citigroup. It's complicated because of the size of the client and all of the internal processes. So it's really a pain, not to blame IBM, not to blame us, not to blame them, but all of the ecosystem is complex.

Installation is pretty straightforward. Deployment only took a day or two.

I think it's a little bit complex, and that's quite a common issue with most of the IBM products.

It's pretty straightforward to install and use it.

It was simple, once we watched many video tutorials and read PDFs to learn about it.

Complex

I was not involved in the initial setup.

The initial setup is not that complex.

This particular product is one of the easier products to set up.