Trusted Computing Group Storage Work Group
Opal Security Subsystem Class (SSC) v2.00 Specification FAQ
February 28, 2013
Q. Is the Opal SSC v2.00 a superset of the Opal SSC v1.00?
A. Yes. The Opal SSC v2.00 specification extends the existing features of Opal SSC v1.00 and adds additional features.
Q. Is the Opal SSC v2.00 specification backwards compatible with the previous Opal SSC v1.00 specification?
A. No. The Opal SSC v2.00 specification itself is not backwards compatible. However, Opal SSC v2.00 allows a storage device vendor to implement a device based on Opal SSC v2.00 in a way that is backwards compatible with Opal SSC v1.00.
Q. Why was the backwards incompatibility introduced in Opal SSC v2.00?
A. The Opal SSC v2.00 specification was extended to allow storage devices with physical block size restrictions to be supported.
Q. How can I tell if a storage device supports both versions of the Opal specifications?
A. The storage device will report the Opal SSC Feature Descriptors for both specifications.
Q. What’s new in Opal SSC v2.00?
A. Opal v2.00 includes the following new and enhanced capabilities:
Q. What are the benefits of the Opal SSC v2.00 specification?
A. Opal SSC v2.00 will accommodate a wider range of storage devices. The addition of new features allows delivery of a richer set of solutions around self-encrypting drives.
Q. What is a Feature Set?
A. A Feature Set defines additional functionality that extends an SSC.
Q. Are there any Mandatory Feature Sets for Opal SSC v2.00?
A. Yes. The Additional DataStore Tables Feature Set is Mandatory for Opal SSC v2.00.
Q. Can Opal SSC v2.00 storage devices work with host software designed for Opal SSC v1.00?
A. Yes, if the storage device was implemented to support both the Opal SSC v1.00 and Opal SSC v2.00 specifications.
Q. How does a storage device vendor implement a device based on Opal SSC v2.00 so that it is compatible with Opal SSC v1.00?
A. An Opal SSC v2.00 implementation is compatible with Opal SSC v1.00 only if the geometry reported by the Geometry Reporting Feature does not specify any alignment restrictions; the TPer does not specify any granularity restrictions for byte tables; and the “Initial C_PIN_SID PIN Indicator” and “Behavior of C_PIN_SID PIN upon TPer Revert” fields are both 0x00 in the Opal SSC V2.00 Level 0 Feature Descriptor. The storage device will report the Opal SSC Feature Descriptors for both specifications.
Q. Will TCG have a certification program to test for Opal SSC v2.00 compliance?
A. Yes, a compliance testing program is currently being developed in the Storage Work Group.
Q. Where are the new TCG Storage specifications available?
A. The Opal v2.00 SSC is available now at:
Contact: Anne Price
Membership in the Trusted Computing Group is your key to participating with fellow industry stakeholders in the quest to develop and promote trusted computing technologies.
Standards-based Trusted Computing technologies developed by TCG members now are deployed in enterprise systems, storage systems, networks, embedded systems, and mobile devices and can help secure cloud computing and virtualized systems.
Trusted Computing Group announced that its TPM 2.0 (Trusted Platform Module) Library Specification was approved as a formal international standard under ISO/IEC (the International Organization for Standardization and the International Electrotechnical Commission). TCG has 90+ specifications and guidance documents to help build a trusted computing environment.