Skip to content
ECZ-IDIoT

Workflow bundle · ECZ-ID IoT

ECZ-ID Connected Platform Assurance Bundle

Connect API and device evidence around the platform customers actually use.

A cross-family bundle for connected platforms where APIs, apps and devices form one customer experience.

Type
Bundle
Price
Not restated on this site; TrustOps publishes the current price and availability
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

Customers experience a connected platform as one product: the API they integrate, the backend services behind it, the devices and apps that call it. Reviewers ask about all of it at once while each component's evidence lives with a different team, so the same organisation answers the same questions several times and nobody sees how the parts relate.

Built for

  • Connected platforms
  • IoT SaaS
  • API-led products

What changes

  • One platform review story
  • Less duplicated evidence
  • Clearer dependency context

What you receive

Concrete deliverables, not a vague trust score.

  • Relevant specialist kits
  • Cross-entity relationship context
  • Customer-facing platform artefacts
A connected-platform view
Platform
The customer-facing platform and its boundary
Components
APIs and devices — each with its own ECZ-ID
Operator
The organisation accountable for each component
Dependencies
Which component depends on which, where published
Boundary
A graph of distinct identities — never one merged Passport

Illustrative structure.

How it works

A short path from need to something usable.

  1. Define the platform boundary.

  2. Map the component identities.

  3. Complete the evidence.

  4. Package the connected view.

How it relates to your Passport

Each component keeps its own free Passport — APIs and devices alike. The bundle uses the Digital Entity Graph to show how they relate, and brings the ECZ-ID Connected Product Cybersecurity Evidence & CRA/PSTI Readiness Kit together with the evidence for the platform's other components.

Use cases

  • A connected product whose devices report to APIs that customers also rely on.
  • A platform team answering one platform review instead of a separate review per component.
  • Showing a buyer how each connected device relates to the other components behind the platform.

Tiers and price

Price and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. This site does not restate this product's price; TrustOps publishes its current tiers, price and availability, and shows them before anything is bought.

How it is arranged

  1. TrustOps acquires

    TrustOps publishes the tiers and holds payment and entitlement whenever it is offered.

  2. Dashboard operates

    Once you hold it, it appears in your Dashboard, where you operate it.

  3. Resolver proves

    Public facts stay on the Resolver; holding it never changes what a record proves.

Privacy, security and evidence

What is collected, published and kept.

  • Each component keeps its own identity and record.
  • Only published relationships appear in public views.
  • A platform view is not a certification of the platform.

Boundaries

The claims stop here.

  • A connected platform remains a graph of distinct identities, not one merged Passport.

Integrations and questions

Works with what you already run.

  • API and IoT Passports, as relevant.
  • Graph Intelligence for the platform's dependency view.
  • The device platforms and API gateways you already run, unchanged.
Does the platform get one Passport?
No. A connected platform remains a graph of distinct identities. Each component keeps its own free Passport.
Is this a certification of the platform?
No. It organises evidence around the platform. It does not certify it as secure, compliant or approved.