ECZ-ID Device Trust

Review connected-device, firmware, fleet and operator-identity evidence before reliance.

Free, local-first. No account is required for a workspace review, and device secrets, credentials, source code and private telemetry are not uploaded.

Useful for

• IoT and connected-product engineering teams
• fleet and device-platform operators
• security and product-assurance reviewers
• organisations that need a durable identity for a device or device family

What it looks for

ECZ-ID Device Trust reviews local device/fleet manifests, firmware and update references, attestation/identity references and related deployment evidence by the specialist detector. Results describe available evidence; they do not determine device security.

What you can do in under a minute

1. Open a trusted workspace containing the device or fleet configuration.
2. Run ECZ-ID Device Trust: Review Workspace.
3. Review observed and not-observed evidence locally.
4. Resolve existing proof, request current proof, or create/connect the free IoT Device Passport when you operate the subject.

Example use cases

• Review firmware/update and device-identity references before a deployment.
• Organise fleet evidence before a customer or insurer review.
• Re-check evidence after firmware or deployment changes.
• Give a connected product a persistent ECZ-ID IoT Device Passport without making the identity itself a metered product.

Result semantics

Results use neutral states such as observed, not observed, review recommended and re-check before reliance. Local policy decides whether the evidence is sufficient.

The free IoT Device Passport identifies the connected-product subject. It is not an approval, certification or safety guarantee. Fleet lifecycle/capacity and stronger Parent verification remain separate optional operating layers.

Privacy & permissions

Free vs operating services

• Free: local evidence review and permanent core IoT Device Passport identity.
• Optional paid layer: managed fleet lifecycle/capacity, currentness and stronger Parent verification where required.
• The identity is never changed merely because an operating-service allowance changes.

Machine-readable facts

First use

Install ECZ-ID Device Trust, open a trusted workspace, then run ECZ-ID Device Trust: Review Workspace from the Command Palette.

ECZ-ID is independent trust infrastructure. Third-party names describe compatible ecosystems only and do not imply endorsement or affiliation.