-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fix Scope Down Statement Rule #88
Fix Scope Down Statement Rule #88
Conversation
/terratest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @RoseSecurity
These changes were released in v1.7.1. |
still the error exists inspite using 1.7.1 |
Thank you for trying it out @likhitha-ch. I have an updated pull request here to address this if you are interested in reviewing. |
Hi @RoseSecurity,
|
@likhitha-ch Have you tried setting rate_based_statement_rules = [
{
name = "rule-40"
action = "block"
priority = 40
statement = {
limit = 100
aggregate_key_type = "IP"
evaluation_window_sec = 300
scope_down_statement = {
byte_match_statement = {
positional_constraint = "STARTS_WITH"
search_string = "example-scope-down-statement"
field_to_match = {
uri_path = true
}
text_transformation = [
{
priority = 40
type = "NONE"
}
]
}
}
} |
@RoseSecurity yes this is working but evaluation window of 600sec is not accepting again facing the below error |
what
byte_match_statement
handling within scope-down rules to accurately query scope_down_statement parameters instead of the statement parameterswhy