Protecting historical records can require changing the controls that make them readable at all.
Retiring a risky cryptographic foundation can conflict with preserving dependable access to old records.
Who you’d be doing this for
“When someone needs a statement for a deadline, ‘we can’t open it’ isn’t an option.”
Ida Olsen · Tenant advocate
Helps customers retrieve account statements and transaction records for housing and benefits documentation.
What is at stake
Pre-migration checks show 0.18% of sampled objects fail to decrypt on the target service, mostly in legacy storage. You have to commit to a cutover you can verify, knowing a bad one locks customers out of their records.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- key retirement vs record recoverability
- broad migration speed vs proof of decryptability
- security exposure reduction vs legacy access continuity
- fixed deadline vs irreversible cutover
Why Chime
For Chime, this can matter because secure access to account records often becomes most important after the original transaction has passed.
Written with these in mind
Not your kind of problem? 8 more at Chime, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.