516d5d1f9d
Tutorial on integrating LogicApps and RAFT webhooks to create issues in Github and send an e-mail with link to the issue Co-authored-by: stas <statis@microsoft.com> |
||
---|---|---|
Scripts | ||
ado | ||
cli | ||
docs | ||
src | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
GeoPol.xml | ||
LICENSE.txt | ||
NOTICE.md | ||
PRIVACY.md | ||
README.md | ||
SECURITY.md |
README.md
REST API Fuzz Testing (RAFT)
A self hosted REST API Fuzzing-As-A-Service platform
RAFT enables painless fuzzing of REST API's using multiple fuzzers in parallel. Using a single command line baked into your CI/CD pipeline developers can launch fuzz jobs against their services.
RAFT has first class integration with Microsoft's Research's RESTler, the first stateful, fuzzing tool designed to automatically test your REST API's driven by your swagger specification.
RAFT also supports ZAP from OWASP out of the box.
As a platform, RAFT is designed to host any API fuzzers that are packaged into a docker container. These can be configured and used in the system via configuration files and require no code changes to integrate.
Getting Started
This project is designed to run on Azure.
To deploy the service download the CLI release and run python raft.py service deploy
. See
the documentation for more details.
Once deployed, read about how to submit a job and use the samples to try out the service and fuzzers!
Documentation
Swagger Documentation
Once the service is created, you can examine the REST interface of the service by browsing to the swagger page at https://<deploymentName>-raft-apiservice.azurewebsites.net/swagger
Interesting in native code fuzzing?
Take a look at our sibling project OneFuzz
Microsoft Open Source Code of Conduct
https://opensource.microsoft.com/codeofconduct
Trademarks
Trademarks This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
Preferred Languages
We prefer all communications to be in English.