AquilaX API Security Scanner vs Automatic API Attack Tool

AquilaX API Security Scanner analyzes API specifications and probes running endpoints for security weaknesses. Its checks target the OWASP API Security Top 10, including broken authentication, object-level authorization problems, mass assignment, excessive data exposure, and rate-limiting gaps. Supported inputs include OpenAPI 3.x, Swagger 2.0, GraphQL schemas, gRPC/Protobuf, Postman collections, discovered URLs, REST APIs, and webhook endpoints. The API scanner is available on Premium and Ultimate; all plans include unlimited scans without scan quotas or per-scan fees. AquilaX lists more than 50 integrations, including GitHub, GitLab, Jira, Slack, Azure DevOps, Bitbucket, and REST API access. CI/CD and IDE connections include GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, CircleCI, Bitbucket Pipelines, TeamCity, VS Code, and JetBrains IDEs. On-premises deployment supports Docker and Docker Compose, air-gapped environments, Ubuntu 22.04 LTS or RHEL 9, and data sovereignty. AquilaX says source code is processed in isolated temporary environments, with only security findings retained and scan containers destroyed after analysis. It states that data in transit uses TLS 1.3 and stored findings and metadata use AES-256 encryption. Premium costs $19 a month per developer; Ultimate costs $99 a month per developer.

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.