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

Managing Digital, Certificates, Specifying Trusted Hosts, However

Page 121 highlights

ProSecure Web/Email Security Threat Management (STM) Appliance If one of these is not satisfied, a security alert message displays in the browser window: Figure 66. However, even when a certificate is trusted or still valid, or when the name of a certificate does match the name of the website, a security alert message still displays when a user who is connected to the STM visits an HTTPS site. The appearance of this security alert message is expected behavior because the HTTPS client receives a certificate from the STM instead of directly from the HTTPS server. If you want to prevent this security alert message from displaying, install a root certificate on the client PC. The root certificate can be downloaded from the STM's User Portal Login screen (see Figure 88 on page 156). If client authentication is required, the STM might not be able to scan the HTTPS traffic because of the nature of SSL. SSL has two parts-client and server authentication. HTTPS server authentication occurs with every HTTPS request, but HTTPS client authentication is not mandatory, and rarely occurs. Therefore it is of less importance whether the HTTPS request comes from the STM or from the real HTTPS client. However, certain HTTPS servers do require HTTPS client certificate authentication for every HTTPS request. Because of the design of SSL, the HTTPS client needs to present its own certificate in this situation rather than using the one from the STM, preventing the STM from scanning the HTTPS traffic. For information about certificates, see Managing Digital Certificates on page 76. You can specify trusted hosts for which the STM bypasses HTTPS traffic scanning. For more information, see Specifying Trusted Hosts on page 124. Chapter 4. Content Filtering and Optimizing Scans | 121

  • 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
|
121
ProSecure Web/Email Security Threat Management (STM) Appliance
If one of these is not satisfied, a security alert message displays in the browser window:
Figure 66.
However, even when a certificate is trusted or still valid, or when the name of a certificate
does match the name of the website, a security alert message still displays when a user who
is connected to the STM visits an HTTPS site. The appearance of this security alert message
is expected behavior because the HTTPS client receives a certificate from the STM instead
of directly from the HTTPS server. If you want to prevent this security alert message from
displaying, install a root certificate on the client PC. The root certificate can be downloaded
from the STM’s User Portal Login screen (see
Figure 88
on page 156).
If client authentication is required, the STM might not be able to scan the HTTPS traffic
because of the nature of SSL. SSL has two parts—client and server authentication. HTTPS
server authentication occurs with every HTTPS request, but HTTPS client authentication is
not mandatory, and rarely occurs. Therefore it is of less importance whether the HTTPS
request comes from the STM or from the real HTTPS client.
However, certain HTTPS servers do require HTTPS client certificate authentication for every
HTTPS request. Because of the design of SSL, the HTTPS client needs to present its own
certificate in this situation rather than using the one from the STM, preventing the STM from
scanning the HTTPS traffic. For information about certificates, see
Managing Digital
Certificates
on page 76.
You can specify trusted hosts for which the STM bypasses HTTPS traffic scanning. For more
information, see
Specifying Trusted Hosts
on page 124.