An automated API security testing tool that generates and runs fuzzing attacks based on an OpenAPI/Swagger specification.
Imperva's Automatic API Attack Tool is an open-source security testing utility that automatically generates and executes fuzzing attacks against APIs based on their OpenAPI/Swagger specifications. It helps identify vulnerabilities by injecting malformed or out-of-spec inputs into API endpoints and validating responses. The tool is designed to run without manual intervention, making it suitable for integration into CI/CD pipelines.
API developers, security engineers, and organizations that need to regularly test their public or internal APIs for security vulnerabilities and implementation correctness.
Developers choose this tool for its ability to automatically generate targeted attacks from API specs, its extensibility for custom security vectors, and its seamless integration into automated testing workflows, providing proactive security validation.
Imperva's customizable API attack tool takes an API specification as an input, generates and runs attacks that are based on it as an output.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates both positive and negative attack scenarios automatically from Swagger 2.0 specs, with no human intervention, as highlighted in the README's description of injecting cleverly generated values.
Designed for integration into automated workflows like Jenkins, with TestNG reporting for structured results and the ability to run nightly or post-deployment scans.
Uses TestNG to log all request/response details, stores failed requests in a 'bad_requests' folder, and provides command-line summaries for easy analysis.
Can be extended to test for XSS, SQLi, RFI, and illegal resource access, with customizable validation for response codes via command-line overrides.
Only supports Swagger 2.0; lacks native support for OpenAPI 3.0 or other modern formats, which restricts its use with newer API ecosystems without conversion.
Requires Java 8 or higher and Gradle for building and running, adding setup complexity and potential compatibility issues for teams using other tech stacks.
The README admits an 'Ongoing Effort' to migrate other scenarios, implying the open-source version may lack some advanced attack vectors available in proprietary tools.