-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MEDIUM: site: add attack_threshold+immediate_block #210
MEDIUM: site: add attack_threshold+immediate_block #210
Conversation
This commit brings in the latest improvements that are in go-sigsci 0.1.19 (to be released), which allows for updating the attack thresholds and/or setting the immediate block functionality. attack_threshold can be set multiple times each for the various intervals: 1, 10, 60 (in minutes). immediate_block is a bool, which will instruct the WAF to immediately block requests with attack signals. This commit depends on go-sigsci#59 as well as a new version being issued.
@daniel-corbett I tagged and released Could you run a couple of commands and push up the results?
|
Done both - still seeing errors in the validation. Is there something else that needs to be done? |
@daniel-corbett the problem is likely that the build is installing We'll probably need to update the build to use the version of the provider from the current branch, rather than the registry. |
@shawnps - i think i fixed it. |
Thanks @daniel-corbett -- LGTM |
This commit brings in the latest improvements that are in go-sigsci 0.1.19 (to be released), which allows for updating the attack thresholds and/or setting the immediate block functionality.
attack_threshold can be set multiple times each for the various intervals: 1, 10, 60 (in minutes).
immediate_block is a bool, which will instruct the WAF to immediately block requests with attack signals.
This commit depends on signalsciences/go-sigsci#59 as well as a new version being issued.