Skip to content

Observatory ProtocolNode registryProvider

Provider

A hardware, software, model, data, connectivity or service supplier that enters by manifest for a stated scope and declares a tested exit path.

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

Provider role. (OBSP 0.1 §3) Presence, connectivity or a commercial relationship MUST NOT imply admission. (OBSP 0.1 §5.2) Every provider manifest MUST declare an exit path. (OBSP 0.1 §5.12)

Class
Operators, providers and stewards
Organisations that run deployments, supply components or maintain the specification.
Protocol role
PROVIDER Provider. (OBSP 0.1 §3)
Conformance profile
OBSP-PROVIDER Hardware, software, model and data provider (OBSP 0.1 §7.1)

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)

InterfaceBindingSources
AdmissionProvider manifest, SBOM and SLSA provenance; a SCITT receipt should be recorded(OBSP 0.1 §5.2; SPDX; CycloneDX; SLSA 1.0; 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

Accepts

Lifecycle and conformance

OBSP-PROVIDER 3 of 12 functions. (OBSP 0.1 §7.1) A level is reached only with the evidence it names. (OBSP 0.1 §7.2)

5.1Join5.2Admit5.3Describe5.4Time5.5Observe5.6Qualify5.7Federate5.8Orchestrate5.9Correct5.10Exchange5.11Prove5.12Exit and decommission
The twelve stages of the lifecycle. The stages in the type's profile are marked.

Conformance cases that apply

CaseWhat it testsKindEvidence
CT-PROVIDER-001Admit: provider manifest with supply-chain evidenceinvariantprovider-manifest supply-chain-receipt
CT-PROVIDER-002Describe: source releases and model manifestsschemasource-release model-manifest
CT-PROVIDER-003Exit: the provider names a data export and replacement pathinvariantprovider-manifest

Run these cases in the onboarding check

Levels

Declared
Signed self-declaration naming profile, version and scope.
Self-tested
Conformance report (obsp conformance run) produced by the participant, with digests of the tested artifacts.
Lab-tested
Conformance report (obsp conformance run) and lab test record from a qualified lab.
Qualified
Lab report plus field observation for the declared scope and a qualification-record.
Suspended
Suspension notice with reason.
Withdrawn
Withdrawal notice.

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)

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 protocol lists no open gap for this type.

Across the consortium

Related pages on the consortium's other networks, in their own words.

StandardsNexus Standards
Open standards to identify, describe, verify and cite risk information, which observations bound by the protocol can carry.nexustandards.com
IndexThe Global Risks Index
Country risk indicators that observations with provenance and quality can inform.risksindex.com
AcademyRisk Academy
Training for implementers and operators of observing systems.risksacademy.com
ReportsReports at Nexus Standards
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.

  1. OBSP 0.1 §3: Participant roles Observatory Protocol 0.1 (draft), CC BY 4.0.
  2. OBSP 0.1 §5.2: Admit Observatory Protocol 0.1 (draft), CC BY 4.0.
  3. OBSP 0.1 §5.12: Exit and decommission Observatory Protocol 0.1 (draft), CC BY 4.0.
  4. OBSP 0.1 §7.1: Profiles Observatory Protocol 0.1 (draft), CC BY 4.0.
  5. OBSP 0.1 §6: Wire bindings Observatory Protocol 0.1 (draft), CC BY 4.0.
  6. SPDX Software Package Data Exchange spdx.dev/ Checked
  7. CycloneDX CycloneDX specification cyclonedx.org/specification/overview/ Checked
  8. SLSA 1.0 Supply-chain Levels for Software Artifacts slsa.dev/spec/v1.0/ Checked
  9. IETF SCITT Supply Chain Integrity, Transparency and Trust working group datatracker.ietf.org/wg/scitt/about/ Checked
  10. JSON Schema 2020-12 JSON Schema draft 2020-12 json-schema.org/draft/2020-12 Checked
  11. OBSP 0.1 §4.3: Request context Observatory Protocol 0.1 (draft), CC BY 4.0.
  12. OBSP 0.1 §7.2: Conformance levels Observatory Protocol 0.1 (draft), CC BY 4.0.
  13. OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
  14. OBSP 0.1 §13: Sovereign deployment for every operator and environment Observatory Protocol 0.1 (draft), CC BY 4.0.
  15. in-toto in-toto supply chain framework in-toto.io/ Checked