Repository navigation
[CA-01-S6] Document Echo security posture and threat models #667
Description
Activity
🔗 Related PRs
#546 - Adopt braids and strands hardening roadmap [closed]
#582 - docs: define the Echo 1.0 release contract and move live planning to GitHub [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Implemented in e9a12b0. The security topic set documents protected assets, trust boundaries, threat actors, mitigations, residual risks, non-goals, authority distinctions, and current evidence across admission, WAL, CAS/projections, exchange, recovery, and resource exhaustion.
Goal
Publish an evidence-grounded security topic set that states what Echo protects, which components and identities it trusts, which attackers and failures it considers, how current controls map to those threats, and where the implementation deliberately makes no security claim.
Acceptance criteria
docs/topics/security/README.mddefines the security posture, protected assets, trust boundaries, security properties, and documentation map.docs/topics/security/ThreatModel.mdenumerates attacker capabilities, abuse cases, mitigations, residual risks, and explicit non-goals across application proposals, trusted-host admission, WAL and durable storage, CAS and projections, Continuum transport, observer capabilities, recovery, replay, downgrade, corruption, and resource exhaustion.docs/topics/security/AuthorityBoundaries.mddistinguishes causal authority, cryptographic integrity, authorization, confidentiality, durability, availability, and derived evidence; no checksum, digest, receipt, WAL record, cache, or materialization is overstated as proof beyond its actual proposition.docs/README.mdanddocs/topics/README.mdlink the security topic set.