Observatory ProtocolOpen developmentSecurity and privacy
Security, privacy and operator sovereignty
The security model, the privacy rules and the requirements that keep every deployment under its operator's control.
- 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
Security model
The security requirements of every deployment. (OBSP 0.1 §8)
| Area | Requirement |
|---|---|
| Architecture | Zero trust (NIST SP 800-207): every request is authenticated, authorised and logged; network position grants nothing |
| Device identity | Attested; hardware root where the class has one; short-lived certificates; revocation within the site cell's offline window |
| Workload identity | SPIFFE-style SVIDs, rotated; no shared secrets |
| Keys | Site cell keys held by the grid operator; customer-held keys for upstream services; HSM or TPM-sealed where available |
| Supply chain | SBOM, SLSA provenance, signed artifacts, TUF update metadata, SUIT for firmware |
| Time | Authenticated time (P3, §5.4); time integrity gates receipts |
| OT environments | IEC 62443 zones and conduits for industrial deployments |
| Privacy | Observation data that can identify a person is a declared data class with its own policy; default is not to collect it |
| Break glass | Logged, time-bound, receipted |
Threats the conformance suite MUST test: rogue node, cloned identity, replayed plan, rolled-back update, spoofed GNSS time, location fraud, poisoned observation, compromised provider control plane, partitioned federation.
Security and disclosure
How vulnerabilities are reported and fixed. Vulnerabilities are reported privately through the security form. (Observatory Protocol policy, Security and disclosure)
SEC-1- Vulnerabilities are reported privately (SECURITY.md); they are acknowledged within 2 working days.
SEC-2- A fix that changes the protocol goes through an expedited OIP and is disclosed with an advisory once implementers have had a reasonable window.
SEC-3- CI pins and verifies every downloaded tool by digest and scans the full history for secrets on every change.
Data and privacy
What personal data the protocol and its gateways may handle. (Observatory Protocol policy, Data and privacy)
DAT-1- The contracts carry no personal data fields; a deployment that observes people does so under its operator's law and policy.
DAT-2- Gateways collect only what a contribution needs and use nothing for marketing; each site's privacy notice applies.
DAT-3- Missing data is a typed state, never zero or an empty string.
Operator sovereignty
Every operator runs every function in the environment it chooses, under its own control (specification §12 and §13). (Observatory Protocol policy, Operator sovereignty)
OSV-1- The protocol never requires a central service, registry, key, cloud or approval; federation is a choice of the operator.
OSV-2- Every operator holds its own keys, identity, update mirror, telemetry and data, in its own jurisdiction when it chooses.
OSV-3- Every environment of registers/deployment-environments.yaml, from air-gapped to public cloud, is supported by the same contracts.
OSV-4- Data and deployments belong to their operator. Nothing in the protocol transfers ownership of data or deployments to another party.
OSV-5- National adoption, profiling or translation of the protocol is a national decision taken by the competent national body.
Operator sovereignty overlay
Where the operator is not the publisher of the software, the overlay OBSP-SOV applies on top of any profile. (OBSP 0.1 §12)
SOV-1- No outbound connection the operator has not configured.
SOV-2- No publisher credential, key or trust anchor in a build; operator generates every root.
SOV-3- Offline-verifiable signed releases from an operator-controlled mirror.
SOV-4- Telemetry only to operator-configured collectors, off by default.
SOV-5- No licence enforcement, third-party metering or billing hook in open components.
SOV-6- Brand-neutral name packs;.
SOV-7- Cloud services only through adapters with an open-source default.
SOV-8- Fully operable by the operator's staff from public documentation; full export.
SOV-9- No publisher remote access path; support through public channels.
SOV-10- Reproducible builds.
References
Sources cited on this page, in order of first citation. Addresses were last checked on the date shown.
- OBSP 0.1 §8: Security model Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Security and disclosure: registers/policies.yaml security Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Data and privacy: registers/policies.yaml data-and-privacy Observatory Protocol 0.1 (draft), CC BY 4.0.
- Observatory Protocol policy, Operator sovereignty: registers/policies.yaml sovereignty Observatory Protocol 0.1 (draft), CC BY 4.0.
- OBSP 0.1 §12: Operator sovereignty profile (`OBSP-SOV`) Observatory Protocol 0.1 (draft), CC BY 4.0.