Cryptography Rules Tighten: What Regulators Will Demand From Key Managers
Archi3 min read
Contents
Regulators Move From Algorithm Lists to Key Lifecycle Proof#
A draft policy circulating among financial supervisors would require regulated firms to produce, on demand, a complete audit trail for every cryptographic key used in production. The shift marks a break from the old model, where compliance meant checking a cipher against an approved list once a year. Under the draft, which several agencies are expected to finalize in stages over the next 18 months, the unit of oversight becomes the key itself: where it was generated, who can touch it, when it rotates, and how it is destroyed.
Cryptography teams that have spent the past decade arguing about RSA versus elliptic curves now face a different set of questions. Regulators want evidence that keys are not shared across tenants, that hardware security modules are configured to block export, and that revocation actually happens within a stated window. The technical arguments are mostly settled. The paperwork is not.
What the Draft Asks For#
Three requirements appear in every version of the text reviewed so far. First, firms must maintain a register of cryptographic assets, including keys, certificates, and trust anchors, with a named owner for each. Second, key rotation must be demonstrable, not just declared: a signed log showing the old key retired and the new one activated. Third, any use of deprecated algorithms requires a written exception with a migration date.
The third point carries the most weight. Supervisors have grown tired of migration plans that slip year after year. An exception with a date is auditable. A promise to move off SHA-1 eventually is not.
One supervisor involved in the drafting described the intent plainly: the goal is to make cryptographic failure visible before it becomes an incident. That framing matters. Regulators are not trying to pick algorithms. They are trying to make sure firms know which keys they depend on and can prove it.
The Post-Quantum Problem Behind the Push#
The timing is not accidental. Post-quantum migration is expected to touch every public-key system in use, and supervisors have watched enough large projects run late to distrust voluntary timelines. A firm that cannot inventory its keys today will struggle to replace them when hybrid post-quantum handshakes become mandatory.
Industry groups have pushed back on one element: the demand for continuous attestation from hardware security modules. Smaller firms argue that the cost of upgrading HSM firmware to produce the required logs is disproportionate. A compromise under discussion would allow sampled attestation for firms below a certain size, with full logs required after the next hardware refresh.
Enforcement Leans on Existing Powers#
Most of the draft relies on powers regulators already hold. Banks must show operational resilience. Payment processors must demonstrate controls. Crypto is being folded into those reviews rather than treated as a separate domain. That means the first enforcement actions are likely to arrive as findings inside a broader examination, not as standalone crypto penalties.
The practical consequence: a firm that fails a key management question may face restrictions on launching new products, rather than a fine. Supervisors have used that lever before, and it tends to move timelines faster than money does.
What Changes for Engineering Teams#
The work lands on platform and security engineers, not compliance officers. A few items are already showing up in examiner requests: , A current inventory of keys and certificates, including those embedded in firmware and third-party appliances, Rotation records for the past 12 months, with timestamps, Configuration evidence that private keys cannot be exported from HSMs in plaintext, A named owner for each key family, reachable during an incident, A migration schedule for any algorithm on the deprecation list
None of these are exotic. Most large firms can produce them with effort. The gap is usually in the long tail: keys baked into vendor products, test environments that share production material, and certificates nobody remembers issuing.
The Calendar#
Supervisors have signaled a phased approach. Inventory and ownership requirements are expected first, likely within 12 months. Rotation evidence and exception handling follow. Continuous attestation is the last phase and the most contested.
For teams that have deferred key inventory work, the window is closing. The first examinations under the new expectations are expected to ask for the register before they ask for anything else. Firms that cannot produce it will spend the rest of the review explaining why.
More articles