-
Notifications
You must be signed in to change notification settings - Fork 138
[SECURITY] Add vault key rotation with backward-compatible credential migration #203
Copy link
Copy link
Open
Labels
area:backendBackend API, database, or service workBackend API, database, or service workarea:securitySecurity-sensitive implementation or testsSecurity-sensitive implementation or testslevel:critical80 pts difficulty label for critical or high-impact PRs80 pts difficulty label for critical or high-impact PRspriority:highHigh-priority issueHigh-priority issuetype:featureFeature work category bonus labelFeature work category bonus labeltype:securitySecurity work category bonus labelSecurity work category bonus label
Metadata
Metadata
Assignees
Labels
area:backendBackend API, database, or service workBackend API, database, or service workarea:securitySecurity-sensitive implementation or testsSecurity-sensitive implementation or testslevel:critical80 pts difficulty label for critical or high-impact PRs80 pts difficulty label for critical or high-impact PRspriority:highHigh-priority issueHigh-priority issuetype:featureFeature work category bonus labelFeature work category bonus labeltype:securitySecurity work category bonus labelSecurity work category bonus label
Problem
SecuScan needs a production-grade improvement in this area: Vault encryption and credential lifecycle..
Scope
Add a key version field for vault entries, support decrypting old entries during rotation, provide an admin rotation command/API, and ensure failed rotations leave data untouched.
Acceptance Criteria
Verification
Unit tests should cover old-key decrypt, new-key encrypt, interrupted rotation rollback, and missing key errors.
Difficulty
Hard, useful issue intended for experienced contributors.