Repository navigation
Conversation
Record when and by whom a vault secret is revealed, copied or exported, not just CRUD on the record. Supports NIS2 and ISO 27001 audit needs. - New model vault.access.log (secret, user, timestamp, IP, access type), read-only to end users and created via sudo so the trail is immutable. - vault.entry.action_log_access logs the event and emits a single-line JSON record for SIEM collectors. Source IP is read server-side. - OWL patch on the secret field fires on reveal and copy. Only the record id and access type are sent, never the decrypted value. - New Vault Manager group. Users see their own logs, managers see all. - Manager-only Access Logs tab on the secret form plus a list and search view under Vault > Access Logs. - Tests for logging, invalid type, per-user visibility and immutability.
bosd
changed the title
bosd
marked this pull request as ready for review
October 21, 2026 12:08
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
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.
What
Adds read and access auditing to the vault module. Today vault tracks CRUD
on secrets but not who actually revealed, copied or exported a value. This
records that, which is what NIS2 and ISO 27001 reviews ask for.
How
vault.access.logholding secret, user, timestamp, source IPand access type (reveal, copy, export). Logs are read-only for end users
and written via sudo, so the trail cannot be edited or deleted by users.
vault.entry.action_log_access(access_type)records the event and alsoemits a single-line JSON log line for SIEM collectors. The source IP is
resolved server-side from the HTTP request, not the browser.
Only the record id and access type leave the browser, never the plaintext.
managers read all of them.
list and search view under Vault > Access Logs (filter by type, date, user).
Tests
New tests cover logging on access, rejection of an invalid access type,
per-user visibility via record rules, and immutability for non-managers.
Run with
--test-tags /vault.