Key concepts
Organizations, proofs, certificates, licenses and roles, in a few lines each.
A handful of words come back on every page of the portal. This page explains them once.
Organization
Your account belongs to an organization: your company, or the entity your provider opened for you. An organization can have sub-organizations (a subsidiary, a site, an end client). You see the data of your organization and of its sub-organizations, never the data of another client.
Every proof is bound to the organization it was produced for. A proof generated for another organization is refused when you upload it.
Proof
A proof is the file the wipe agent writes at the end of an erasure session, with the .der
extension. It describes the machine, each disk and the result of its erasure. The agent signs it
and encrypts it, so nobody can alter it on the way: the portal checks the signature before doing
anything else.
A proof goes through several statuses, from Received to Certified. See Proof statuses.
Certificate
When a proof passes every check, the portal issues an erasure certificate. It comes in two forms:
- a PDF signed electronically (PAdES signature), with your branding and a QR code that leads to the public verification page;
- a canonical JSON (
canonical.json), the machine-readable version of the same content, whose fingerprint (canonical hash) identifies the certificate.
Each certificate also carries a public verification code (format XXXX-XXXX-XXXX-XX). When
your instance is connected to a blockchain, the certificate fingerprint is anchored there:
recorded in a public transaction that nobody can modify afterwards.
License
Certifying an erasure consumes licenses: one license per disk erased successfully. A machine with two disks erased successfully uses two licenses; a disk whose erasure failed uses none.
Your licenses come from license grants, issued by your provider, with a quantity (or unlimited use) and a validity period. Your administrator allocates them to your organization and its sub-organizations. When an organization runs out of licenses, its new proofs wait in Awaiting license instead of being refused. See Licenses.
Roles
| Role | For whom | In short |
|---|---|---|
| Client admin | The person in charge of Wipe in your company | Everything in the portal: proofs, certificates, licenses, users, settings |
| Technician | The people who run the wipes | Upload proofs, follow them, download certificates |
| Auditor | An internal or external auditor | Read-only access to proofs, certificates, usage and the audit log, for a set period |
The full table is in the introduction.