Audit Tools: Where the Erasure-Tool Configurations Live

Erasure reports arrive in several shapes: Blancco XML/CSV exports, API-sync payloads, files from other vendors. /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

Your organization stores each tool’s provider, connection type, endpoint, matching preference and import settings under /settings/core/audit-tools. Auto-import, auto-match, automatic specification completion and automatic evidence attachment are separate switches. Blancco automatically attaches evidence only when auto-match and evidence attachment are enabled and serial-number matching identifies exactly one data-bearing device. Other matching preferences send reports to review. Credentials are stored as protected secrets; saved forms show masked hints and leaving a secret field empty retains the saved value.

Checking your connection

An administrator or manager can test a supported Blancco configuration, use “Sync now”, or enable scheduled import. Validate the connection and a representative report import against your own Blancco environment before relying on it. A saved configuration is not a successful connection test. Aiken configurations and review tools remain available, but do not imply an automatic Aiken sync. The page shows connection status and recorded import counts, with a link to the review queue.

Disconnecting

Disconnect takes a configuration out of service: automatic imports stop and the stored credentials are revoked. Previously imported reports, unmatched evidence and the sync history stay visible, because an auditor who asks how a certificate got attached in March does not care that the integration was switched off in June. The connection is temporary. The evidence is not.

Import-queue behavior

A new Blancco report can attach to one unambiguous device and retains its original source. Missing, placeholder or ambiguous serial numbers go to the import queue. Operators can resolve an initial match or dismiss a record with a reason. Changed evidence for the same certificate, or evidence that would replace a successful report, requires an administrator or manager to review the source and confirm the correction with a reason. Previous evidence and assignment history remain available. Repeated content does not create another queue item. Audit reports can also create a device when they contain enough hardware identity.

Failure handling

Each scheduled run processes a bounded portion, gives other configurations a turn and resumes unfinished work later. Only one worker processes a configuration at a time. Progress advances after the entire fetched page is stored; a failed run retries from the saved position without counting the same evidence twice. A large backlog is not skipped after an arbitrary page limit. Import errors are recorded in Activity, and one organization’s failure does not stop the others. Reports awaiting review stay there until someone resolves or dismisses them.