Automatic API Attack Tool vs Indusface WAS
Automatic API Attack Tool
github.comIndusface WAS
indusface.comSide by side
| Figure | Automatic API Attack Tool | Indusface WAS |
|---|---|---|
| Price from | Free | $49.92/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| Linux | Yes | — |
| Plans published | 1 | 4 |
| Spec score · API Security Testing Software | 8.2 (#7) | 8.0 (#10) |
| Support | The README directs users to source code documentation and gives an email address for questions; it directs bug reports to GitHub Issues. | WAS support is available 24×7×365 by email, phone, and chat on Premium; the page lists unlimited email support and business-hours on-call support for WAS. |
Plans
Indusface WAS
- Advance$59 a month
- Advance$599 a year
- MSSP EditionPriced on request
- PremiumPriced on request
In their own words
Automatic API Attack Tool
Automatic API Attack Tool is a free, MIT-licensed, self-hosted security tool for Windows and Linux. It takes a Swagger 2.0 API specification in JSON or YAML and generates and runs attacks from that definition. Fuzzing scenarios send generated values within the specification’s boundaries and values that violate them, including random invalid values for checked parameters. The project describes extensibility for attack types such as illegal resource access, XSS, SQL injection, and RFI, and supports authorization and input-validation testing. It reports request details, expected-response checks, and a summary. TestNG results are written under build/testng-results, while bad requests are saved in a bad_requests folder. Optional host and port arguments support routing through a proxy. The project is intended for CI/CD and describes scheduled or code-push Jenkins jobs. Running it requires Java 8 or higher and Gradle. Windows build instructions use gradlew.bat build; Linux instructions create an executable from a shell script and the JAR. API discovery is not included.
Indusface WAS
Indusface WAS has no write-up on Specifiction yet; its figures are above.