D-Link DFL-200 Product Manual - Page 122

Appendix D: HTTP Content Filtering, outbound policy utilizing the HTTP ALG.

Get D-Link DFL-200 - Security Appliance PDF manuals and user guides
UPC - 790069268823
View all D-Link DFL-200 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 122 highlights

Appendix D: HTTP Content Filtering HTTP Content Filtering Global Policy Protection from malicious or improper web content is a must for Business owners and concerned parents alike. There are numerous vehicles for hackers to damage or take control of one's PC or even Network. Malicious code may be delivered in deviously crafted ActiveX controls, Java Scripts, cookies, or tainted file downloads. Many times executable (*.exe) files are laced with spy-ware or viral programs that become active and take over after the program is run for the first time. To help reduce the likelihood of malicious software reaching the PCs on the LAN or DMZ of the NetDefend Firewall, filtering of HTTP traffic can be customized and enabled. This filter can be configured to strip ActiveX objects (including flash), Java Applets, Visual Basic/Java Scripts, and or block cookies. In addition, a Whitelist is configurable to define URLs that will always be allowed. Conversely a Blacklist is provided to allow customizable filtering of websites, domains, and even file types based on file extension. All of the aforementioned filters function simultaneously (if enabled/configured) when HTTP content filtering is enabled. In order for HTTP content filtering to be performed, all HTTP traffic must pass-through an outbound policy utilizing the HTTP ALG. Due to this behavior content filtering can be applied to either LAN or DMZ interface simultaneously or independent of one another. Keep in mind that the content filtering specifications are global and will apply to every instance of a rule using the HTTP ALG. Two configurations need to be made in order to use HTTP Content Filtering: - The Whitelist and Blacklist must be customized to suit the desired filtering requirements. - HTTP traffic on an interface (LAN or DMZ) must be bound to a rule using the HTTP ALG. 122

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
122
Appendix D: HTTP Content Filtering
HTTP Content Filtering Global Policy
Protection from malicious or improper web content is a must for Business owners and
concerned parents alike.
There are numerous vehicles for hackers to damage or take control
of one’s PC or even Network.
Malicious code may be delivered in deviously crafted ActiveX
controls, Java Scripts, cookies, or tainted file downloads.
Many times executable (*.exe) files
are laced with spy-ware or viral programs that become active and take over after the program
is run for the first time.
To help reduce the likelihood of malicious software reaching the PCs on the LAN or DMZ
of the NetDefend Firewall, filtering of HTTP traffic can be customized and enabled.
This filter
can be configured to strip ActiveX objects (including flash), Java Applets, Visual Basic/Java
Scripts, and or block cookies.
In addition, a Whitelist is configurable to define URLs that will
always be allowed.
Conversely a Blacklist is provided to allow customizable filtering of
websites, domains, and even file types based on file extension.
All of the aforementioned
filters function simultaneously (if enabled/configured) when HTTP content filtering is enabled.
In order for HTTP content filtering to be performed, all HTTP traffic must pass-through an
outbound policy utilizing the HTTP ALG.
Due to this behavior content filtering can be applied
to either LAN or DMZ interface simultaneously or independent of one another.
Keep in mind
that the content filtering specifications are global and will apply to every instance of a rule
using the HTTP ALG.
Two configurations need to be made in order to use HTTP Content Filtering:
- The Whitelist and Blacklist must be customized to suit the desired filtering requirements.
- HTTP traffic on an interface (LAN or DMZ) must be bound to a rule using the HTTP ALG.