When CE is the purge technique, the sanitization record is augmented with: the make, model, version or ISM type and the storage technology, noting that data may sit in several components such as cache and platters; whether a deterministic random bit generator (for example from SP 800-90A) was used for key generation and how it was validated; the media encryption algorithm, key strength, mode and validations; which key (data-encryption, key-wrapping or key-derivation) is sanitized and, where a key-encryption key is involved, the wrapping and derivation algorithms, strengths and modes; which ISM areas are encrypted and how any unencrypted areas are sanitized; the treatment of the keys under sanitization during any wrapping, unwrapping or rewrapping that is not part of the CE itself; the ISM-dependent key sanitization technique; support in the ISM for escrow or injection of keys at or beneath the CE level and whether the key was ever escrowed or injected; how the ISM handles error conditions that stop CE completing and whether it reports success or failure; and the host interface commands that provide the features, including whether all data-encryption keys are changed. Where target keys live in an external key management system, the record also shows how key sanitization in that system and any escrowed, backed-up or elsewhere-stored copies were addressed. CE works regardless of documentation, but organisational acceptance of CE depends on it.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.