Erasure Certificates: Import, Review and Corrections

“We wiped the laptop” is not a statement an auditor accepts. The auditor wants the report the erasure tool produced, attached to the device it was produced for, and a status on that device that a buyer, a regulator and your own outbound screen all read the same way. The platform stores the first and derives the second.

Where the evidence comes from

Import Blancco XML or CSV through /core/erasure/import. The preview separates reports ready to attach, reports already recorded and reports needing review. Automatic matching requires a reliable serial number identifying exactly one data-bearing device. Missing serials, all-zero serials, manufacturer placeholders and ambiguous matches stay in the import queue. A readable report with a failed wipe still imports as evidence of that failed result.

XML/CSV uploads allow 10 MB; manual PDF certificates allow 50 MB. You can import a batch even if every report needs review. Re-importing the same report content does not add another evidence version, assignment or queue item, even if the filename changes. A new report for a later wipe attempt can replace failed evidence. Changed content under the same certificate, or a report for a device with successful evidence, requires review. Direct XML/CSV uploads must identify one report with the device’s serial number.

Path B: upload the certificate by hand. For a tool without an export, or a destruction record, the operator uploads the PDF on the asset together with the method, who performed it, the date and notes. The provider is recorded as Blancco, Aiken or other.

The certificate on the asset

ReVend preserves the source that was supplied: the original XML or CSV file, Cloud response, or manually uploaded PDF. Importing XML does not create a provider PDF. The source remains available beside the structured result, and previous evidence versions keep their own source. Evidence packages retain the evidence selected when the package was created. ReVend records document access and keeps the provider’s report unchanged.

Correcting evidence

The device’s erasure history shows the current and previous evidence, its source, and who changed the assignment and why. Only your organization’s administrators and managers can replace existing evidence or move it to another data-bearing device. They review the source, select the destination and provide a reason. An ordinary import or queue match cannot silently replace successful evidence. If another user changes the evidence during review, refresh before confirming the correction.

The data-security grade

For imported Blancco evidence, D3 requires a certificate and successful erasure and verification of every drive. Successful erasure without complete verification can remain D2. D1 represents weaker evidence; failed or partial erasure remains D0. The original report stays available. Reading a signature does not mean ReVend has cryptographically verified it.

The gate

For data-bearing assets, erasure evidence is required before a direct sale can be recorded or shipped, and the market-ready check for Market and Auction asks the same question. Commercial urgency does not get an exception here. A retry that succeeds, or a destruction record with its own certificate, is how an asset gets past it.

Cloud sync and resuming an import

Configure the Blancco connection under Settings > Core > Audit tools. Test the connection and a representative import with your own Blancco environment before relying on automatic delivery; saving a configuration alone does not prove that connection works. Each sync processes a bounded portion and resumes saved progress on the next run. Interrupted runs keep the last completed position and recognize reports already stored. Reports stay in review when automatic matching or automatic attachment is disabled. Carbontrace may recalculate after newly applied evidence when the integration is enabled; a recalculation failure does not undo the evidence import.