[P0] Create threat model and privacy invariants #2

New issue

Closed

opened 2026-07-17 23:57:55 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-17 23:57:55 +00:00

(Migrated from github.com)

Goal

Document what Local Recall must defend against and define fail-closed privacy behavior.

Threats to cover

Accidental capture while disabled.
Secrets appearing in screenshots, OCR, metadata, logs, errors, caches, swap, crash dumps, or temporary files.
Unauthorized local API access.
Malicious or compromised provider plugins.
Database theft and offline inspection.
Key loss, key theft, and unsafe fallback behavior.
Remote-provider data exfiltration.
Untrusted metadata scripts and command injection.
Stale queued work continuing after capture is disabled.

Deliverables

docs/threat-model.md
Trust boundaries and data-flow diagram.
Privacy invariants with corresponding test requirements.
Explicit attacker assumptions and accepted residual risks.

Acceptance criteria

Every persistent artifact and process boundary is covered.
The document defines fail-closed behavior for missing encryption, unsupported capture backends, and policy failures.
Each high-risk threat maps to at least one planned control or test.

Depends on

## Goal Document what Local Recall must defend against and define fail-closed privacy behavior. ## Threats to cover - Accidental capture while disabled. - Secrets appearing in screenshots, OCR, metadata, logs, errors, caches, swap, crash dumps, or temporary files. - Unauthorized local API access. - Malicious or compromised provider plugins. - Database theft and offline inspection. - Key loss, key theft, and unsafe fallback behavior. - Remote-provider data exfiltration. - Untrusted metadata scripts and command injection. - Stale queued work continuing after capture is disabled. ## Deliverables - `docs/threat-model.md` - Trust boundaries and data-flow diagram. - Privacy invariants with corresponding test requirements. - Explicit attacker assumptions and accepted residual risks. ## Acceptance criteria - Every persistent artifact and process boundary is covered. - The document defines fail-closed behavior for missing encryption, unsupported capture backends, and policy failures. - Each high-risk threat maps to at least one planned control or test. ## Depends on - #1