docs(security): update config path and acknowledge cue subprocess#58
Merged
docs(security): update config path and acknowledge cue subprocess#58
Conversation
After #38 moved the config to .vaultctl/config.yml, four references in SECURITY.md were left at the legacy .vaultctl.yml path. Trust-boundary semantics are unchanged; only the strings needed updating. While here, add a single line to the local-operations section acknowledging that `cue` is a second external-binary subprocess parallel to `ansible-vault` (added across #34/#39 and the schema lifecycle work in #40 phases 1-3). Same trust boundary, same shape of guarantee — the document stays honest about what runs in CI. No new attack surface analysis: schema.py operates on already-decrypted data inside the process and makes no network calls beyond invoking `cue vet`. The audit table's approximate LOC counts are still accurate within rounding. Closes #57.
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.
Summary
Targeted refresh of `docs/SECURITY.md` after the `.vaultctl/`-restructure (#37/PR #38) and the CUE schema work (#34/#39, #40).
Changes
Why Minimal
Per the project's quality bar (#feedback_quality_bar_simple_useful), no schema-validation feature description was added. `schema.py` doesn't introduce new attack surface — it operates on already-decrypted data inside the process and makes no external calls beyond `cue vet`. The path strings and the one parallel-subprocess line are exactly what changed; nothing else needs updating.
The audit-table LOC approximations were verified (`redact 88`, `ai_detect 255`, `vault 97`, `password 64`) and are still within the document's existing rounding (~80, ~250, ~80, ~60) — no churn there.
Closes #57.