301
Controlling traffic at the security gateway
Blocking inappropriate content with content filtering
Filter on URL pattern matches
To filter traffic based on URL pattern matches, you must do the following:
■
Specify the URL patterns.
■
Create a rule and apply the URL pattern match restriction.
To filter by URL pattern matching
1
In the SGMI, in the left pane, under Policy, click
Content Filtering
.
2
In the right pane, on the Advanced Restrictions tab, to the right of the Deny URLs that contain the
following patterns, click
Add.
3
In the URL Pattern dialog box, in the URL pattern text box, type the URL pattern that you want to
add to the list.
For example, the following regular expression:
3[1248]?(K|M)\\.bin
denies access to the files 31K.bin, 32K.bin, 34K.bin, 36K.bin, 38K.bin, 31M.bin, 32M.bin, 34M.bin,
and 38M.bin.
4
Click
OK
.
5
Optionally, do one of the following:
■
To save your configuration now and activate later, on the toolbar, click
Save
.
■
To activate your configuration now, on the toolbar, click
Activate
.
When prompted to save your changes, click
Yes
.
To add filtering on URL pattern matches to a rule
1
In the SGMI, in the left pane, under Policy, click
Firewall
.
2
In the right pane, on the Rules tab, do one of the following:
■
To add URL pattern filtering to an existing rule, highlight the rule, and then double-click to
display its properties.
■
To create a new rule, click
New
.
3
If you create a new rule, in the Rule Properties dialog box, on the General tab, do the following:
4
Next to the Service group field, do one of the following:
■
Select a service group that contains the HTTP protocol, such as the Web service group.
■
Select a service group and add the HTTP protocol to it.
■
Create a service group with the HTTP protocol.
Rule name
Type a name for this rule.
Caption
Type a brief description of the rule.
Action
Click
allow
.
Arriving through
Select the connection point through which traffic enters the security gateway.
Source
Select the defined network entity from which HTTP traffic originates. This can be a host
network entity representing a specific machine from which the packets originate, or
subnet network entity representing your internal network.
Destination
Select the defined network entity to which HTTP traffic is destined. This can be a host
network entity representing a specific machine or a subnet network entity representing
your internal network.
Leaving through
Select the connection point through which traffic leaves the security gateway.
Summary of Contents for Security 5600 Series, Security 5400 Series,Clientless VPN 4400 Series
Page 76: ...76 Managing administrative access Enabling SSH for command line access to the appliance...
Page 242: ...242 Defining your security environment Controlling full application inspection of traffic...
Page 243: ...243 Defining your security environment Controlling full application inspection of traffic...
Page 269: ...268 Limiting user access Authenticating using Out Of Band Authentication OOBA...
Page 373: ...372 Preventing attacks Enabling protection for logical network interfaces...
Page 509: ...508 Generating reports Upgrade reports...
Page 553: ...552 Advanced system settings Configuring advanced options...
Page 557: ...556 SSL server certificate management Installing a signed certificate...
Page 861: ...860 Index...