Netgear STM300 STM 150-300-600 Reference Manual (PDF) - Page 119

HTTPS Scan Settings, client, scan the HTTPS traffic, and then rebuild the SSL connection.

Page 119 highlights

ProSecure Web/Email Security Threat Management (STM) Appliance Table 35. URL Filtering Settings (Continued) Setting Description Add URL Import from File Type or copy a URL in the Add URL field. Then click the Add table button to add the URL to the URL field. To import a list with URLs into the URL field, click the Browse button and navigate to a file in .txt format that contains line-delimited URLs (that is, one URL per line). Then click the Upload table button to add the URLs to the URL field. Note: Any existing URLs in the URL field are overwritten when you import a list of URLs from a file. Replace the When a user attempts to access a blocked URL, the STM replaces the content of the Content of a blocked URL with the following text, which you can customize: Blocked Page with the Following Text Internet Policy has restricted access to this location: %URL% Note: Make sure that you keep the %URL% metaword in the text to enable the STM to insert the category that the blocked Web page falls under. As an option, you can select the Insert Link to User Login Portal Page check box to include a hyperlink on screen that allows the user to log in as another user: You are logged in as %USER% (Click here to login as another user) Note: Make sure that you keep the %LOGIN-LINK% metaword in the text to enable the STM to insert the actual hyperlink. The text is displayed on the URL Filtering screen with HTML tags. Click Preview to open a screen that displays the notification text in HTML format. 4. Click Apply to save your settings. HTTPS Scan Settings HTTPS traffic is encrypted traffic that cannot be scanned or the data stream would not be secure. However, the STM can scan HTTPS traffic that is transmitted through an HTTP proxy. The STM can break up the SSL connection between the HTTPS server and the HTTP client, scan the HTTPS traffic, and then rebuild the SSL connection. Chapter 4. Content Filtering and Optimizing Scans | 119

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261

Chapter 4.
Content Filtering and Optimizing Scans
|
119
ProSecure Web/Email Security Threat Management (STM) Appliance
4.
Click
Apply
to save your settings.
HTTPS Scan Settings
HTTPS traffic is encrypted traffic that cannot be scanned or the data stream would not be
secure. However, the STM can scan HTTPS traffic that is transmitted through an HTTP
proxy. The STM can break up the SSL connection between the HTTPS server and the HTTP
client, scan the HTTPS traffic, and then rebuild the SSL connection.
Add URL
Type or copy a URL in the Add URL field. Then click the
Add
table button to add the
URL to the URL field.
Import from File
To import a list with URLs into the URL field, click the
Browse
button and navigate to a
file in .txt format that contains line-delimited URLs (that is, one URL per line). Then click
the
Upload
table button to add the URLs to the URL field.
Note:
Any existing URLs in the URL field are overwritten when you import a list of
URLs from a file.
Replace the
Content of a
Blocked Page with
the Following Text
When a user attempts to access a blocked URL, the STM replaces the content of the
blocked URL with the following text, which you can customize:
Internet Policy has restricted access to this location:
%URL%
Note:
Make sure that you keep the %URL% metaword in the text to enable the STM
to insert the category that the blocked Web page falls under.
As an option, you can select the
Insert Link to User Login Portal Page
check box to
include a hyperlink on screen that allows the user to log in as another user:
You are logged in as %USER%
(Click here to login as another user)
Note:
Make sure that you keep the %LOGIN-LINK% metaword in the text to enable the
STM to insert the actual hyperlink.
The text is displayed on the URL Filtering screen with HTML tags. Click
Preview
to
open a screen that displays the notification text in HTML format.
Table 35.
URL Filtering Settings (Continued)
Setting
Description