Skip to content

docs(security): record the multi-replica replay-guard residual #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
terraboops merged 1 commit into from
Sep 28, 2026
Merged

docs(security): record the multi-replica replay-guard residual #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,13 @@ single-use; both are weaker than confining the hop. Restrict who reaches the
backend (a network policy), and keep the lifetime short. This is the same
trust that every identity-aware proxy places in the network behind it.

The shipped replay guard is per-process: it protects one backend instance. A
horizontally scaled backend needs a shared store behind the `ReplayGuard`
interface (the interface exists so one can be plugged in); running more than
one replica with the in-memory guard gives false comfort, not protection. No
shared implementation ships here on purpose — it would pull in a datastore the
generic library has no business choosing.

## What is not in scope

* **A stolen device.** A person with an unlocked device gets the identity of
Expand Down
Loading