SED and TCG Opal Hardware Encrypted SSD Recovery: Keys, PSID and Limits
How a self encrypting SSD (SED), TCG Opal locking ranges, PBA and the shadow MBR work. Recovery when the credential is known, why chip off does not help on a controller fault, and why a PSID revert is not recovery but permanent erasure. The honest limits.
Quick answer: In recovering a self encrypting SSD (SED, TCG Opal) the decisive question is this: do you have a valid credential (password, PIN or recovery key)? If yes, the disk is unlocked normally, a read only image is taken, and recovery continues with classic methods. If no, the situation is different: on a SED all data is permanently encrypted with a media encryption key (MEK) inside the controller, and that key cannot be unwrapped without the credential. So if there is no credential, even removing the NAND chips (chip off) does not help, because the bits read are encrypted. A PSID revert is not a recovery path: while returning the disk to factory state it generates a new key and discards the old one, that is, it permanently destroys the data. Modern SED technology is designed to make data inaccessible without the credential, and this limit is real.
Hardware encrypted SSDs have become standard in enterprise and personal devices. Most NVMe and SATA SSDs run as self encrypting drives even if the user is unaware. This is excellent for data security, but it makes recovery entirely different from classic disks in the event of a fault or a forgotten password. This guide explains, honestly, the SED and TCG Opal architecture, in which scenario recovery is possible, and which limits are mathematically insurmountable.
How a SED works: always encrypted
On a self encrypting drive, data is encrypted by hardware from the moment it is written to disk. There are two key layers.
Media encryption key (MEK or DEK). The actual key that encrypts all data on the disk. It is generated inside the controller, never leaves in clear text, and the user never sees it directly. Data is always written to disk encrypted with this key; encryption cannot be turned off, only the unlock mechanism changes.
Authentication key (AK or KEK). Derived from the user's password, PIN or recovery key, this is the key that wraps the MEK. When the correct credential is given, the controller unwraps the MEK and the data becomes readable. If the credential is wrong, the MEK is not unwrapped and everything read from the disk is meaningless encrypted blocks.
The consequence of this architecture is critical: what makes the disk secure is not erasing the data but keeping the MEK inaccessible. Without the key, the encrypted blocks are practically unsolvable with today's encryption standards.
TCG Opal: locking ranges, PBA and the shadow MBR
TCG Opal is the industry standard that manages this encryption. A few concepts are needed for recovery decisions.
Locking ranges. Opal can divide the disk into ranges that lock separately. Each range has its own lock state.
Security providers (SP). The Admin SP manages the disk, the Locking SP manages the locking ranges and credentials.
Pre boot authentication (PBA) and the shadow MBR. Opal disks can present a small authentication environment (the shadow MBR) before the operating system boots. The user enters the credential there, the disk unlocks, and then the real operating system loads.
SID and PSID. The SID is the disk's administrator credential. The PSID (Physical Security ID) is a code printed on the disk's label, readable only with physical access. The PSID's only function is revert, that is, returning the disk to factory state, and this operation destroys the data.
The recovery path by symptom
| Situation | Credential | Recovery path |
|---|---|---|
| Password known, disk healthy | yes | normal unlock, read only image, classic recovery |
| Password forgotten, disk healthy | no | mathematically unrecoverable, only search for the credential |
| Controller fault, password known | yes | unlock after controller repair; hard but may be possible |
| Controller fault, no password | no | even chip off yields encrypted data, unrecoverable |
| PSID revert performed | either | data permanently gone, unrecoverable |
| Firmware update broke it | yes | controller firmware recovery, expert lab |
With a credential: standard recovery
The best scenario is that the user knows the password, PIN or recovery key. In that case the disk is unlocked through the Opal mechanism, the data becomes clear, and from there it is classic SSD recovery. If the disk also carries physical or logical damage, a read only image is taken first and work is done on the image.
Because BitLocker with Microsoft eDrive (IEEE 1667) can use hardware encryption, on an eDrive device the BitLocker recovery key also unlocks the disk. We covered software side BitLocker and LUKS recovery in our BitLocker encrypted disk recovery article and our FileVault and LUKS recovery article; the difference with hardware encryption is that the key is inside the controller and the data is never written in clear.
Controller fault: why chip off is not a solution
When a classic SSD controller fails, in some cases the NAND chips can be removed (chip off) and the raw data read. On an unencrypted disk this can bring back pieces of data; we described the method in our chip off NAND extraction article. But on a SED disk the situation is different. Every block on the NAND is encrypted with the MEK inside the controller. Even if you remove and read the chips, you hold encrypted bits; the key is in the controller's secure store and cannot be unwrapped without the credential.
So a controller fault on a SED disk becomes two separate problems: first bringing the controller back to working order (firmware or electronics repair), then unwrapping the MEK with a valid credential. If the credential exists and the controller can be repaired, recovery is possible but requires expertise. If there is no credential, you cannot reach the data even if you repair the controller. This is the most important difference between SED and unencrypted SSD recovery. We also examined NVMe side controller and NAND recovery in our NVMe M.2 SSD recovery article.
PSID revert: not recovery, but permanent erasure
The most common and most expensive mistake is to do a PSID revert as a solution to a forgotten password. Online this may be described as a way to unlock, but the truth is the opposite. A PSID revert, while returning the disk to factory state, generates a new media encryption key and permanently discards the old one. Because the old key is gone, all encrypted data on the disk instantly becomes mathematically inaccessible. So a PSID revert is a crypto erase; it does not recover data, it destroys it for certain.
PSID is used only when you want to safely reuse or dispose of the disk. On a disk that holds data you want to recover, a PSID revert must never be done.
The honest limit: inaccessible by design
It is essential to be honest here. Modern SED and TCG Opal are designed to make data inaccessible without the credential; this is not a flaw, it is the purpose of the technology. Without a valid password, PIN or recovery key, decrypting the encrypted data with today's encryption standards is practically impossible. Do not trust any method that promises decryption without the key or guaranteed unlocking; these are either fraud or apply only to old, weak or badly implemented encryption. The right approach is to focus on finding the credential (password manager, enterprise key store, BitLocker recovery key backup) and, where possible, always keep a valid backup. A similar limit applies to locked and encrypted mobile devices; we covered it in our recovering data from a locked encrypted phone article.
The DSET approach
At DSET we start hardware encrypted SSD recoveries in our lab at Ankara Hacettepe Teknokent with an honest initial assessment. We first determine whether the disk is a SED, its Opal lock state, and whether a valid credential exists. If there is a credential, we image the disk read only and run recovery on the image; if there is a controller fault, we attempt firmware and electronics repair. If there is no credential, we say up front and clearly that decryption without the key is not possible, and we do not sell false hope. We avoid data destroying operations such as a PSID revert. If your SSD is locked or its controller has failed, contact DSET without doing any revert or reset. For physical recovery of the disk our PC-3000 lab hardware article and, for the legal dimension of an incident, our digital forensics process article provide guidance.
Frequently asked questions
I forgot my password, can you recover the data on my SED disk? No, without a valid credential (password, PIN or recovery key) the data on a hardware encrypted disk cannot be recovered mathematically. This is not a shortcoming, it is exactly the purpose of the technology. The only thing that can be done is to find the credential: password manager records, an enterprise key management system, or a BitLocker recovery key backup. Without these, the data stays inaccessible.
Can you unlock it with the PSID? No, this is a very common misunderstanding. A PSID revert does not unlock; while returning the disk to factory state it changes the encryption key and permanently destroys the old data. The PSID exists only to safely erase and reuse the disk. Never do a PSID revert on a disk that holds valuable data.
How do I tell whether a disk is a SED? Most modern NVMe and SATA SSDs support TCG Opal or the ATA security feature, and many run encryption on by default. Definitive information comes from the disk's properties and a controller query; expert tools can read Opal support, locking ranges and the lock state. If BitLocker on a device uses the disk's eDrive feature, hardware encryption is already active.
Sources
- TCG Opal SSC and Enterprise SSC specifications, locking ranges and SP structure.
- NIST SP 800-88, media sanitization and crypto erase principles.
- Microsoft eDrive and IEEE 1667 documentation, BitLocker hardware encryption interaction.
- DSET blog: NVMe M.2 SSD recovery and BitLocker encrypted disk recovery.
Kimliğinizi doğrulayın
Yetkilendirilmiş erişim alanı. Tüm giriş denemeleri kayıt altına alınır.