Our clients use it to try to find errors in base code, and also to find how solutions work together.
I believe they have on-premise usage; they are local government, so they are not very used to using the cloud.
Our clients use it to try to find errors in base code, and also to find how solutions work together.
I believe they have on-premise usage; they are local government, so they are not very used to using the cloud.
I'm mainly working on the licensing side and not the technical side, so I don't get this kind of feedback.
Scalability, and it's a very powerful tool.
I believe there are improvements that can be made, but I'm not aware of those kinds of things.
It's stable.
For the market in Finland, when we are talking about a mid-size company, it equals a small company here in the USA, but they are mainly from 1,000 users to 10,000 users.
Tech support is responsive. With the local support I get all the help I need. I'm a former IBMer, so I know the right contacts, so it's quite simple to work.
I think it's a little bit complex, and that's quite a common issue with most of the IBM products.
Some of the customers are using office open-source tools, but most are not using a tool at all. So, that's the competition. Of course, they are thinking about return on investment because it's quite an expensive tool and they won't take it back.
It is used for a DevOps environment, to perform a security profile, a code profile assessment. When you are building your software code, before finishing the build process and deploying to production, we run AppScan to figure out any security vulnerabilities in the code. It's called static analysis of the code.
It decreases the operational risk, security risk, a lot. In fact, when we first used it, the number of vulnerability alerts generated by the tool was huge. As time goes on, we can decrease those vulnerabilities because we learn from it. So, in the next release of the software, or new software that we have to develop, we know upfront that we should take care of some of the characteristics of the software.
It highlights, with several grades of severity, the types of vulnerabilities, so we can focus on the most severe security vulnerabilities in the code.
One thing that we would like in this tool is that it keeps ahead of the security guys, because one big advantage of this tool is that it always offers updates. Security is a process, you mitigate a risk, but the malware guys, they're trying to find another security hole in your environment. And the technology is evolving. So new security vulnerabilities are in the software. The point is, I hope that IBM continue, in improving and launching new versions, new upgrades, that can mitigate those security risks.
That's the most important value. It's not the tool itself, but the continuous enhancement of the tool. That's why we recommended this tool.
It's pretty stable. No issues as far as I can remember.
It's scalable. In the beginning, we found some issues regarding installing the tool in an open-source Jenkins environment - Jenkins is a tool for open-source. Jenkins and other tools, they automate the process. Those tools call AppScan in a way to generate a proper time to do this. But after a couple of discussions, we solved the problem, so we don't have any issues anymore.
I think it is pretty good. They answer in a very fast manner.
It's pretty straightforward to install and use it.
One competitor that I remember, one of the last candidates in the evaluation process was Checkmarx. Those tools, especially from startups that come from Israel, they try to grab this market space that IBM dominates.
That's why they have to take care in terms of the price; the price model. But other than that, it would be unbeatable.
The most important criteria when selecting a vendor, first of all, is their capability to continuously invest in the development and enhancement of the software. We are in a very changing process, software is a very changing environment, in terms of the technology. If you develop a tool, launch this tool, but don't have enough commitment to upgrade, to continuously enhance, it's not worth it. That's why I think IBM has a good presence in this area.
My advice would be, don't see only the cost. Try to see the capability of the tools and, besides that, as I have stressed in this review, the capability of the vendor to invest in enhancing and mitigating the risks that will come. New risks, new threats, security threats, will appear. If you don't have a company that is continuously enhancing its software, there will be a problem.
I would rate this product a nine out of 10. The reason I don't give it a 10 is because AppScan is a little bit expensive. IBM needs to work a little bit on the pricing model, decreasing the license cost. But with the maintenance - and the maintenance is the most important, as I told you, because it has to continuously enhance the tool to mitigate the increasing malware in the future - IBM could recover the investment and meet their target margins in another way.
Unfortunately, there is a big discussion if it is very expensive, to use it or not, and there are competitors. I see competitors trying to grab this market.
But from the point of view of quality, very excellent quality, it's above all the tools that I have worked with.
I mainly use AppScan for vulnerability scanning and database bridging.
AppScan is too complicated and should be made more user-friendly.
I've been using HCL AppScan for three to four years.
AppScan is stable.
AppScan is scalable.
HCL's technical support is ok, but it could be faster and more responsive.
The initial setup was complex and took about a day and a half.
I would rate AppScan four out of ten.
IBM AppScan has made our work easy, as we can do four to five scans of websites at a time, which saves time when it comes to vulnerability.
Many features are valuable but some features stand out, like using our own scripts, and capturing the authentication.
Yes, sometimes we encounter stability issues.
Yes, sometimes we encounter scalability issues.
I would rate tech support a seven out of 10.
Yes. We switched because they made our work easier, with fewer false positives.
It was simple, once we watched many video tutorials and read PDFs to learn about it.
Yes, I used with Acunetix and open source tools.
It is used as a last check before moving code to production. Therefore, it is used as a developer tool.
With AppScan, we are now deploying less defects to production.
We leverage it as a quality check against code.
No stability issues.
We have a strong partnership with IBM. Their tech support is very knowledgeable.
We were using something else (a competing product of IBM), but we switched to AppScan because it is reliable.
Most important criteria when selecting a vendor: At the end of the day, it would have to be the support and relationship. There are a lot of smart people out there building products which do things. However, not everyone can use them, and without having someone to call, it is sort of its own disadvantage.
External and internal web application vulnerability scan.
AppScan seems to be very good at detecting reflected XSS vulnerabilities. This increases the security of web applications that are in operation.
It would be nice to be able to specify the parameter values used in the login sequence function.
The primary use case is to detect time-based Blind SQL Injection attacks, as well as Error-Based Injection attacks. The SQL injection attack is my favorite and I have more expertise in this vulnerability.
This solution saves us time due to the low number of false positives detected. Other scanners have an issue with respect to reporting false positives.
The most valuable feature is that it achieves a very low false-positive detection rate.
While I did not identify any specific bugs in this application. I did find that sometimes a restart was needed to deal with unresponsiveness means when AppScan is in a hang situation, this happens usually when you select a large number of sources.
IBM Security AppScan needs to add performance optimization for quickly scanning the target web applications.
We previously used Burp Suite. This application is best for static scanning.
Complex
We also evaluated Acunetix and Nexpose.
The benefits are that we that we can find security vulnerabilities fast, get that back to development teams, and report on those. They can then act, fix the issues, and we'll have a secure code in place.
It is easy it is to use. It is quick to find things, because of the code scanning tools. It's quite simple to use and it is very good the way it reports the findings.
We would like to be able to integrate to some of the other tools that we are using. That would be great. We would like to integrate with some of the other reporting tools that we're planning to use in the future.
I think it's quite stable.
So far scalability is pretty good.
We're really happy with technical support. They are great and very responsive.
I was not involved in the initial setup.
What I look for most in a vendor is the product, the offer, the service, the vendor service, and after sale support.
I would definitely recommend this product.