Packages
PackagesGroups
Get a WAF rule group
Update a WAF rule group
ModelsExpand Collapse
Group { id, description, mode, 5 more }
mode: "on" or "off"Defines the state of the rules contained in the rule group. When on, the rules in the group are configurable/usable.
Defines the state of the rules contained in the rule group. When on, the rules in the group are configurable/usable.
PackagesRules
ModelsExpand Collapse
RuleListResponse = { id, allowed_modes, description, 4 more } or { id, allowed_modes, default_mode, 5 more } or { id, allowed_modes, description, 4 more } When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
WAFManagedRulesAnomalyRule { id, allowed_modes, description, 4 more } When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
WAFManagedRulesTraditionalDenyRule { id, allowed_modes, default_mode, 5 more } When triggered, traditional WAF rules cause the firewall to immediately act upon the request based on the configuration of the rule. A ‘deny’ rule will immediately respond to the request based on the configured rule action/mode (for example, ‘block’) and no other rules will be processed.
When triggered, traditional WAF rules cause the firewall to immediately act upon the request based on the configuration of the rule. A ‘deny’ rule will immediately respond to the request based on the configured rule action/mode (for example, ‘block’) and no other rules will be processed.
allowed_modes: array of "default" or "disable" or "simulate" or 2 moreDefines the list of possible actions of the WAF rule when it is triggered.
Defines the list of possible actions of the WAF rule when it is triggered.
default_mode: "disable" or "simulate" or "block" or "challenge"Defines the default action/mode of a rule.
Defines the default action/mode of a rule.
WAFManagedRulesTraditionalAllowRule { id, allowed_modes, description, 4 more } When triggered, traditional WAF rules cause the firewall to immediately act on the request based on the rule configuration. An ‘allow’ rule will immediately allow the request and no other rules will be processed.
When triggered, traditional WAF rules cause the firewall to immediately act on the request based on the rule configuration. An ‘allow’ rule will immediately allow the request and no other rules will be processed.
RuleEditResponse = { id, allowed_modes, description, 4 more } or { id, allowed_modes, default_mode, 5 more } or { id, allowed_modes, description, 4 more } When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
WAFManagedRulesAnomalyRule { id, allowed_modes, description, 4 more } When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
When triggered, anomaly detection WAF rules contribute to an overall threat score that will determine if a request is considered malicious. You can configure the total scoring threshold through the ‘sensitivity’ property of the WAF package.
WAFManagedRulesTraditionalDenyRule { id, allowed_modes, default_mode, 5 more } When triggered, traditional WAF rules cause the firewall to immediately act upon the request based on the configuration of the rule. A ‘deny’ rule will immediately respond to the request based on the configured rule action/mode (for example, ‘block’) and no other rules will be processed.
When triggered, traditional WAF rules cause the firewall to immediately act upon the request based on the configuration of the rule. A ‘deny’ rule will immediately respond to the request based on the configured rule action/mode (for example, ‘block’) and no other rules will be processed.
allowed_modes: array of "default" or "disable" or "simulate" or 2 moreDefines the list of possible actions of the WAF rule when it is triggered.
Defines the list of possible actions of the WAF rule when it is triggered.
default_mode: "disable" or "simulate" or "block" or "challenge"Defines the default action/mode of a rule.
Defines the default action/mode of a rule.
WAFManagedRulesTraditionalAllowRule { id, allowed_modes, description, 4 more } When triggered, traditional WAF rules cause the firewall to immediately act on the request based on the rule configuration. An ‘allow’ rule will immediately allow the request and no other rules will be processed.
When triggered, traditional WAF rules cause the firewall to immediately act on the request based on the rule configuration. An ‘allow’ rule will immediately allow the request and no other rules will be processed.