Security Artifacts

Generated from security/README.md. Edit the canonical source file, not this page.

Required (foundation gate §13)

• threat-model.md — threat model covering the attack surface of the protocol
• authorization-matrix.md — complete matrix of which roles can perform which operations on which resources
• abuse-cases.md — abuse case catalogue (adversarial perspective)

These artifacts must exist and be reviewed before any production broker implementation begins. See QUALITY-STRATEGY.md §8.10 and §13.

Threat model scope

• Organization and object-level isolation
• Field-level disclosure
• Token audience and scope validation
• Replay resistance
• Webhook authentication
• Resource enumeration resistance
• Injection and hostile references
• Oversized payload handling
• Sensitive log redaction
• Retention and deletion
• Software supply chain
• OWASP API Security Top 10

No unresolved critical or high finding is releasable without an explicit, time-bounded risk acceptance.