Help Centre

Getting Started

DestructLog generates a NIST 800-88 sanitization document from the asset data you provide. There is no account to create, no login, and no setup. The tool works through its API:

1. Prepare a CSV with your asset serial numbers, media types, and the sanitization method used. See How It Works for the full column reference.
2. Send the CSV to the /api/generate endpoint via an HTTP POST request. The tool parses the data, validates each row against the NIST 800-88 decision matrix, and returns a completed sanitization document.
3. Receive the document — a numbered record (format: DEST-YYYYMMDD-NNN) with per-asset detail, NIST citations, and summary counts. The document states plainly that it records what the operator entered and does not itself verify that any asset was sanitized.

Top Questions

What CSV format does DestructLog accept?

DestructLog accepts comma-separated (CSV), tab-separated (TSV), and pipe-delimited formats. The delimiter is detected automatically. Column headers are matched flexibly — for example, serial_number, serial#, asset tag, and asset id all map to the serial_number field. The required columns are serial_number, media_type, and method. Optional columns: make_model, date, verifier.

Which media types and methods are supported?

DestructLog supports all media types from NIST SP 800-88 Rev. 1: HDD, SSD, magnetic tape, optical disc, flash drive / USB, floppy disk, paper, and mixed media. Methods are Clear, Purge, and Destroy. Each row is validated against the standard's decision matrix — for instance, Clear (overwrite) is valid for HDDs but not for SSDs or flash drives. See the NIST 800-88 page for the full matrix.

Is my asset data stored or logged?

No. DestructLog processes the CSV data server-side during a single API request-response cycle. The data is parsed and validated in memory, then the document is returned. The submitted data is not stored, logged, written to disk, or retained after the response is delivered. DestructLog has no database, no persistent storage, and no retention mechanism. See the Privacy page for full details.

What does the generated document include?

Each numbered sanitization record (format: DEST-YYYYMMDD-NNN) includes: the organization name and issue date, a per-asset table listing serial number, make/model, media type, method, status, verifier, and date; NIST SP 800-88 citations for each method-media type combination; a summary section with counts by method and media type; validation notes for any flagged rows; and a disclaimer stating the document records what was entered and does not verify sanitization.

How do I set the organization name on the certificate?

The organization name is passed as a parameter in the API request. Include an organization field in your POST body alongside the CSV data. If omitted, the document uses "Unspecified Organization". There is no stored profile or saved preference — each request is self-contained.

Can I use DestructLog for audit evidence?

DestructLog produces a numbered document with per-asset detail and NIST citations that can be part of your audit documentation package. However, DestructLog is a documentation tool — it does not verify that any sanitization actually occurred. Your organisation is responsible for performing and verifying the sanitisation itself. The document's disclaimer states this explicitly. Review the Terms of Use for the full scope of the tool.

Known Limitations

DestructLog is a documentation tool, not a verification platform. The following limitations are by design and are not bugs:

• No asset management integration. DestructLog does not connect to any inventory system, CMDB, or asset database. Data is submitted per-request via CSV pasted into the API call.
• No verification. The tool does not verify that any drive was actually sanitized, destroyed, or purged. It documents what the operator enters.
• No data persistence. Asset data is not stored, logged, or retained after the response is delivered. There is no history, no dashboard, and no saved sessions.
• No user accounts. There is no login, no registration, and no user database. Each request is independent.
• No multi-organization batching. Each request produces a document for a single organization. Batch processing across multiple orgs is not supported.
• No paid tier yet. The service is currently free. A paid subscription tier with additional features may be introduced in the future, but nothing is available for purchase today. Any checkout or pricing page operates in test mode only.
• No email delivery. Documents are returned synchronously in the API response. DestructLog cannot email you the document, send notifications, or deliver certificates asynchronously.
• No certification authority. DestructLog does not certify anything on its own authority. The generated document is a record of operator-supplied data, not a certified statement.