Dell DL4300 Appliance Users Guide - Page 38

Managing security, Adding an encryption key

Page 38 highlights

md "" NOTE: Ensure that you remove the \File_x portion of the metadata path, and enclose the metadata path in quotes. 9. From Computer Management → Storage Management → Disk Management, add the mount path to the volume. NOTE: Ensure that you remove the \File_x portion of the metadata path. 10. Remove the drive letter. 11. Add drive letters to all DL_VMRSRV_x volumes. 12. From the AppAssure Core Console → Configuration → Restore screen, click fix path, and then click Save. The repository is back online and display a green status. NOTE: You must repeat Step 9 through Step 12 for each DL_REPO_xxxx volume. Managing security The Core can encrypt protected machine snapshot data within the repository. Instead of encrypting the entire repository, you can specify an encryption key during the protection of a machine in a repository which lets the keys be reused for different protected machines. Encryption does not affect performance, as each active encryption key creates an encryption domain, thus letting a single core support multitenancy by hosting multiple encryption domains. In a multi-tenant environment, data is partitioned and deduplicated within the encryption domains. Because you manage the encryption keys, loss of the volume cannot leak the keys. Key security concepts and considerations include: • Encryption is performed using 256 bit AES in Cipher Block Chaining (CBC) mode that is compliant with SHA-3. • Deduplication operates within an encryption domain to ensure privacy. • Encryption is performed without impact on performance. • You can add, remove, import, export, modify, and delete encryption keys that are configured on the Core. • There is no limit to the number of encryption keys you can create on the Core. Adding an encryption key To add an encryption key: 1. Navigate to the Core Console. 2. Click Configuration → Security. The Encryption Keys page appears. 3. Click Actions, and then click Add Encryption Key. The Create Encryption Key dialog box displays. 4. In the Create Encryption Key dialog box, enter the details for the key described as follows. Text Box Description Name Enter a name for the encryption key. 38

  • 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

md "<metadata path>"
NOTE:
Ensure that you remove the
\File_x
portion of the metadata path, and enclose the
metadata path in quotes.
9.
From
Computer Management
Storage Management
Disk Management
, add the mount path
to the volume.
NOTE:
Ensure that you remove the
\File_x
portion of the metadata path.
10.
Remove the drive letter.
11.
Add drive letters to all
DL_VMRSRV_x
volumes.
12.
From the AppAssure Core Console
Configuration
Restore
screen, click
fix path
, and then click
Save
.
The repository is back online and display a green status.
NOTE:
You must repeat Step 9 through Step 12 for each
DL_REPO_xxxx
volume.
Managing security
The Core can encrypt protected machine snapshot data within the repository. Instead of encrypting the
entire repository, you can specify an encryption key during the protection of a machine in a repository
which lets the keys be reused for different protected machines. Encryption does not affect performance,
as each active encryption key creates an encryption domain, thus letting a single core support
multitenancy by hosting multiple encryption domains. In a multi-tenant environment, data is partitioned
and deduplicated within the encryption domains. Because you manage the encryption keys, loss of the
volume cannot leak the keys. Key security concepts and considerations include:
Encryption is performed using 256 bit AES in Cipher Block Chaining (CBC) mode that is compliant
with SHA-3.
Deduplication operates within an encryption domain to ensure privacy.
Encryption is performed without impact on performance.
You can add, remove, import, export, modify, and delete encryption keys that are configured on the
Core.
There is no limit to the number of encryption keys you can create on the Core.
Adding an encryption key
To add an encryption key:
1.
Navigate to the Core Console.
2.
Click
Configuration
Security
.
The
Encryption Keys
page appears.
3.
Click
Actions
, and then click
Add Encryption Key
.
The
Create Encryption Key
dialog box displays.
4.
In the
Create Encryption Key
dialog box, enter the details for the key described as follows.
Text Box
Description
Name
Enter a name for the encryption key.
38