With Testing Time Control, Impart Security has built an industry first way to test rate limiting rules. Testing time control is an innovation from Impart that can dynamically adjust system clocks in order to simulate test requests coming from different times. This helps security teams drastically reduce the time spent tuning WAF rate limiting rules and get to blocking mode in production faster.
For most security teams, rate Limiting policies are normally tested manually by security engineering teams using cURL scripts. If they want to test a rate limiting policy that spans 24 hours, then they would send one set of test requests on one day, then have to wait for 24 hours to elapse before second another set of test requests.
With Testing Time Control, Security teams can now specify a delay between different test messages. When the tests run, Testing Time Control adjusts application clocks forward in time to account for the specified delays, so that test messages can be sent immediately without waiting for the full time delay to elapse.
This enhancement makes it easier for security teams to
✅ Simulate and test low and slow attacks detections in seconds, not weeks
✅ More rapidly gain confidence in rate limiting rules and policies
✅ Get to blocking mode in production more quickly
Why wait weeks to simulate threats manually?
Impart’s Testing Time ContTime Control’s configurable internal timing mechanism accelerates your testing cycles, giving you immediate feedback to optimize your defenses.
Discover how Time Control can transform your detection workflows: try.imp.art
*** This is a Security Bloggers Network syndicated blog from Impart Security Blog authored by Impart Security Blog. Read the original post at: https://www.impart.security/blog/test-low-and-slow-attack-detections-in-seconds-with-testing-time-control