Technical information

HGST Ultrastar C15K600 Hard Disk Drive Specification
333
21.1.4
Department of Defense
DoD 5220.22-M, "National Industrial Security Program Operating Manual", 2/28/2006
http://www.dtic.mil/whs/directives/corres/pdf/522022m.pdf
DoD 5220.22-M Supplement 1, “National Industrial Security Program Operating Manual Supplement”, 02/1995 -
http://www.dtic.mil/whs/directives/corres/pdf/522022MSup1.pdf
21.1.5
RSA Laboratories Standards
1. RSA-PSS - http://www.rsa.com/rsalabs/node.asp?id=2146
2. RSA PKCS #5 v2.0 Password-Based Cryptography Standard -
ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-5v2/
pkcs5v2-0.doc
21.1.6
Other Standards
1. T10 SCSI Standard.(T10 homepage - http://www.t10.org/index.html)
21.2
Implementation Exceptions
The following is a list that describes non-compliance with the TCG Enterprise SSC specification:
• The SSC specification requires support for 1024 bands, but the implementation supports up to 6 bands.
• The K_AES_256 table was implemented with only the UID and MODE columns.
• Only one active session is permitted at a time. If a new session is requested when a session is already active,
the drive answers the host with SP_BUSY, instead of NO_SESSIONS_AVAILABLE
21.3
Implementation Features and Details Outside of TCG
Specifications
The following features are outside of the TCG specifications.
1. Ports
2. Firmware signing
The following implementation details are outside of the TCG SSC specification.
a. The SSC Specification states “The TPer SHALL implement the ParamCheck Longitudinal Redundancy
Check (LRC) for Get and Set method calls on a PIN value". If the LRC check is erroneously applied to a
value other than a PIN we ignore it, therefore no error is generated.
b. When handling a "TCG cmd followed by a R/W cmd", all reads and writes that follow a TCG command will
be processed in the normal way. No special handling or error messages will be sent to the host. It is up to
the host to understand the possible outcomes of TCG commands and r/w command ordering and plan
accordingly.
c. CRC checking is disabled in all cases, so the drive will return data to the host. If the user successfully
authenticates, then unencrypted data is returned to the host. If the user is unable to authenticate,
encrypted data is returned to the host.
d. The TPer replies with SP_BUSY for requests beyond 1 session.