Skip to content
ECZ-IDIoT
Free Passport: Get a FREE IoT Passport

Works alongside

What an ECZ-ID IoT Passport sits beside

An IoT Passport complements the device identities, platforms, certificates and supply-chain records you already run. It publishes who is accountable for the device and, where declared, its manufacturer and model, and leaves provisioning, authentication and updates where they already live.

Native where you operate. ECZ-ID where you interoperate.

Across the device lifecycle

Who does what, at every stage of a device's life

Your platforms keep doing their jobs at each stage. The ECZ-ID record adds the part nobody outside them can otherwise see.

  1. Manufacture and commission

    Your systems: Manufacturing and PKI provisioning issue the device its credentials and its internal identifiers.

    ECZ-ID adds: The device's public ECZ-ID, with the accountable organisation on the record, bound to its product page and documentation.

  2. Deploy and install

    Your systems: The cloud IoT platform or device registry enrols the device under its own identity and authenticates it.

    ECZ-ID adds: A record anyone else can resolve — an installer, a customer, a buyer — without access to your platform.

  3. Operate and service

    Your systems: Device-management and field-service systems monitor, configure and repair the device.

    ECZ-ID adds: Current public state and evidence that a service partner or customer can re-check.

  4. Software and firmware change

    Your systems: Build, signing and update systems produce and ship each release, with its SBOM and provenance.

    ECZ-ID adds: One enduring identity those release records are organised around; the ECZ-ID does not change with the version.

  5. Ownership or custody change

    Your systems: Platforms re-enrol the device and rotate or re-issue its credentials for the new operator.

    ECZ-ID adds: An authority change on the same ECZ-ID, kept as lifecycle evidence, so the history travels with the device.

  6. Decommission and retire

    Your systems: Platforms de-enrol the device and revoke its credentials.

    ECZ-ID adds: Its lifecycle state on the public record, with the essential evidence of its life kept.

Provider-native identities. The identities your cloud provider, IoT platform and PKI give a device stay native, and keep doing the work they do today. ECZ-ID never issues device credentials, never holds key material and never sits in the authentication path. It adds the one identity everyone outside your platforms can resolve.

Adjacent systems

What each already does, and what the Passport adds

ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.

  • Cloud IoT platforms and device registries

    What it does
    Provision, connect and manage individual devices.
    What an ECZ-ID adds
    A public, operator-linked identity for each device that anyone can resolve, carrying no raw serial number, MAC address or location. The platform's own device identity stays where it is.

  • Device certificates (X.509)

    What it does
    Authenticate an individual device to your services.
    What an ECZ-ID adds
    A printable public identity for the device that points to its accountable operator — never its key material, and never a replacement for its certificate.

  • GS1 product identifiers

    What it does
    Identify trade items across supply chains.
    What an ECZ-ID adds
    An operator-linked device identity that can be resolved alongside the product's trade identifier. It never replaces the GTIN.

  • Firmware and software supply-chain tooling

    What it does
    Build, sign, describe and ship the firmware and software a device runs, including the SBOM and provenance records for each release.
    What an ECZ-ID adds
    One enduring device identity those release, SBOM and provenance records can be organised around, so evidence follows the product through updates instead of living in detached files.

  • Manufacturing, device-management and field-service systems

    What it does
    Provision, enrol, update, service and decommission devices, and hold the manufacturer's and operator's own records about them.
    What an ECZ-ID adds
    A public record of which organisation answers for the device at each stage, which those systems can link to without exposing their internal identifiers.

Naming a kind of system here states what it does and what ECZ-ID adds beside it. It implies no partnership, endorsement, certified integration or joint product.

Adjacent identities

The Passports that surround this one

Each is a separate subject with its own operator and its own identity. None is issued for you, and none is implied by holding this one.

  • ECZ-ID API Passport™

    Devices report to, and are managed through, APIs. The API is identified separately from the devices that use it.

  • ECZ-ID Service & Workload Passport™

    Fleets report into cloud services and workloads, which are separate enduring subjects with their own Passports.

  • ECZ-ID Agent Passport™

    Where an agent acts on devices, the agent is a separate subject with its own Passport — never part of the device's.

Read this as carefully as the rest

An ECZ-ID does not replace any of these

An ECZ-ID IoT Device Passport is a persistent, resolver-verifiable identity for something you operate. It records who operates it, what has been declared and bound, and what the current public state is. It is not a substitute for, and must never be presented as replacing:

  • device security
  • network security
  • authentication
  • firmware security
  • safety engineering
  • device-management platforms

An ECZ-ID does not make a device safe, secure or correct, and it is not a certification, approval or test result. Your policy decides what to do with what the record says.

Where next

Keep going with ECZ-ID IoT.

Get a FREE IoT Passport