Wipe reports
Wipes (/wipes) is the ledger of every wipe your kiosks have reported — one row per drive, per wipe, with its outcome and its certificate. Because every certificate hangs off a wipe result, this page is also the certificate listing: there is no separate certificates index.
The wipes grid
A spreadsheet-style grid, paginated at 100 rows per page, newest first. Columns:
| Column | Contents |
|---|---|
| Vendor | Derived from the drive model string |
| Model | The drive model |
| Serial | The drive serial number |
| Capacity | e.g. "512 GB" |
| Media Type | SSD or HDD, read from the matched machine's fingerprint |
| Method | The wipe method, e.g. NIST 800-88 R2 Purge |
| Source | The machine the drive was in (see below) |
| Duration | e.g. "1h 12m" |
| Status | Outcome badge (see below) |
| Technician | The operator |
| Completed | Completion time |
| Certificate | The certificate state (see below) |
Status badges
| Wipe status | Badge |
|---|---|
| completed | Pass (green) |
| failed | Fail (red) |
| anything else | The status, titleized, in grey |
A wipe with no recorded status is a legacy record and reads as completed — it shows Pass.
Source machine matching
The Source column ties a drive back to the machine it was wiped in, by matching the drive's serial number against the storage serials of the machines in your inventory. A match renders as a link that opens that asset's drawer. Wipes performed on a hotswap station show the label "Hotswap" instead — the drive was in a bay, not inside a fingerprinted machine. An unmatched drive shows "—".
The Certificate column
Each row's Certificate cell tells you exactly where its certificate stands:
- Issued — a link labelled with the certificate number, e.g.
CW-000123, which opens the Certificate of Sanitization in a new tab, alongside a link to the same wipe's Erasure Report. - In progress or failed — a badge: Pending, Generating, Complete, or Failed.
- Not certifiable — muted text "Not issued", with the tooltip "Certificates are only issued for successful, verified wipes".
Only successful, verified wipes certify. A wipe that failed, or whose validation flagged it for review, stays on this page as evidence but never gets a certificate.
Downloading a certificate
Every certified wipe has two documents: the one-page Certificate of Sanitization and the fuller Erasure Report, generated together under one certificate number. The CW-… link points at GET /certificates/:id for the certificate, and GET /certificates/:id?document=report fetches the report. Each responds with a 302 redirect to a presigned URL for the PDF, valid for five minutes. Certificate PDFs are stored privately — the presigned redirect is the only way to fetch one, and it requires being signed in to the owning account. If the PDF isn't ready yet you're redirected back with "Certificate is still generating."
Anyone — no account required — can check a certificate's authenticity at the public verify endpoint:
curl https://averase.com/certificates/{id}/verify
Response
{
"valid": true,
"certificate_number": "CW-000241",
"account": "MAESON Technologies LLC",
"drive_serial": "S6MZNF1WA04527",
"drive_model": "SAMSUNG MZVL2512HCJQ",
"drive_capacity_gb": 512,
"wipe_method": "NIST 800-88 R2 Purge",
"passes_completed": 1,
"completed_at": "2026-08-01T14:22:07Z",
"signed_at": "2026-08-01T14:22:09Z"
}
See Certificates for how certificates are generated and signed, and Certificate verification for the full endpoint reference.
Sorting
The Sort menu offers a fixed list of whole-table reorders:
- Ascending / Descending by Completed
- A→Z / Z→A by Model
- Capacity, high→low
- Duration, long→short
- Status, A→Z
As on Inventory, search, filter, and sort operate client-side within the loaded page of 100 rows, and Push sends selected rows (reading e.g. "1 Wipe") to a connected integration.