Audit Tools: Where the Erasure-Tool Configurations Live

Erasure reports arrive in several shapes: Blancco XML/CSV exports, API-sync payloads, and later other vendor formats. /settings/core/audit-tools is where a tenant stores provider configuration. /core/erasure/import is the manual Blancco batch import. /core/inventory/import-queue is the review place for reports or wipe certificates that could not be attached automatically to an asset.

Tool configurations

For each erasure tool a tenant uses, ReVend OS stores a configuration row: provider, connection type, API or Console endpoint, credential references, match field, and auto-import settings. Sensitive values are stored as external secrets; the configuration row only shows masked hints.

What is live

Blancco Cloud/API sync is live. An admin or manager can test the connection, run "Sync now" manually, or enable auto-import so the hourly cron fetches new reports. Aiken has configuration and review surfaces, but it does not import or sync yet; provider-specific import/sync work is still required before it feeds data automatically.

Import-queue behaviour

When a Blancco bulk file or sync report matches an asset by serial number, ReVend OS attaches the wipe certificate to the existing asset and stores the original evidence document. Records without an asset match go to the import queue, where the operator can link them manually or dismiss them with a reason. Audit reports can also create a new asset when the report itself carries enough hardware identity.

Failure handling

Sync and import failures are logged as activity events. A failed tenant sync does not stop the other tenants. Unmatched records do not disappear: they stay in the review queue until someone resolves or deliberately dismisses them.