PR #786 — Koschei Sentinel: Canton-relevant progress, seeking a Tech & Ops Champion (Security & Assurance)
grants-discuss0 messages
- Hi all,
PR #786 — Proposal: Koschei Sentinel — Canton Security Assurance & Incident Readiness Toolkit — is still open as Needs Champion, aligned to RFP 27 as primary and RFP 28 as secondary. I am posting a short progress note so that Tech & Ops members with Security & Assurance experience can judge the proposal on its current state rather than on the original submission.
Five pieces of the underlying infrastructure have been completed since the PR was opened. Each one maps directly to the incident-readiness scope in the proposal:
1. Durable monitoring-state tracking. Monitoring state survives process restarts, so a restart cannot silently reset what is being watched.
2. Explicit coverage-loss signaling. When a collector stops producing, the system reports the loss as an explicit state instead of rendering it as "nothing found". Missing evidence is never converted into a clean result.
3. Ingest-gap recovery tracking. Gaps in the event stream are detected, recorded with their boundaries, and replayed where the source permits; what cannot be recovered stays marked as an unresolved gap.
4. Archive and restore verification. Archived evidence is verified on readback against its checksum, so the archive is proven restorable rather than assumed restorable.
5. Deployed-revision verification. The exact revision running in production is verifiable, so an assurance report can be tied to the build that produced it.
Two further results from the last two weeks are relevant to how a Canton deliverable would be audited:
- Findings are now signed with Ed25519 under a published key id, and an open-source TypeScript verifier independently recomputes the canonical payload hash and checks the signature. A third party can verify a finding without trusting our API.
- The deterministic evidence policy is enforced in code: no verified evidence, no grade and no signed verdict. Explanations can describe a verdict but can never produce or override one.
The Canton-specific scope and acceptance criteria in the PR are unchanged and remain open to review. If you are a Tech & Ops member with Security & Assurance experience, I would welcome your review, and I am happy to walk through the threat model, the evidence contracts or the acceptance criteria on a call at your convenience.
PR: https://www.google.com/url?q=https://github.com/canton-foundation/canton-dev-fund/pull/786&source=gmail&ust=1791767408024000&sa=E
Best regards,
Onur Sel
Founder, Koschei