Black Duck Continuous Dynamic vs w3af
Black Duck Continuous Dynamic
blackduck.comw3af
w3af.orgSide by side
| Figure | Black Duck Continuous Dynamic | w3af |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Dynamic Application Security Testing Software | 7.5 (#14) | 8.2 (#7) |
| Support | Black Duck security engineers provide issue guidance through the portal. | For installation issues, the guide directs users to create a ticket and include their Linux distribution, dependency-install script, pip freeze output, and Python version. |
Plans
Black Duck Continuous Dynamic
- Continuous Dynamic (custom quote)Priced on request
In their own words
Black Duck Continuous Dynamic
Black Duck Continuous Dynamic has no write-up on Specifiction yet; its figures are above.
w3af
w3af is a free, open-source web application security scanner for vulnerability assessments and penetration tests. It can identify more than 200 vulnerabilities, including cross-site scripting, SQL injection, and OS command injection. Its workflow starts with crawler plugins that find URLs and injection points, continues with audit plugins that check for vulnerabilities, and can use attack plugins to exploit findings. Other plugin types cover infrastructure detection, request and response analysis, output, brute force, request modification, and evasion.
Users can scan and analyze results in a GTK graphical interface or a console. Web application payloads can interact with Metasploit when an exploit provides exec() capability. Developers can use the REST API from development languages and run it in Docker; scripts and the API also support automation. The project documents Linux and macOS installation, including running in Docker without installing w3af dependencies. It is available for Linux, macOS, web, API, and self-hosted deployment. REST API traffic over HTTP is unencrypted, so the documentation recommends added protection such as an SSL proxy for publicly reachable deployments.