Self-Encrypting GPU Storage Is Not Evidence of Sanitization

Identify whether the statement describes a feature or a result

A GPU-server offer might describe encrypted storage while a refresh request asks for media suitable for reassignment. The offer and the request need an evidence connection. A component specification can help identify what was supplied; it does not describe a later event involving a particular drive.

NVIDIA's DGX B200 component table, on the page updated October 17, 2026, labels its data-cache drives SEDs. That is a concrete hardware example. The linked B200 storage guide addresses the distinction between boot drives, local cache and external storage. Here, the question is what supports a sanitization claim for the actual media.

Read the subject and tense of the statement closely. “Includes self-encrypting drives” describes equipment. “CE is proposed for these drives” describes intended work. “These drives have a suitable, accepted sanitization outcome” requires evidence of that outcome. Progress from one statement to the next needs more than the same product name.

References: [N1]

Understand what cryptographic erase depends on

NIST SP 800-88 Revision 2, published September 2025, explains CE through sanitization of keys protecting encrypted data. Ciphertext can remain on the media. The intended result depends on preventing recovery of the relevant keys, including applicable copies and paths through a key hierarchy.

Its applicability discussion excludes prior sensitive plaintext since the last appropriate sanitization. It also addresses external key recovery and confidentiality needs extending into a future where cryptographic weaknesses or greater computing capability could matter. Its implementation-assurance discussion covers key generation, encryption, key sanitization and wrapping.

Those dependencies explain why an encrypted-storage claim cannot settle the release question. Ask the appointed security specialist to connect the actual media's history and implementation to the proposed result. This is an educational comparison; the authorized data/security owner selects the policy, applicable method and acceptance requirements.

References: [D1]

Give the proposed result a precise scope

Begin with the media and target data the claim covers. “The GPU server is sanitized” is broader than a statement about identified local cache drives. Ask whether the proposed result covers the intended media set, and who resolves any difference between the two descriptions. Use the existing decommissioning guide for destination, release and custody planning.

Keep two recovery questions distinct. An external key that can recover the scoped drive's data bears directly on the CE claim for that drive. A separate copy of the data on other storage has its own disposition. Evidence about one drive cannot establish what happened to that separate copy.

For example, a claim limited to server-local cache should retain that limit when the project summary also mentions a shared dataset service. The wider dataset's disposition needs its own answer. Expanding the summary to “all project data erased” would create a claim that the narrower result never addressed.

References: [D1]

EX-CE-21: compare two fictional offers

Suppose a GPU refresh owner asks for evidence that identified storage media can meet the organization's sanitization requirement before reassignment. Offers A and B below are invented. Neither represents completed work or an actual supplier assessment.

Offer A identifies self-encrypting drives in the equipment list and attaches a product specification. It supplies no sanitization proposal or outcome evidence. A helps identify a feature of the offered storage. The requested reassignment decision remains unanswered.

Offer B identifies the media set, limits its proposed result to the encrypted local cache and names CE as the intended technique. Its proposal leaves two questions open: the relevant data history has not been established, and an external key-recovery store is listed with its status awaiting confirmation. B supplies no completed-operation evidence.

B has described a mechanism relevant to the requested result. Its unresolved preconditions still prevent the proposal from establishing that result. A's feature description and B's proposed technique should therefore receive different follow-up questions, while both remain short of evidence supporting acceptance.

For A, request an explanation of the proposed sanitization outcome and its scope from the responsible provider. For B, request the appointed specialist's assessment of the history and recovery questions, and the evidence that would support the eventual outcome. Neither inquiry calls for the buyer to perform an erase operation.

The comparison also avoids an unsupported equipment verdict. Missing evidence does not establish that A's drives failed a sanitization test. A relevant proposal does not establish that B's drives passed one. The useful finding identifies exactly what each offer establishes and what remains unresolved.

Connect implementation assurance to the actual outcome

A technical explanation of CE gives the reviewer a mechanism to assess. Evidence concerning the implementation addresses whether that mechanism can be relied on in the identified product and configuration. An account of a completed operation addresses a later, particular event. Keep these subjects visible when requesting supporting material.

NIST's July 16, 2026 FAQ distinguishes verification of successful completion from validation of whether the result is effective and its residual confidentiality risk acceptable. Its Revision 2 traceability discussion also recognizes that storage-device records may lack visibility into key sanitization performed in an external key-management system.

A completion report therefore needs a clear connection to the scoped media and the owner's acceptance requirements. Ask who reconciles the implementation evidence, remaining exceptions and outcome evidence. An unexplained success status cannot answer the open history and external-recovery questions in Offer B.

Keep the evidence request proportionate to the decision. It should help the designated reviewer resolve those questions, rather than accumulate unrelated product literature. CE's suitability remains a policy and technical assessment for the actual circumstances; neither the technique's name nor this article establishes regulatory compliance.

References: [D1][D2]

Carry the disposition decision into a separate physical scope

Once the responsible owner has determined the relevant disposition, surrounding equipment changes can be discussed through Leviathan's Hardware Refresh & Physical Support service. The service and project inquiry linked below are for a specifically agreed physical work package. Sanitization, forensic assessment, key management and secure disposal require separately appointed responsible parties; the physical engagement supplies no assurance of those outcomes.

For an initial discussion, provide a nonconfidential description of the affected equipment, site, intended physical change, approval owner and receiving team. Identify unresolved disposition dependencies without sending data contents, keys or sensitive security records. This gives the physical coordinator the scope needed to discuss the work while preserving the security owner's decision.

References: [L1]