Skip to content

Security

Open Asset Evidence describes how asset records can retain their source and be checked when shared. Security depends on the specification, the software that implements it, the organisations operating that software and the recipient's decisions.

Draft security guidance. These pages describe requirements and reference designs. They do not establish production readiness or independent security assurance. Existing demonstrations are not offered for reliance and must not receive personal, client or confidential data.

Start here

  • Trust and responsibilities: Who is responsible for a statement, a signing key, a check and the decision to use the evidence.
  • Verifier behaviour: The checks a verifier should perform and the limits it must preserve in its result.
  • Issuer and key security: Signing authority, key custody, public verification material and compromise handling.
  • Integration profiles: Security boundaries for websites, APIs, software components and agent connections.
  • Assurance and release: Evidence needed to support a security claim and to release a specific implementation.
  • Reporting security issues: Current reporting limitations and how to request a suitable contact without sending sensitive material.

What a successful check means

A valid signature establishes that the signed content matches the signature under the verification key. The recipient must separately establish whose key it is, whether that issuer is authorised for the statement, whether the evidence is sufficiently current and whether it meets the recipient's policy.

A signature does not make an observation or valuation true. A credential does not grant legal reliance, establish professional indemnity insurance cover or require an institution to accept it. Those questions depend on the professional source, the engagement and the recipient's separate arrangements.

Three statuses must stay separate:

  • Specification status: Which draft or released rules describe this record?
  • Credential status: What is known about this particular credential's validity, suspension, revocation or replacement at the relevant time?
  • Recipient acceptance: Has this recipient decided that the evidence is appropriate for this purpose under its own policy?

Publication of a specification does not approve credentials made using it. A credential being current does not mean a recipient has accepted it. A successful technical result is an input to acceptance, not the acceptance itself.

Current maturity

The documentation and reference work remain under development. Internal review and local tests provide evidence about particular code, inputs and versions; they also identify unresolved gaps. They do not establish the security of a deployed service, another implementation or a later release.

No production assurance, independent security audit, certification or end-to-end interoperability claim is made by these pages. The assurance requirements distinguish what has been observed from what a release would need to demonstrate.

An open standard still has security risks. Ambiguous rules can produce inconsistent checks; software and trust configuration can be compromised; an authorised issuer can sign an incorrect statement. The purpose of this section is to make those boundaries visible and define how an implementation should handle them, without publishing material that would expose people, credentials or systems.

Shared definitions · SD-JWT VC Binding · Verification Result Contract · Engagement and reliance