Observatory ProtocolNode registryAttestation and proof verifier
Attestation and proof verifier
Appraises attestation evidence and proof challenges and issues results bound to a nonce, an expiry and a scope.
- Version
- 0.1.0-draft
- Status
- Draft specification
- Specification
- CC BY 4.0
- Code
- Apache-2.0
- Steward
- GCRI Canada
- Source
- obsp-0.1-foundation
Role
Verifier role. (OBSP 0.1 §3) A verifier MUST bind the result to a nonce and an expiry. (OBSP 0.1 §5.1) A receipt MUST be signed and bound to the challenge, the evidence digests and the scope. (OBSP 0.1 §5.11)
- Class
- Assurance
Verifiers that appraise evidence and proof challenges. - Protocol role
VERIFIERVerifier. (OBSP 0.1 §3)- Conformance profile
- OBSP-SITE carries the local verifier role for proofs. OBSP 0.1 defines no stand-alone verifier profile.
- Technology domains
- Security, identity and supply chain
Interfaces
The planes and bindings this type uses. Bindings are normative for OBSP 0.1; radio and link layers follow their own standards. (OBSP 0.1 §6)
| Interface | Binding | Sources |
|---|---|---|
| Attestation | RATS passport and background-check models | (IETF RFC 9334; OBSP 0.1 §5.1) |
| Evidence | SCITT transparency receipts | (OBSP 0.1 §6; IETF SCITT) |
Schemas it emits and accepts
Each document is a JSON Schema 2020-12 contract. Open one in the schema explorer. (JSON Schema 2020-12) Every request, command and event also carries a request context. (OBSP 0.1 §4.3)
Emits
attestation-resultAttestationResultproof-receiptProofReceipt
Accepts
attestation-evidenceAttestationEvidenceproof-receiptProofReceiptrequest-contextRequestContext
Lifecycle and conformance
OBSP-SITE carries the local verifier role for proofs. OBSP 0.1 defines no stand-alone verifier profile.
| Clause | Stage | In a profile | Contract |
|---|---|---|---|
| §5.1 | Join | No | Contracted |
| §5.2 | Admit | No | Contracted |
| §5.3 | Describe | No | Contracted |
| §5.4 | Time | No | Contracted |
| §5.5 | Observe | No | Contracted |
| §5.6 | Qualify | No | Contracted |
| §5.7 | Federate | No | Open gap G-FED-1 |
| §5.8 | Orchestrate | No | Open gap G-ORCH-1 |
| §5.9 | Correct | No | Contracted |
| §5.10 | Exchange | No | Open gap G-EXCH-1 |
| §5.11 | Prove | No | Open gap G-PROVE-1 |
| §5.12 | Exit and decommission | No | Contracted |
Identity, attestation and security
Requirements of the security model that apply to this role. (OBSP 0.1 §8)
- Architecture
- Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing (OBSP 0.1 §8)
- Workload identity
- SPIFFE-style SVIDs, rotated; no shared secrets (OBSP 0.1 §8)
- Supply chain
- SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware (OBSP 0.1 §8)
- Privacy
- Observation data that can identify a person is a declared data class with its own policy; default is not to collect it (OBSP 0.1 §8)
Interoperability profile and standards
The primary standards this type draws on. Alignment with a standard is stated as alignment. It is not an approval by the standards body. (OBSP 0.1 §13)
- IETF RFC 9334Remote ATtestation procedureS (RATS) Architecture(IETF RFC 9334)
- TCG TPM 2.0Trusted Platform Module Library Specification(TCG TPM 2.0)
- TCG DICEDevice Identifier Composition Engine architectures(TCG DICE)
- IETF SCITTSupply Chain Integrity, Transparency and Trust working group(IETF SCITT)
Not yet defined
What the protocol does not define for this type in version 0.1, stated as the specification states it. Nothing here is filled in from elsewhere.
- The proof verifier is an open gap in OBSP 0.1 (G-PROVE-1). (OBSP 0.1 §9)
Across the consortium
Related pages on the consortium's other networks, in their own words.
- Standards
- Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.nexustandards.com
- Index
- Country risk indicators that observations with provenance and quality can inform.risksindex.com
- Academy
- Training for implementers and operators of observing systems.risksacademy.com
- Reports
- Published evidence with provenance, citation and corrections.nexustandards.com/nexus-reports
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.1: Join Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §5.11: Prove Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
- IETF RFC 9334 Remote ATtestation procedureS (RATS) Architecture www.rfc-editor.org/rfc/rfc9334.html Checked
- IETF SCITT Supply Chain Integrity, Transparency and Trust working group datatracker.ietf.org/wg/scitt/about/ Checked
- JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
- OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
- TCG TPM 2.0 Trusted Platform Module Library Specification trustedcomputinggroup.org/resource/tpm-library-specification/ Checked
- TCG DICE Device Identifier Composition Engine architectures trustedcomputinggroup.org/work-groups/dice-architectures/ Checked
- OBSP 0.1 §9: Gaps register Observatory Protocol 0.1 (draft), CC BY 4.0.