The application that wrote it is gone
Decommissioned, or the vendor left. The encrypted archive remains, in a format nobody in the building has touched in years, and nobody wants to be the one who breaks it.
ANKASecure© modernizes legacy cryptographic estates in four steps without the originating application: PKCS#12 and JKS keystores are imported through a seven-stage validation pipeline that reports certificate status and migration path, while the keys are still valid, because an expired key is refused for the conversion; each PKCS#7 archive is analyzed for the algorithms and key references it uses; the archive is converted to a JOSE-based representation (JWE/JWS with extended identifiers) in streaming with bounded memory, addressed to its own keys, the content decrypted and encrypted again under a fresh content key inside the control plane without the plaintext ever being written to disk, logged or returned to the caller; and, as a second step, the converted archive is re-encrypted or re-signed under a post-quantum or composite key, while the old keys are retired rather than destroyed so original envelopes stay readable under policy. Every import, conversion and re-encryption is recorded in a signed, tamper-evident audit trail. Discovery of which archives exist is delivered by ANKATech channel partners.
The system that wrote them is gone, the vendor with it, and the certificate is expiring on data the business cannot lose. ANKASecure© imports the keys, converts the archives to a JOSE-based representation in streaming without exposing plaintext, then moves them to the keys the policy requires, while the originals stay readable.
Is this you
Decommissioned, or the vendor left. The encrypted archive remains, in a format nobody in the building has touched in years, and nobody wants to be the one who breaks it.
Retention says ten more years. The key material says eighteen months. Renewal is not an option when the issuing system no longer exists.
“And the encrypted archive?” Every plan to move the platform stops at the data that was encrypted under the old one.
Who signs this: A head of platform engineering or a modernization program owner with a decommissioning date, and a CISO who has to approve what happens to the archive. If the honest plan for the legacy data is “leave it where it is”, this is the conversation.
Why existing approaches fall short
Teams facing an archive under an old format reach for one of four plans. Each one either leaves the data where it is or exposes it on the way out: a script that decrypts everything to disk, a rewrite of an application that no longer exists, a library upgrade that only changes what is written next. The problem is not choosing an algorithm. It is moving data that is already protected without creating a moment in which it is not.
Where the plaintext exists
What it needs from the old system
What happens to the old keys
What you can prove afterwards
A records system wrote ten years of PKCS#7 envelopes to a recipient certificate that expires in eight months. Retention says the records must stay readable for another decade. The vendor is gone. The first plan is a script on a hardened server: decrypt everything, re-encrypt with a new library, delete the originals. Security refuses it, because for the length of the run the whole archive exists in plaintext on one machine. The second plan is to leave the archive alone and renew nothing. Eight months later the key can still decrypt but can no longer be used to protect anything, and every option that remains starts from plaintext.
An old envelope is rarely one algorithm. It is a bundle of decisions made by people who have left.
Several signers or several recipients
A signature over SHA-1 or MD5
Content under 3DES-CBC or AES-CBC
Signed and enveloped data (RFC 2315 §11)
A signer certificate anyone could have copied
How it works
Import, analyze, convert, bridge. The originating application is not needed at any step, and the plaintext is never written anywhere.
ANKASecure© imports PKCS#12 and JKS keystores through a seven-stage validation pipeline that reports each certificate’s real status and its migration path. A key past its expiry is refused for the conversion, so the keys come in while they can still protect.
Before converting anything, ANKASecure© reads the PKCS#7 structure and reports the algorithms, the key references and the migration path per item — compact or streaming — so the conversion is planned against what is there, not against what the documentation said.
The PKCS#7 envelope is converted to JWE/JWS with extended identifiers, addressed to the archive’s own recipient keys. The content is decrypted inside the control plane and encrypted again under a fresh content key; it streams with bounded memory, without the plaintext ever being written to disk, logged or returned to the caller.
The converted archive moves to a post-quantum or composite key in a second step, a re-encryption or re-signing under the rotation and lifecycle policies. Old keys are retired, not destroyed, so the original envelopes stay readable for as long as the policy says. Both coexist under one policy until the last archive is moved, and each conversion and re-encryption is recorded with its key and outcome.
Modernization done right
The fair objection to converting an archive in a central service is that the service now sees every plaintext. ANKASecure© answers it in the authorization model rather than in a promise: a conversion or a re-encryption needs a re-encryption grant from the old key to the new one, and no decrypt grant on either, so the caller who runs the migration is never given the content. The rest is sequencing.
The keystore and the archive are read before anything is imported or converted. The keystore preview reports, per alias, the algorithm, the projected key identifier and the purpose derived from the certificate, and imports, wraps and records nothing. The archive analysis names every signer, every recipient and the keys the conversion will need.
The PKCS#7 conversion changes the container, not the cryptography: the new envelope is written to the same keys the archive used. Moving it to a post-quantum or composite key is a separate re-encryption or re-signing, decided by the rotation and lifecycle policies like any other. Each step is small enough to verify on its own.
A legacy hash is refused unless the request says otherwise, an unresolved signer or recipient stops the conversion before any private key is used, and every refusal is named and recorded. Nothing weak is quietly promoted into the governed format.
A key revoked because its algorithm was deprecated keeps decrypting and verifying under the default policy while new protection is refused. Destruction is the only end of that history: it always waits for a person other than the requester and a cooling-off period of 7 to 365 days.
NIST SP 800-57 Part 1 describes the same shape for stored data: the period in which a key may apply protection can end long before the period in which the data it protected must still be processed, and when the data must outlive the key, protection is reapplied under a new key. It also warns that re-encryption does not repair what was already exposed: ciphertext that travelled under a weak algorithm may already have been captured. Modernization limits future exposure; it does not rewrite the past.
The conversion window
A legacy archive has two clocks. The first is retention: how long the records must remain readable. The second is the life of the keys that protect them. The conversion writes the new envelope to the archive’s own keys, so each of those keys must still be allowed to protect at that moment. A key past its expiry or at its usage limit keeps decrypting and verifying, but ANKASecure© refuses to use it to write, and names it. The window to move the archive closes when its keys stop protecting, not when retention ends.
Key recovery
Analysis
Format conversion
Algorithm move
Exit
Discovery of which archives exist, and which systems still read them, is work done with your team or an ANKATech partner before any of this starts. What ANKASecure© shortens is everything after it: the keys are imported once, the archive is converted in a stream, the algorithm move is a re-encryption under policy, and the exit is a recorded revocation followed by an approved destruction. The order matters most where the window is shortest: convert while the archive’s keys can still protect, and re-encrypt to the target afterwards.
Fifteen minutes
Live, on a real deployment, with an archive shaped like yours. Nothing in this list is a mock-up or a roadmap item.
A PKCS#7 archive from a decommissioned system, and the PKCS#12 keystore that goes with it.
The keystore is imported: seven validation stages, each certificate’s status and validity reported, the migration path named.
The archive is analyzed, then converted to the JOSE-based representation, still addressed to its own keys. Memory stays flat while it streams.
The second step: the converted envelope is re-encrypted to a policy-approved post-quantum key. The original still opens too, because its key was retired and not destroyed.
The audit trail: import, conversion and re-encryption, signed, each with its key and outcome.
Your archive, discussed on the deployment rather than on a slide.
Legacy is a defined state
NIST SP 800-131A Rev. 2 defines legacy use precisely: an algorithm or key length that may be used only to process information already protected, such as decrypting ciphertext or verifying a signature. Most of what sits in a legacy archive is in that state today. The obligation is not to make the old data unreadable. It is to stop applying new protection with the old mechanism and to move what must be kept.
Three-key TDEA (3DES)
SHA-1 in digital signatures
ECB mode, SHA-1 and 224-bit hashes
A key protecting stored data
PCI DSS v4.0 requirement 12.3.3, mandatory since 31 March 2025, asks for an up-to-date inventory of the cipher suites and protocols in use, active monitoring of their continued viability and a documented strategy to respond to anticipated changes. ANKASecure© does not produce the inventory. It is the response path for the data and keys brought under it.
NIST IR 8547, final since October 2026, deprecates quantum-vulnerable public-key cryptography after 2030 and disallows it after 2035. An archive converted to a governed format before then is one re-encryption away from meeting it, not one project away.
Each conversion, each re-encryption and each refusal is recorded as a signed audit event with the key and the outcome. The question an auditor asks at the end of a migration, whether the old mechanism still protects anything new, is answered from the trail.
What it rests on
Shipping
PKCS#7 analysis and conversion to JOSE
Compact and streaming; the conversion keeps the archive’s own keys and encrypts the content again under a fresh content key inside the control plane, with no plaintext egress.
Shipping
PKCS#12 and JKS import
Seven-stage validation pipeline with certificate status and migration-path analysis.
Shipping
Re-encryption and re-signing without plaintext exposure
Compact and streaming, bounded memory at any file size.
Shipping
Key lifecycle with retirement
A retired key still decrypts what it protected; only destruction removes that, and destruction is a separate, audited step.
Shipping
120+ algorithms
The classical families the archives were written with and the post-quantum and composite families they move to.
Per channel
Discovery and inventory
Which archives exist and which systems still read them, delivered by ANKATech channel partners.
The framework
The Cryptographic Control Plane reference architecture describes each pillar through the scenarios it must handle and one practical test. This solution is the modernization pillar’s scenarios, taken literally.
03
Primary pillar
Scenario realised
Migrating legacy cryptographic infrastructure
Practical test
“Can the protection of data encrypted years ago be changed today, without the originating application and without plaintext at rest?”
04
Supporting pillar
Scenario realised
Enforcing a new enterprise security requirement
Practical test
“Can the organization prove, by querying the control plane, which policy applied to a given operation, and change that policy centrally?”
Maturity move
From algorithms and formats embedded in systems nobody can change to data held in a governed representation under a Control Plane. This is the step that makes every later level possible for the archive.
It does not recover data whose key is lost, or convert an archive whose keys have already expired. Conversion needs the original key material, still valid; without it there is nothing to convert with, and no control plane changes that.
It does not reach archives held by a system that will not delegate the operation. Data stays where it is until that system, or a copy of its data, is brought under the plane.
It does not certify you. ANKASecure© maps its controls to NIST CSWP 39, the GSA PQC Buyer’s Guide and OWASP and hands you the evidence; the determination is still your auditor’s.
Where to start
The archive to start with is not the largest one. It is the one whose keys stop protecting first, because after that date the conversion can no longer write to them and the honest options get worse.
1
Locate the keystores and their passwords, preview them without importing, and analyze a sample of each archive to learn which keys and algorithms it actually uses.
2
ANKASecure© importing the keys, converting one file in a stream and re-encrypting it under a policy-approved key, with the original still readable.
3
One archive, its keys imported under your existing HSM or KMS custody, converted end to end, the old keys revoked for algorithm deprecation and kept readable until the destruction is approved.
After this
No new deployment, no second contract for the platform. Once the archive is in the governed format, everything else is a policy change.
The PKCS#7 estate from the system that is gone. Fifteen minutes on a live deployment to import its keys, analyze it and convert one file.
Book the demo