Security model
Approved sources. Authenticated evidence. Independently checkable results.
Workspace access
Cloud checks workspace membership and scoped project keys on authenticated operations. Administrator-approved rules determine the accepted sources, evidence and verification policy.
Evidence and privacy
Cloud stores submitted verification materials and reports in authorized workspaces. Private source records and signing keys stay in the source environment. Retention, deletion and connector credential handling are described in the data handling notice.
Authenticated sources
Signed observations bind the source, task, approved profile and evaluation window. Signature checks establish control of the declared key; the approved source policy supplies its identity and authority. Evidence integrity, signer authenticity and signed service registration are evaluated separately.
Independent review
Independent verification runs offline on exported reports and their verification materials. The export binds the input, approved profile, certificate, policy, verifier version and evaluation time so another reviewer can reproduce the recorded conclusion.
How verification results compose
- Completion certificates use the admitted coordinate model, authenticated sources and approved fault and omission budgets.
- Hashes, signatures and evidence relationships produce separate results. Model-based support assessments retain their method and evidence alongside deterministic checks.
- Missing optional evidence remains NOT_PROVIDED or INDETERMINATE. Conflicting log, epoch, root or witness contexts fail the corresponding consistency checks.