Repository navigation
docs: keep the Bitwarden account that can read the secrets off agent machines - #86
Merged
Merged
Conversation
…machines T7 says: never log in to the approver's Telegram account on an agent machine. The docs had no such rule for Bitwarden. Whoever is logged in to an account that can read the store's secrets can read them in Bitwarden's own apps, with no tap and no entry in nodkey's audit log. The new threat T32 lists who can read the secrets, by Bitwarden's documentation and source code: owners and admins of the organization, the member who made the project, members with access to the project or to one secret, members of a machine account that can read them, and for bw the separate account and its emergency access contacts. It says what to do: use an account that is never logged in on an agent machine, do not save its master password or two-step key in a password manager that is open there, use two-step login with an app or a security key, and check the members after each change. The trust table, the known limits (section 5), the assumptions (section 7), setup.md sections 1, 5 and 9, the README and DESIGN.md section 11 point to the rule. setup.md section 5 also notes the Free Secrets Manager plan (seen 2026-10-16). Closes #82
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #82.
Why
T7 says: never log in to the approver's Telegram account on an agent machine. The docs had no such rule for the Bitwarden side. Whoever is logged in to a Bitwarden account that can read the store's secrets can read them in Bitwarden's own apps, with no tap and no entry in nodkey's audit log. A common setup keeps the main Bitwarden account open on the computer where the agent works.
What changes
bws(with the Free Secrets Manager plan, as Bitwarden's plan page shows it) and forbw(no emergency access).Review
A security review subagent checked it in three rounds. All Bitwarden quotes match the pages; all links and anchors resolve. The Go tests that read DESIGN.md pass (they check sections 5, 7, 13 and 14; this changes section 11). Docs only; no code changes.