HP 8/8 Fabric OS Encryption Administrator's Guide v6.4.0 (53-1001864-01, June - Page 163

First time encryption, Resource allocation, Configuring a LUN for first time encryption

Page 163 highlights

First time encryption 3 First time encryption First time encryption, also referred to as encryption of existing data, is similar to the re-keying process described in the previous section, except that there is no expired key and the data present in the LUN is cleartext to begin with. In a first time encryption operation, cleartext data is read from a LUN, encrypted with the current key and written back to the same LUN at the same logical block address (LBA) location. This process effectively encrypts the LUN and is referred to as "in-place encryption." Resource allocation System resources for first time encryption sessions are shared with re-key sessions. There is an upper limit of twelve sessions with two concurrent sessions per target. Refer to the re-key "Resource allocation" on page 145 section for details. First time encryption modes First-time encryption can be performed under the following conditions: • Offline encryption - The hosts accessing the LUN are offline or host I/O is halted while encryption is in process. • Online encryption - The hosts accessing the LUN are online and host I/O is active during the encryption operation. Configuring a LUN for first time encryption First time encryption options are configured at the LUN level either during LUN configuration with the cryptocfg --add -LUN command, or at a later time with the cryptocfg --modify -LUN command. 1. Set the LUN policy to encrypt to enable encryption on the LUN. All other options related to encryption are enabled. A DEK is generated and associated with the LUN. 2. Enable first time encryption by setting the -enable_encexistingdata parameter. The existing data on the disk is encrypted using the configured DEK. 3. Optionally set the auto re-keying feature with the cryptocfg --enable_rekey command and specify the interval at which the key expires and automatic re-keying should take place (time period in days) Enabling automatic re-keying is valid only if the LUN policy is set to encrypt and the encryption format is Brocade native. Refer to the section "Crypto LUN parameters and policies" on page 129 for more information. The following example configures a LUN for first time encryption with re-keying scheduled at a 6-month interval. You must commit the operation to take effect. FabricAdmin:switch>cryptocfg --add -LUN my_disk_tgt 0x0 \ 10:00:00:00:c9:2b:c9:3a 20:00:00:00:c9:2b:c9:3a -encrypt \ -enable_encexistingdata -enable_rekey 180 Operation Succeeded Fabric OS Encryption Administrator's Guide 145 53-1001864-01

  • 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

Fabric OS Encryption Administrator’s Guide
145
53-1001864-01
First time encryption
3
First time encryption
First time encryption, also referred to as encryption of existing data, is similar to the re-keying
process described in the previous section, except that there is no expired key and the data present
in the LUN is cleartext to begin with.
In a first time encryption operation, cleartext data is read from a LUN, encrypted with the current
key and written back to the same LUN at the same logical block address (LBA) location. This
process effectively encrypts the LUN and is referred to as “in-place encryption.”
Resource allocation
System resources for first time encryption sessions are shared with re-key sessions. There is an
upper limit of twelve sessions with two concurrent sessions per target. Refer to the re-key
“Resource allocation”
on page 145 section for details.
First time encryption modes
First-time encryption can be performed under the following conditions:
Offline encryption
- The hosts accessing the LUN are offline or host I/O is halted while
encryption is in process.
Online encryption
- The hosts accessing the LUN are online and host I/O is active during the
encryption operation.
Configuring a LUN for first time encryption
First time encryption options are configured at the LUN level either during LUN configuration with
the
cryptocfg
--
add -LUN
command, or at a later time with the
cryptocfg
--
modify -LUN
command.
1.
Set the LUN policy to
encrypt
to enable encryption on the LUN. All other options related to
encryption are enabled. A DEK is generated and associated with the LUN.
2.
Enable first time encryption by setting the
-enable_encexistingdata
parameter. The existing
data on the disk is encrypted using the configured DEK.
3.
Optionally set the auto re-keying feature with the
cryptocfg
--
enable_rekey
command and
specify the interval at which the key expires and automatic re-keying should take place (
time
period in days
) Enabling automatic re-keying is valid only if the LUN policy is set to
encrypt
and
the encryption format is Brocade
native.
Refer to the section
“Crypto LUN parameters and
policies”
on page 129 for more information.
The following example configures a LUN for first time encryption with re-keying scheduled at a
6-month interval. You must commit the operation to take effect.
FabricAdmin:switch>
cryptocfg --add -LUN my_disk_tgt 0x0 \
10:00:00:00:c9:2b:c9:3a 20:00:00:00:c9:2b:c9:3a -encrypt \
-enable_encexistingdata -enable_rekey 180
Operation Succeeded