Constellation ES.1 SAS Product Manual, Rev. E
45
1. The download must be an SED file. A standard (base) drive (non-SED) file will be rejected.
2. The download file must be signed and authenticated.
3. As with a non-SED drive, the download file must pass the acceptance criteria for the drive. For example it
must be applicable to the correct drive model, and have compatible revision and customer status.
9.8
Power requirements
The standard drive models and the SED drive models have identical hardware, however the security and
encryption portion of the drive controller ASIC is enabled and functional in the SED models. This represents a
small additional drain on the 5V supply of about 30mA and a commensurate increase of about 150mW in
power consumption. There is no additional drain on the 12V supply. See the tables in Section 7.3 for power
requirements on the standard (non-SED) drive models.
9.9
Supported commands
The SED models support the following two commands in addition to the commands supported by the standard
(non-SED) models as listed in Table 8:
• Security Protocol Out (B5h)
• Security Protocol In (A2h)
9.10
Sanitize - CRYPTOGRAPHIC ERASE
This command cryptographically erases all user data on the drive by destroying the current data encryption key
and replacing it with a new data encryption key randomly generated by the drive. Sanitize CRYPTOGRAPHIC
ERASE is a SCSI CDB Op code 48h and selecting the service action code 3 (CRYPTOGRAPHIC ERASE)
9.11
RevertSP
The SED models will support RevertSP feature where it erases all data in all bands on the device and returns
the contents of all SPs (Security Providers) on the device to their original factory state. In order to execute the
RevertSP method the unique PSID (Physical Secure ID) printed on the drive label must be provided. PSID is
not electronically accessible and can only be manually read from the drive label or scanned in via the 2D bar-
code.
