Complexity: Hard (200)
Description
Soter handles biometric evidence, recipient identity data, and value-bearing onchain operations,
with controls spread across services: app/ai-service/logging_redaction.py,
services/evidence_access_control.py, the backend HMAC and API key scope guards, artifact access
tokens, and retention policies. No document states what the threat model is or how these controls fit
together, which makes it impossible to review the system's security posture as a whole.
Acceptance Criteria
- Trust boundaries between mobile, frontend, backend, AI service, and contract are described
- Each class of sensitive data is documented with where it lives, how long, and who can read it
- Authentication and authorization mechanisms are described per boundary, including HMAC and API key scopes
- Redaction, retention, and purge behaviour is documented per service
- Known gaps and accepted risks are stated explicitly rather than omitted
Complexity: Hard (200)
Description
Soter handles biometric evidence, recipient identity data, and value-bearing onchain operations,
with controls spread across services:
app/ai-service/logging_redaction.py,services/evidence_access_control.py, the backend HMAC and API key scope guards, artifact accesstokens, and retention policies. No document states what the threat model is or how these controls fit
together, which makes it impossible to review the system's security posture as a whole.
Acceptance Criteria