SANITIZE

CertifiedNIST SP 800-88 Rev. 2 · DoD 5220.22-M · IEEE 2883

support@datasanitizationpro.com+91-852-770-9690
Get a Free Trial

Reports & Certificates

The two documents the software produces, published in full so you can check them before you buy anything.

Every job the software finishes ends in a document. A sanitization run produces a certificate; a hardware test produces a test report. Both are PDFs, both are generated on the machine that did the work, and both are what you hand to an auditor, a client or a buyer.

Most people only find out what is in that document after they have paid for the software. Both of our competitors put their sample behind a registration form. We publish ours outright — the real exports, with nothing taken out — because a document you cannot read is not evidence of anything.

What Goes Wrong

The Risks This Removes

A Spreadsheet Is Not Evidence

A row saying a drive was wiped proves that someone typed a row. It carries no serial, no method, no reading taken from the drive itself, and nothing that would fail if it were altered afterwards.

The Gap Between Wiping and Proving

Most teams can erase a drive. What they cannot do, months later, is show which drive, by which method, on what date, and that it was checked afterwards. That gap is what an audit finds.

Samples You Cannot See

A sample certificate behind a registration form tells you nothing until you have given up your contact details. You end up judging the document after the decision instead of before it.

How It Runs

The Process, Step by Step

01

The Run Records Itself

The drive is identified by serial, firmware and interface before anything is written. Capacity, SMART health, temperature and power-on hours are read from the drive at that moment, not typed in.

02

Verification Is a Separate Read

After the write passes complete, the drive is read back and hashed. The certificate carries both the pre-sanitization and the post-sanitization hash so the two can be compared rather than trusted.

03

The Document Is Generated on the Spot

The PDF is built on the machine that did the work, with the host system's own identity — manufacturer, model, serial, chassis, UUID, BIOS — recorded alongside the drive's.

What Is in the File, and What Is Not

  • The drive's own serial number, firmware revision and interface, read from the device.
  • The standard and method selected for the run, and the number of write passes it performed.
  • The verification algorithm, with the hash captured before the run and the hash verified after it.
  • The operator who ran the job, who approved it, and the organization the asset belongs to.
  • The host machine's identity, so the certificate can be traced to the workstation that produced it.
  • No customer data. The report describes the asset and the process, never the contents of the drive.
Take It with You

Sample Documents

No form, no email address. The files open straight away.

Sanitization Certificate

A completed erasure run on a single drive, from the standard chosen to the hash that proves the drive reads back clean.

  • Report ID, job ID, generated timestamp and elapsed duration
  • Compliance summary — status, standard, method, verification and outcome
  • Asset and custody — operator, approver, final release team and organization
  • Drive detail — model, serial number, firmware, interface, capacity and sectors processed
  • Drive health at the time of the run — SMART status, temperature and power-on hours
  • Sanitization detail — write passes, technique, purpose, start and completion times
  • The host machine — manufacturer, model, serial, chassis, UUID, BIOS, OS, processor and memory
  • Verification — the algorithm used, with the pre-sanitization and post-sanitization hashes
  • Authorized validation block
Download the samplePDF · 635 KB

PC Hardware Test Report

A full diagnostic pass over a machine — what works, what is degraded, and what the readings were at the time.

  • Report ID, job ID, start and completion times and duration
  • Overall verdict and grade
  • Result distribution across pass, warning and fail
  • Subsystem health — CPU, memory, storage, display, battery, cooling, network, audio, camera, keyboard, Bluetooth, motherboard and BIOS
  • Every test with the reading it returned, its result and the time it ran
  • System information — machine, manufacturer, model, serial number, BIOS and operating system
Download the samplePDF · 641 KB
Questions

Frequently Asked Questions

Are these real exports or mock-ups?

Real exports. Both files are produced by the desktop application in the ordinary way and published unedited. The asset details in them are from our own test hardware.

Do I have to give an email address?

No. Both files are linked directly on this page. There is no form and nothing is recorded when you download them.

Can the PDF be altered after it is issued?

The files are generated with document protection set, and the verification hashes are part of the document. A changed report no longer agrees with the readings it carries.

Can we put our own organization on the certificate?

Yes. The organization, the operator, the approver and the final release team are all recorded on the report from the details set in the application.

Is there a report for a machine that was tested but not wiped?

Yes — that is the second file. The hardware test report is produced by a diagnostic pass on its own and is what you would use to grade a machine for resale rather than to prove erasure.

Tell us what you need

Run It on Your Own Hardware

The trial produces the same two documents on your machines, with your organization's details on them.

Get a Free Trial

Goes straight to our engineers. No newsletter, no call centre.