Raidiam Connect/Software Identity & Attestation

Verify which software instance is connecting

Trusting an application doesn't mean you can trust every running copy. Software Identity & Attestation gives each instance a unique cryptographic identity, backed by evidence from its environment, so you can verify which instance is connecting and control what it can access.

Trusting the application doesn't mean you can trust every instance

A bank trusts a third-party AI assistant to access its APIs. But how does it know whether the instance connecting is legitimate, rather than an unauthorised copy using the same identity?

Each instance has its own key and evidence, so it can be verified and revoked separately

  • Evidence

    Refuse copies that can't prove where they run

    An instance presents evidence from the environment it runs in, such as a SPIFFE workload identity (an open standard for identifying cloud workloads), a cloud workload identity or a supported device attestation mechanism. A copy without acceptable evidence is refused.

  • Instance key

    Tell instances apart by their own keys

    Each instance has its own cryptographic key, generated where it runs, instead of a credential shared across copies.

  • Federation

    See who stands behind each instance

    A verified instance is tied to its software and provider in the trust framework managed in Raidiam Connect, so organisations that use that trust framework can check who stands behind it.

  • Revocation

    Revoke one instance and keep the rest

    If one instance is compromised, you can revoke trust in it, and other instances of the same application can keep working.

An instance proves where it runs, your authorisation server verifies it, and you decide what it may do

Proving which instance is connecting and deciding what it may do are separate steps, handled by different parts of the system.

  1. The software provider and the connector have recognised identities in Raidiam Connect, and each instance is identified by its own key.

    • Software IdentityApplications and their providers have recognised identities, which can be linked to a trust framework managed in Raidiam Connect.
    • Instance IdentityEach instance has a distinct identity, so it can be recognised and managed independently.
Register
Connector recordReady
  • 1Provider recognised.
  • 2Connector software recognised.
  • 3Instances identified by their own keys.
  • Provider
  • Software
  • Instances

Same software. Two instances. One compromised.

A bank allows customers to connect a trusted third-party AI assistant to its APIs. Two instances of the same software are running in different environments.

SoftwareInstance ATRUSTEDInstance BTRUSTEDBank
  1. Both instances generate their own cryptographic keys and present evidence from where they're running, for example a SPIFFE workload identity from a cloud environment. This evidence is bound to each instance's unique key.

The outcome: One compromised instance. One targeted revocation. No unnecessary disruption to other instances.

See instance attestation in action

From attestation to access control

Evidence

Software Identity & Attestation

Establishes verifiable evidence about each running instance and its cryptographic identity.

Management

Trust Control Plane

Sits at the centre of Raidiam Connect. It recognises software identities, establishes the trust relationships between organisations in a federation and governs who takes part.

Access

Your authorisation and enforcement infrastructure

Your authorisation servers, API gateways and services use the identity, attestation and trust information to make and enforce access decisions. Connect's Identity & Access Management can be your authorisation server, or you keep your own.

Raidiam Connect works alongside the identity and API security platforms you already run.

Raidiam's agent showcase demonstrates instance attestation working

The agent showcase is a working demonstration, built with fictional organisations, of the mechanisms on this page:

SPIFFE workload identityManaged workstation identityA key for each instanceattest_jwt_client_authDPoP token binding

Raidiam Connect, the platform this capability is part of, runs national trust frameworks in production.

300B+

API calls each year

2000+

organisations

100M+

consumers served

8

national trust frameworks

  • ISO 27001
  • SOC 2 Type II
  • PCI DSS 4.0
  • FAPI 2.0 Certified
  • Cyber Essentials

Figures published by Raidiam for Raidiam Connect in production, in open banking and open finance.

Common questions about Software Identity & Attestation

Build Once. Expand Everywhere.

Where will your ecosystem take you?

Whether you're a regulator building a national digital economy, an enterprise platformising across brands and clouds, or a bank that wants to stop rebuilding trust for every new use case, there's a next step.

See It in Action

See how one investment in Raidiam Connect covers your first use case, and the next hundred.

See the Proof

Explore how governments, regulators and enterprises are using Raidiam to deliver trusted digital ecosystems.

Have questions first?

Tell us about your ecosystem and we'll show you where Raidiam fits.