Firewall Rule

Overview

A Firewall Rule is used to set up regulations on a particular domain. When a request is made to that domain, the WAF checks for the violation of a rule and carries out the appropriate action that is configured by the User.

The following actions are available to the User :

1. DROP & RECORD REQUEST - If the Request to the subscribed domain matches the Firewall Rule, an event is generated but the request will not be allowed through the WAF.
2. RECORD REQUEST - An event is generated whenever the Request satisfies the Rule, but whenever the request passes through other rules its events are logged by Haltdos.
3. BYPASS REQUEST - If the Request tests positive for the rule, no other rule is tested and the Request will be allowed through the WAF.
4. TEMPORARY BLACKLIST SOURCE IP - If the request satisfies the rule, then the user is temporarily blacklisted.
5. REDIRECT - If the request satisfies the rule, then the user is redirected to another page.
6. SEND CAPTCHA CHALLENGE - If the request satisfies the rule, then the user receives a challenge like a captcha.
7. SEND RESPONSE WITH STATUS CODE - If the request satisfies the rule, a custom HTML response will be returned with a status code.
8. SEND CUSTOM RESPONSE - If the request satisfies the rule, a custom HTML response will be returned.
9. CHANGE RESPONSE CODE - If the request satisfies the rule, the user can change the response code, and the changed response code will be sent back.
10. TARPIT SRC. IP - If the request satisfies the rule, the end-user IP will be tarpit.
11. NO ACTION - If the request satisfies the rule, then no action will be performed on the current request.
12. SKIP LEARNING - If the request satisfies the rule, then no learning will be performed on the current request.
13. SEND EMPTY RESPONSE - If the request satisfies the rule, the end-user will get empty response / blank page in return.

How to Use:

1. Go to WAF > Listener > Profiles > Rules > Firewall Rules
2. Click on the Add Rule Button and a pop-up box will open.
3. Configure the fields that are present.
4. Click on Save Changes and the rule will be reflected.

Parameters	Accepted value	Default
Rule Name	String	Blank
Rule Message	String	Blank
Rule Priority	Integer	0
URI	Strng	1000
Method	Drop-down	All
Rule Action	Drop-down	Record Request
Find Location	Drop-Down	Variable
Find Parameter	String	Blank
Match Condition	Drop-Down	Pattern Exists
Match Value	String	Blank

Description

Rule Name

Users are allowed to specify a rule name to identify the rule which is to be created. The rule name takes alpha-numeric input.

Rule Message

Users are allowed to specify a rule message to understand the purpose of the rule. It can contain a detailed description to identify the rule.

Rule Priority

It is a numeric field that specifies the priority of the rule in which the rule will be executed while evaluating the request. The lower value of priority means it will be executed first while executing the type of rule. The default value Is 0.

URI

Users are allowed to specify the URI. Specify the URI on which the firewall rule will be applied.

Method

Users are allowed to specify the HTTP method on which the rule will be applied i.e. All, GET, POST, PUT, DELETE, HEAD, OPTIONS.

Rule Action

Users are allowed to specify the action to be taken for the request matched i.e. No Action, Drop, Record, Bypass, Redirect, Temporary Blacklist, Send Challenge, Skip Learning.

Match Condition

This drop-down allows to set the match condition i.e. Pattern Match or Pattern Not Match for the request.

Match Pattern

Users are allowed to specify the keyword to match when the rule is invoked. The entered value can be a regex pattern.

Find Location

Users can define the source location where this condition needs to be applied.

Variable

Users can select the variable.

Match Condition

The user can define the match condition for the parameter and match value.

Match Value

The user can define what value needs to be matched with the match condition.