Dell EqualLogic PS6210XS EqualLogic Group Manager Administrator s Guide PS Ser - Page 74

IPsec Policies, Security Certificates, Certificates

Page 74 highlights

• Traffic is protected using certificates or pre-shared keys. NOTE: IPsec configurations cannot be modified. They must be removed and then recreated using the new configuration. Protect Communication Between Group Members To enable IPsec security for communication between group members, use the ipsec enable CLI command. After IPsec is enabled, all network traffic between group members is protected automatically. No further configuration is required. Any incoming or outgoing IP traffic that travels between hosts and the group can be protected with IPsec. This traffic includes, but is not necessarily limited to: • iSCSI traffic • Telnet and SSH connections to the Group Manager CLI • HTTP connections to the Group Manager GUI • SMTP email notifications • Syslog • NTP • RADIUS • SNMP NOTE: If IPsec is enabled but no security parameters or policies are in place, intragroup traffic is protected, and traffic to and from the group is allowed to pass without being protected or dropped. IPsec During Replication The PS Series firmware provides no mechanism for using IPsec to protect traffic between replication partners. It is technically possible to create IPsec polices on both the primary and secondary group in which each group treats the other as an iSCSI initiator and traffic is protected accordingly. However, this configuration is not supported, and Dell recommends against implementing it in a production environment. IPsec Policies Traffic that meets the conditions stipulated by the policy can either be passed, dropped, or protected using an IPsec security parameter associated with the policy. You can use IPsec policies to apply IPsec protection to traffic that meets one or more of the following criteria: • Data traveling to or from specific IP addresses, or a range of IP addresses defined by a specific subnet or netmask • IPv4 or IPv6 traffic • Specific network protocols: TCP, UDP or ICMP (either IPv4 or IPv6) Unless explicitly specified by the policy, traffic is allowed to pass. If you want to drop all traffic that is not explicitly protected or passed, you must create an IPsec policy that drops traffic by default. If multiple IPsec policies are in place, the system determines their priority by the order in which they were created. Policies created first take precedence over policies created later. You can also use IPsec policies to determine what traffic is being protected using IPsec, and what traffic is being passed or dropped without encryption. Security Certificates Security certificates are used in an IPsec configuration as one method of authenticating secured connections between iSCSI initiators and the group. Implementation of an IPsec-enabled SAN requires both a root-CA (Certificate Authority) certificate from the issuing authority and a local certificate to authenticate the group. 74 About Group-Level Security

  • 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
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355

Traffic
is protected using
certificates
or pre-shared keys.
NOTE: IPsec
configurations
cannot be
modified.
They must be removed and then recreated using the new
configuration.
Protect Communication Between Group Members
To enable IPsec security for communication between group members, use the
ipsec enable
CLI command.
After IPsec is enabled, all network
traffic
between group members is protected automatically. No further
configuration
is required.
Any incoming or outgoing IP
traffic
that travels between hosts and the group can be protected with IPsec. This
traffic
includes, but is
not necessarily limited to:
iSCSI
traffic
Telnet and SSH connections to the Group Manager CLI
HTTP connections to the Group Manager GUI
SMTP email
notifications
Syslog
NTP
RADIUS
SNMP
NOTE: If IPsec is enabled but no security parameters or policies are in place, intragroup
traffic
is protected, and
traffic
to
and from the group is allowed to pass without being protected or dropped.
IPsec During Replication
The PS Series
firmware
provides no mechanism for using IPsec to protect
traffic
between replication partners. It is technically
possible to create IPsec polices on both the primary and secondary group in which each group treats the other as an iSCSI initiator
and
traffic
is protected accordingly. However, this
configuration
is not supported, and Dell recommends against implementing it in a
production environment.
IPsec Policies
Traffic
that meets the conditions stipulated by the policy can either be passed, dropped, or protected using an IPsec security
parameter associated with the policy.
You can use IPsec policies to apply IPsec protection to
traffic
that meets one or more of the following criteria:
Data traveling to or from
specific
IP addresses, or a range of IP addresses
defined
by a
specific
subnet or netmask
IPv4 or IPv6
traffic
Specific
network protocols: TCP, UDP or ICMP (either IPv4 or IPv6)
Unless explicitly
specified
by the policy,
traffic
is allowed to pass. If you want to drop all
traffic
that is not explicitly protected or
passed, you must create an IPsec policy that drops
traffic
by default.
If multiple IPsec policies are in place, the system determines their priority by the order in which they were created. Policies created
first
take precedence over policies created later.
You can also use IPsec policies to determine what
traffic
is being protected using IPsec, and what
traffic
is being passed or dropped
without encryption.
Security
Certificates
Security
certificates
are used in an IPsec
configuration
as one method of authenticating secured connections between iSCSI
initiators and the group. Implementation of an IPsec-enabled SAN requires both a root-CA
(Certificate
Authority)
certificate
from the
issuing authority and a local
certificate
to authenticate the group.
74
About Group-Level Security