Repulsive Grizzly是一个应用层DoS测试框架

网友投稿 676 2022-10-25

Repulsive Grizzly是一个应用层DoS测试框架

Repulsive Grizzly是一个应用层DoS测试框架

Repulsive Grizzly

Application Layer DoS Testing Framework

What is Repulsive Grizzly?

Repulsive Grizzly is an application layer load testing framework specifically designed to support high throughput and sophisticated request types. Repulsive Grizzly can help you confirm application layer Denial of Service (DoS) by running your test at a higher concurrency with other features such as session round robining to help you bypass certain rate limiters or web application firewalls.

Why is Repulsive Grizzly Different?

The main difference between Repulsive Grizzly and other load testing tools is we're specifically focused on providing a framework that makes Application Denial of Service testing easier. Some features that are useful in Repulsive Grizzly include:

Optional support to run tests within Cloudy Kraken a red team orchestration framework that can help you scale up your test across multiple datacenters or regionsLogging messages to centralized Amazon SNS queue for aggregation during larger exercises such as running a multiple agent test with Cloudy KrakenAbility to round robin authentication objects using placeholders in headers, cookies, and/or POST:GET:PUT:DELETE dataAbility to round robin target URLs or fix one URL per attack agentSanity check logic to confirm your environment is stable enough to begin the testLeverages Eventlet for high concurrency, allowing you to scale up to > 300 threads per repulsive grizzly agentProvides TTL as well as start time so multiple agent scans conducted with Cloudy Kraken start and stop at the same timeHTTP Proxy support for troubleshootingGrizzly Dashboard to aggregate and graph http status codes while you run multi agent tests

How Does Repulsive Grizzly Perform Tests?

The typical execution of Repulsive Grizzly is as follows:

Validate the commands.json file for good settingsSleep until start time is triggeredValidate that the sanity check URL returns a HTTP 200Build Eventlet Pool of request objects based on the commands fileBegin execution of the testLog messages to console and Amazon SNS messaging queue (if configured)Each iteration check TTL and one triggered, exit the test

Getting Started

Wiki

What is Skunkworks?

Skunkworks projects are not fully supported unlike other projects we open source. We are leveraging the Skunkworks project to demonstrate one way engineers can approach application layer load testing. We'd be happy to accept Pull Requests for bug fixes or features.

Release History

Version 1.0 - July 29, 2017

Initial Release

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:C++核心准则边译边学-F.5 如果函数非常小而且时间敏感,将其定义为inline
下一篇:C++核心准则C.50:如果在构造过程中需要“虚行为”,使用工厂函数
相关文章

 发表评论

暂时没有评论,来抢沙发吧~