Identity Trust
Is the identity and evidence trustworthy within the method/source scope?
CHECKID · SERVICE TRUST
Service Trust
A regulated organisation must be able to trust not only an identity result but also how the service is operated, changed, supported and recovered.
SERVICEPurpose → Method → Result
TRUSTSource → Evidence → Scope
OPERATIONSSaaS · API · SDK · SLA
FOUR TRUST LAYERS
A badge does not replace the full trust model
Identity · Evidence · Technical · Service
Evidence Trust
Can the result be traced to transaction, provenance, method and limitations?
Technical Trust
Are security architecture, certificates, platform controls and attack boundaries evidence-backed?
Service Trust
Are availability, incidents, support, change, continuity and responsibility transparent?
Certificate ≠ Service SLA
Technical certification does not replace SLA, incident process or business continuity.
Public vs contractual
The website publishes public principles and evidence; specific SLA/NFR values remain in contractual documents where applicable.
SERVICE TRUST
Operational controls need owners and evidence
Public disclosure is separate from contractual commitments.
| Domain | Question | Evidence source |
|---|---|---|
| Availability | How is service availability managed? | Service architecture / SLA |
| Incident | Who communicates, classifies and recovers? | Incident process / support agreement |
| Change | How are API/service changes governed? | Version/deprecation/release governance |
| Continuity | Where are continuity/DR obligations defined? | NFR/BCP/contract |
| Support | Which channel/escalation path applies? | Support agreement |
| Reporting | Which operational/evidence reports are available? | Service operations source |